plan_class tag
17 Feb 2016 6:53:01 UTC
Topic 198441
(moderation:
I use the tag from boinc to display the "name" of the tasks in my home built monitor program.
For all "old" searches this tag contains a nice short description of the task, but for the new "Gamma-ray pulsar binary search #1" this tag is empty. The beta "Gravitational Wave search O1" only show a short "SSE2" or "AVX".
In the regular boinc manager this is shown in parentheses after the long name in the Application column.
Is it possible to include a short "FGRP1" and "GWO1" (or whatever the correct short name is) in the tag like you do for the "old" searches?
plan_class tag
)
No. The plan_class is used to distribute an application version for different instruction sets (cpu capabilities). It has nothing to do with the search that is done. You need to use the name of the task to determine the search. They are easily distinguishable (needs a bit thinking for FGRP4 and FGRPB1).
Not easily. For FGRPB1 we
)
Not easily.
For FGRPB1 we currently have no need for plan classes (assuming that all host out there by now have SSE).
The O1AS is a short tuning run, and the first where we test AVX support. Currently there is no need to distinguish AVX application versions between applications.
This is different for BRP where BRP6 GPU tasks have e.g. GPU memory requirements different from BRP4, and for a similar reason it was necessary to distinguish between FGRP(3) and FGRP4 plan classes at the transition from FGRP3 to FGRP4.
Adding unnecessary plan classes increases not only configuration and maintenance work, it also increases the possibility for errors.
BM
BM
Alright, guess I have to
)
Alright, guess I have to fiddle with the task name to try to shorten it down.
Thanks for the replies.