Short results reshedule for CPU

[Pepi]

Rescheduling tool is great, but tell me is this possible.
When tool scan result and determine what result is VLAR and what is not, is also possible to add option to take short ones ( below few minutes computing on cuda) to reschedule on CPU?
Maybe this is foolish, but I would love to have that option.

[Raistmer]

Such tasks called VHARs and Re-schedule 1.9 already has required option.

[Pepi]

Such tasks called VHARs and Re-schedule 1.9 already has required option.

So VHARS are always short ones?

[Raistmer]

Such tasks called VHARs and Re-schedule 1.9 already has required option.

So VHARS are always short ones?

Yes. VHAR means very high angle range.
If angle range is big, telescope moved fast and any single signal source stayed in observation field relatively short time. That is, no some signal accumulating procedures are possible. Generally, we can extract much less from such tasks. Hence smaller processing times. There is just less work to do on those data.

[Pepi]

In that case I am very confused!!!! 
Reschedule tools shows only 105 VHARS  and I have got 240 task with short times. ( all times are same cca 7 minutes)

[Raistmer]

In that case I am very confused!!!! 
Reschedule tools shows only 105 VHARS  and I have got 240 task with short times. ( all times are same cca 7 minutes)

That is, VHAR threshold used in Re-schedule just differs from threshold used to estimate running time.
What strange in that? If you would see let say 200 VHARs and only 100 "short" tasks - that would sound strange to me

[Pepi]

In that case I am very confused!!!! 
Reschedule tools shows only 105 VHARS  and I have got 240 task with short times. ( all times are same cca 7 minutes)

[/qote]

That is, VHAR threshold used in Re-schedule just differs from threshold used to estimate running time.
What strange in that? If you would see let say 200 VHARs and only 100 "short" tasks - that would sound strange to me

That option I would love to have
To determine only short ones between VHARS

[Raistmer]

Again, ALL VHARs are short. Reverse isn't true, not all shorties are VHARs.
If AR of task near VHAR threshold it will have small execution time too, but will be not VHAR from re-scheduler point of view.
You could adopt my perl script to move short tasks to CPU if you want.

[Pepi]

Perl script never work for me ( win 7 64 bit) so I left that script and wait fro CPU2GPU tools
But thanks for answer, maybe I came back to script