> OK, I will add it.
Thanks, great news.
> Ability to write 3-D data to files is interesting. But as I wrote
> use of 'unparse' looks wrong -- I suspect that it can be replaced
> by something simpler. In other words I feel that 'Export3D'
> needs a cleanup before we include it.
I can't understand why 'unparse' is needed but I have tried it without
and it does seem to be needed. Can any one help me work it out?
I would call it from the command line like this:
writeObj(subspace(makeObject(x*x-y*y,x=-1..1,y=-1..1)),"myfile.obj")
All the work is done by makeObject (in draw.spad) so that must be
where the parse, which must be unparsed, must get done.
There are two families of function calls in draw.spad with exactly the
same signatures:
makeObject - which builds a ThreeSpace structure
draw - (which I don't tend to use) which calls makeObject above and
then calls makeViewport3D (which opens the x-window and so on)
So makeObject only builds the ThreeSpace domain and I can see no
reason for it to call C or Lisp code.
It builds the points in this line:
fcn : L((SF,SF) -> Pt) :=
[(x, y) +-> makePt4(myTrap2(f, x, y), x, y, (first col2)(x,
y))]
where myTrap2 is defined as follows:
myTrap2(ff:(SF, SF) -> SF, u:SF, v:SF):SF ==
s := trapNumericErrors(ff(u, v))$Lisp :: Union(SF, "failed")
s case "failed" => 0
r:SF := s::SF
r >max()$SF => max()$SF
r < min()$SF => min()$SF
r
So does the Lisp function 'trapNumericErrors' parse the points?
Should I write a version of makeObject that does not call
'trapNumericErrors'?
Martin Baker
--
You received this message because you are subscribed to the Google Groups
"FriCAS - computer algebra system" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/fricas-devel?hl=en.
