(0013343)
Ken Moreland (manager)
2008-09-08 09:38

What do you expect to happen? The Mandelbrot source has no time associated with it. If you want to see something animate, you first have to define something that changes over time.

(0015034)
Utkarsh Ayachit (administrator)
2009-02-17 13:22

Mandelbrot has no time. If an animation is defined using the Animation View, it shows correctly.

(0015120)
Alan Scott (manager)
2009-02-17 21:42

If there isn't any time in the dataset (mandebrot), why does time cycle from 0 to 1 in the display window? Shouldn't it just stay as 0?

(0015140)
Utkarsh Ayachit (administrator)
2009-02-18 11:05

That's the animation time. You can create animations with non-time sources as well such a sphere source. In that case the time is the animation time. Actually, the time in the toolbar is always the animation time, it just matches the data-time when readers provide time.

(0015143)
Ken Moreland (manager)
2009-02-18 11:11

ParaView is doing the right thing. If one or more pipeline objects specify time, the time range defaults to the range of time defined. If no pipeline objects specify time (as is the case here), then the time range defaults to 0-1. (It also defaults to a sequence of 10 time steps.) This behavior should stay the same because:

1) Setting the start/end time both to 0 would unnecessarily complicate creating animations. You would have to change the time range before adding any tracks, and if you forgot that it could do some screwy things to your animation time.

2) Setting the time anywhere between 0 and 1 is no more or less correct then having the time as 0. If you have data that does not change over time, it does not change over time. It is consistent for any time value that you set. If you loaded both the Mandelbrot source and some other data with these time steps, wouldn't you expect the Mandelbrot to stay the same, exactly as it does now?

3) There is no compelling reason to change it. This has been ParaView's behavior since ParaView supported animations (which is to say, forever). I don't think this behavior confuses people, and it would add heartache to other users to make the change.

(0015180)
Alan Scott (manager)
2009-02-18 16:51

Not a bug.

Issue History
Date Modified	Username	Field	Change
2008-09-05 20:54	Alan Scott	New Issue
2008-09-08 09:38	Ken Moreland	Note Added: 0013343
2009-02-17 13:22	Utkarsh Ayachit	Note Added: 0015034
2009-02-17 13:22	Utkarsh Ayachit	Status	backlog => @80@
2009-02-17 13:22	Utkarsh Ayachit	Resolution	open => won't fix
2009-02-17 13:22	Utkarsh Ayachit	Assigned To	=> Utkarsh Ayachit
2009-02-17 21:42	Alan Scott	Note Added: 0015120
2009-02-17 21:42	Alan Scott	Status	@80@ => @20@
2009-02-17 21:42	Alan Scott	Resolution	won't fix => reopened
2009-02-18 11:05	Utkarsh Ayachit	Note Added: 0015140
2009-02-18 11:05	Utkarsh Ayachit	Status	@20@ => @80@
2009-02-18 11:05	Utkarsh Ayachit	Resolution	reopened => fixed
2009-02-18 11:11	Ken Moreland	Note Added: 0015143
2009-02-18 11:11	Ken Moreland	Resolution	fixed => no change required
2009-02-18 16:51	Alan Scott	Note Added: 0015180
2009-02-18 16:51	Alan Scott	Status	@80@ => closed
2009-05-13 13:46	Utkarsh Ayachit	Target Version	=> 3.6
2011-06-16 13:10	Zack Galbreath	Category	=> (No Category)

Notes
(0013343) Ken Moreland (manager) 2008-09-08 09:38	What do you expect to happen? The Mandelbrot source has no time associated with it. If you want to see something animate, you first have to define something that changes over time.

(0015034) Utkarsh Ayachit (administrator) 2009-02-17 13:22	Mandelbrot has no time. If an animation is defined using the Animation View, it shows correctly.

(0015120) Alan Scott (manager) 2009-02-17 21:42	If there isn't any time in the dataset (mandebrot), why does time cycle from 0 to 1 in the display window? Shouldn't it just stay as 0?

(0015140) Utkarsh Ayachit (administrator) 2009-02-18 11:05	That's the animation time. You can create animations with non-time sources as well such a sphere source. In that case the time is the animation time. Actually, the time in the toolbar is always the animation time, it just matches the data-time when readers provide time.

(0015143) Ken Moreland (manager) 2009-02-18 11:11	ParaView is doing the right thing. If one or more pipeline objects specify time, the time range defaults to the range of time defined. If no pipeline objects specify time (as is the case here), then the time range defaults to 0-1. (It also defaults to a sequence of 10 time steps.) This behavior should stay the same because: 1) Setting the start/end time both to 0 would unnecessarily complicate creating animations. You would have to change the time range before adding any tracks, and if you forgot that it could do some screwy things to your animation time. 2) Setting the time anywhere between 0 and 1 is no more or less correct then having the time as 0. If you have data that does not change over time, it does not change over time. It is consistent for any time value that you set. If you loaded both the Mandelbrot source and some other data with these time steps, wouldn't you expect the Mandelbrot to stay the same, exactly as it does now? 3) There is no compelling reason to change it. This has been ParaView's behavior since ParaView supported animations (which is to say, forever). I don't think this behavior confuses people, and it would add heartache to other users to make the change.

(0015180) Alan Scott (manager) 2009-02-18 16:51	Not a bug.

Relationships