Grass5.0beta - reals ??

GRASS GRASS user
1

Which bits of the Grass5.0 beta should produce real number output where
approprate? I just compiled the 5.0 beta code, and tried both r.surf.contour and
r.mapcalc. Neither of these produced real numbers when they I expected them to.

If using integer numbers in mapcalc, you have to add a decimal
point of you want to get a floating point map.

mapcalc> newmap = oldmap + 123 # here newmap is integer

mapcalc> newmap = oldmap + 123. # this creates a floating point map

Am I missing something? Can somebody direct me to any documentation for the 5.0
project?

I have linked some draft programmer's texts at:
http://www.geog.uni-hannover.de/grass/5.0beta/htdocs/welcome.html

PS what is the relationship (if any) between Baylor's 5.0 beta release and the
   old fpgrass code?

Baylor's team is working on further development. The old fpgrass is
the basis for GRASS 5.x. The next release of GRASS 5.x shall be much more
stable than the old fpgrass and the current beta version.

As the GRASS Research Group is very small, it takes time to
work on the floating point migration. Please be patient (or send your
contributions) until the next release.

Best regards

  Markus Neteler

PS: A lot of things are in progress - stay tuned.

2

Markus,

Many thanks for the response, I see now how the new mapcalc works. Apologies if
my message sounded like a complaint - it wasn't: the research group is doing a
fine job and I'm certain that the whole user community appreciates your efforts.

You didn't say what the current state of other routines (e.g. r.surf.contour and
r.surf.idw) is with respect to real numbers - do the versions of these in
5.0beta produce reals or is that modification pending?

David Wheatley

Markus Neteler wrote:

If using integer numbers in mapcalc, you have to add a decimal
point of you want to get a floating point map.

mapcalc> newmap = oldmap + 123 # here newmap is integer

mapcalc> newmap = oldmap + 123. # this creates a floating point map

As the GRASS Research Group is very small, it takes time to
work on the floating point migration. Please be patient (or send your
contributions) until the next release.

Best regards

  Markus Neteler