CPU <-> GPU rebranding

[Geek@Play]

So I started using the ReSchedule.exe (1.2) from Marius.  Question now is how can I make it rebrand GPU to CPU only those that will error out when the GPU crunches them?

[KarVi]

As far as I know it does this automatically.

If you set the bar to convert 100% to the GPU, it will leave out VLAR and such units that error out, and keep/move them for the CPU to crunch.

[Marius]

So I started using the ReSchedule.exe (1.2) from Marius.  Question now is how can I make it rebrand GPU to CPU only those that will error out when the GPU crunches them?

With version 1.2 this is not possible (it will always reschedulue). Atatched version 1.3 already has this option (see OnlyVLarVHar). There's a textfile explaining stuff, a ini file for remembering settings + AngleRates and it will create a logfile (in automatic mode)

Have fun,
Marius

[attachment deleted by admin]

[Geek@Play]

Thanks Marius.......Exactly what I needed!

 

[Geek@Play]

oooopppsss.....

Been using the Reschedule 1.3 version with no changes to it's configuration file.  Noted two of these go through this moring despite Reschedule running each moring at 3:00am.

VLAR WU (AR: 0.009063 )detected... autokill initialised
SETI@home error -6 Bad workunit header

Guess it's not working.

[Jason G]

...despite Reschedule running each moring at 3:00am....

Which is why I run every hour, since fresh task downloads with closer deadline can preempt tasks in cache and slip through the net.  Could still happen even then, but the probability is lower.

[Geek@Play]

Understood Jason but nothing was prempted.  With a two day cache everything works it's way to the top.

[Jason G]

Ahhh, I see how that could happen, yes.

...thinking...

[Ignoring DCF fluctuation & outage induced cache shrinkage effects] Let's say one day you run, and server had recently issued you a run of VLAR, so it re-marks half the 2 day cache (1 day worth) to CPU.  Now it downloads another day's worth for GPU.  Even if no new tasks preempt, you'll still be finished the already checked portion by the end of that day, before the next run of the rebranding, so for all we know the top-up portion that is now reached is loaded with VLARs that slip the net anyway.

[Geek@Play]

I'll try scheduling it for twice each day but I still don't believe it's working properly with the default configuration.

[Jason G]

quite possible, despite my comments.  I'm still using 1.2, so effectiveness of 1.3 edition itself I don't know either.

[Marius]

quite possible, despite my comments.  I'm still using 1.2, so effectiveness of 1.3 edition itself I don't know either.

I will look at it first thing when i get home monday. Personally i haven seen any vlar in over two weeks so it was hard to test.

Greetings,
Marius

[EPG]

Maybe it works, but the server send wrong wu...
http://setiathome.berkeley.edu/forum_thread.php?id=54154

[Marius]

I will look at it first thing when i get home monday. Personally i haven seen any vlar in over two weeks so it was hard to test.

Finally a couple of vlar's, and there were a couple of problems in the Reschedule 1.3. Most minor but 1 major: It refused to move units to the cpu or do a proper reschedule. All should be solved with the 1.4 though.


Greetings,
Marius

[edit]: attachment removed.

[EPG]

Something seriously wrong with this...
81   81     turns into    6    6
388   6                   462  81

run again

6    6        turns into   81    81
463 81                      387    6

Notice the number of WUs change 462->463 ...  and 388 -> 387


Edit: I wanted to move every non V* wu to GPU, so the slider was at 100% and the onlyVlar option was off.

[Marius]

Something seriously wrong with this...

Indeed, i must check all possibilties (or don't do any programming when i'm just out of hospital  )

[attachment deleted by admin]