David,
Thanks for looking into this. I did read the documentation,
but obviously didn't quite get it.
Going back and reading the documentation a bit on this, it appears
that your assumption that adding SIDE_EFFECT results in the module
always runs is correct. However, the assumption that
Going back and reading the documentation a bit on this, it appears
that your assumption that adding SIDE_EFFECT results in the module
always runs is correct. However, the assumption that the downstream
modules assume that the output has changed is incorrect. A
SIDE_EFFECT is exactly that. If
I have written a small inboard module, getTime, that returns the
current system clock, using the gettimeofday() call. The module
is marked as having side effects, so it is called on
every execution, as expected.
The problem is the downstream Compute. I want to use the
time of day as a random
Have you tried setting the output of getTime to cache No results.
I'm betting that Compute is seeing getTime as not changing so it
cache's the input value.
David
I have written a small inboard module, getTime, that returns the
current system clock, using the gettimeofday() call. The module
I just tried that and it has no effect...
Somehow, the Compute is not being executed, even though
its input is clearly changing. If I change
Compute's output to no caching, it forces execution,
but that shouldn't be necessary, if I'm
understanding things correctly.
Joel
Have you tried
