My PC is working on the result 00ct_000025446_0 using hadsm3 version 4.02.

The machine was shut down for several days. So maybe the server state was set into \"inactive\" by the CPDN, because no trickle information was reportet. Now the PC is running and has send new trickle to CPDN. the state is still \"inactive\". There are now also two trickle reportet (Sep. 11th and Sep. 9th) on different days with the same timestep information. Is it normal?

> The machine was shut down for several days. So maybe the server state was set
> into "inactive" by the CPDN, because no trickle information was reportet. Now
> the PC is running and has send new trickle to CPDN. the state is still

I set a bunch of workunits "inactive" so they won't get sent out again, but they are still fine to run. The "duplicate trickle" can happen when you shut down at a point that you've hit a trickle but the trickle is "ahead" of the checkpoint. So when you restart it will hit the trickle again. Just an oddity of the way I made trickle timestep points, i.e.

<pre>
Checkpoints (every 144 timesteps)
x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x

Trickles (every 10802 timesteps, "not to scale")
X X X X X

^ so it's possible to trickle here,
but if you stop before the next checkpoint 'x'
you'll end up just before a trickle point.
</pre>

Just an odd quirk that always slipped my mind to correct!