Denis
have a look at this URL listed below, and the first link in that page, i
think it might
help you on the right path. It's been a while I did this though. I don't
know the provenance of your data, another potential program you
could look into is glnemo2, which you can find within the NEMO
package
http://bima.astro.umd.edu/nemo/amnh/movies/
Peter
Right. Actually, just this spring, I made some changes (in partiview CVS)
to fix that problem, for just this purpose. Remember that originally
"warp extrap" would yield particle positions like
position(t) = position + t*velocity + t^2*...
Now, with the latest code, you can use "warp extrap" on a dataset with
multiple "datatime" timesteps. You can construct the velocities (and higher-order
coefficients if you use degree > 1) on the assumption that they'll be multiplied
by a time between 0 and 1. Specifically, at time t,
if the highest (integer) datatime less than t is T, then it displays particles
from datatime T, and their positions become
position(t) = position + (t - T)*velocity + (t - T)^2*...
Generally 0 <= (t-T) < 1, except when t goes out of the range of defined
datatimes. When t<0, it uses datatime T=0 particles and coefficents,
and (t-T) < 0 of course; when t exceeds the highest defined datatime,
then t-T can obviously exceed 1.
To get this feature, you'll need to compile partiview from the CVS source;
see the summary on the partiview web page under "Source code"
http://virdir.ncsa.illinois.edu/partiview/#src
... or let me know -- I could make and post a current binary for windows/macos/linux.
> When using the "datatime T" command, Partiview reads and shows a set
> of data at the date T=0, then it reads and shows the new set at T=1
> and so on up to T=99. Apparently, T can not be written with three
> digits, so I can not read more than one hundred time steps.
That doesn't sound right -- there should be no limit other than available
memory, and I've made time-series with thousands of datatime timesteps.
What happened when you tried to make a longer series?
> the warp command applied by Partiview is the last one written in the script
Does that matter? The warp does apply regardless of timestep --
you don't need to (and can't) enter a separate warp for each timestep.
It's true that the integer data-timestep numbers mean that you have to
supply motion coefficients (position, velocity, acceleration, etc.)
at fixed time intervals.
However, even you can only specify data values at integer times,
you can still set the partiview time to any real number,
and it will interpolate (or extrapolate) in the way specified by "warp -extrap".
I've recently checked in a new script into the CVS repository, as
partiview/scripts/timesnapper
To use it (on unix/linux/macos, though not windows),
you'd put it in your search path somewhere,
invoke partiview with your data, adjust for a nice display and
point-of-view, and then type in the partiview text box something like
async timesnapper /some/where/myimage 0 150 0.1
(assuming the range of datatimes was from 0 to 150 or more)
This should take a series of about 1500 snapshots named
/some/where/myimage.0000.png (with time set to 0.0)
/some/where/myimage.0001.png (with time set to 0.1)
/some/where/myimage.0002.png (with time set to 0.2)
...
/some/where/myimage.1500.png (with time set to 150.0)
> --
> You received this message because you are subscribed to the Google Groups "partiview" group.
> To post to this group, send email to part...@googlegroups.com.
> To unsubscribe from this group, send email to partiview+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/partiview?hl=en.