Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo


Tree [r453] /

File Date Author Commit
Glite 2010-06-13 kahr-alpha [r48]
Octave 2012-06-23 kahr-alpha [r409]
Renders 2011-05-21 kahr-alpha [r197] Normalization factor
TeX 2012-07-19 kahr-alpha [r440]
code_archive 2011-07-07 kahr-alpha [r256]
render 2010-11-01 kahr-alpha [r95]
src 2013-11-28 kahr-alpha [r453]
svg 2012-07-18 kahr-alpha [r439]
tmp 2011-06-26 aldaron-j [r218] Added a tmp dir and a readme.txt for a basic us...
Gneiss_biblio.bib 2012-09-18 kahr-alpha [r449]
SConstruct 2012-11-02 kahr-alpha [r450]
authors 2012-05-26 kahr-alpha [r372] Large commit which is mostly about the new beha...
bfont.ttf 2010-05-22 kahr-alpha [r43]
buildingthestuff.txt 2012-08-15 kahr-alpha [r446]
link.txt 2010-05-23 kahr-alpha [r46]
makefile.unix 2012-07-19 kahr-alpha [r443]
premake4.lua 2012-07-29 kahr-alpha [r445]
readme.txt 2011-07-03 aldaron-j [r245] conventions to readme

Read Me

Gneiss is compiled to one executable. Output is written in BMP files in a sub-
directory. Renders/ is for single images, render/ for animations. Some output
is also in tmp/. If the right directory doesn't exist, gneiss will just silently
not write output.

Different use cases are documented below:

* Planet generation *

run the fresh gneiss executable.

* Nebula graphics generation *

to access the nebula, you got to comment line 37 in mathUT.h and rebuild.

* Coding conventions *

An effort-like thing is made to use standard SI units if not specified otherwise.
So here's a key that just might help with variable names:

x, y, z			Cartesian coordinates
x1, x2, x3, face	Internal coordinates for cubed sphere. -1 .. 1, -1 .. 1, N levels, 0 .. 5 face
r, th, ph		Spherical coordinates in radians. Radius meters, theta 0 .. pi, phi 0 .. 2pi.
r, theta, phi		Same
h, lat, lon		height above mean radius, latitude -90 .. 90 degrees, longitude 0 .. 360 deg.
R0			Mean radius