Yes, thats the expected behavior. Before a module is run, a cache tag for the module's output is created from the cache tags of the module's inputs, and the cache is searched for that key. In this case, the input to Import is the string containing a filename, so it misses the fact that the file contents are different. You can "fix" it by by sending the FileSelector output to the second input of Format, adding an Integer interactor and connect it to the third input, and setting the first to "%s". Format will create an output string that contains the filename, but its cache tag will reflect both the filename and the integer value. So you can update the cache tag of the filename without changing the filename itself by bumping the Integer interactor, and it will re-import the file.
Greg
| Hartwig Wiesmann <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED] 02/09/2004 01:43 PM
|
To: [email protected] cc: Subject: [opendx-users] data caching with the import module |
Hi!
I have connected the "FileSelector" module with the "Import" module.
The data is rendered and shown by the "Image" module.
In case I change the file with the "FileSelector" module and re-execute
the data is read and the image is newly rendered. If I switch back to a
file that has already been rendered but the data in the file has
changed meanwhile the old image is re-drawn. This means that the data
is somewhere cached instead re-read from the file.
My questions:
1) is this normal behaviour? I am using OpenDX on MacOSX.
2) is there any possibility to force OpenDX to re-read the data from
the file?
3) can I invalidate the data of the import module so that a new
execution of the OpenDX program will re-read the data from the file?
I already tried to switch off all caching but this does not show any
effects. The only workaround I found is to reload the whole OpenDX
program. But this is very annoying!
Hartwig
