Discussion Thread for the Continuous GW Search known as O2MD1 (now O2MDF - GPUs only)
1 Oct 2019 22:54:17 UTC
Topic 219695
(moderation:
This new search for Continuous Gravitational Waves has been foreshadowed in this message. GPU tasks for the new search will be using a new test version (V1.09) of the existing GW GPU app and CPU tasks (unless subsequently announced otherwise) will probably continue using the long running V1.01 CPU version.
Since the V1.09 GPU app is a test version, all tasks will continue to be validated against a corresponding task computed using the CPU app. This is likely to cause some initial delays in the validation process, not only because CPU tasks will take longer to complete but also because of the way that locality scheduling works. It will probably take extra time for a GPU task to receive a CPU task 'quorum partner' for validation purposes. This is just a 'known fact of life' so please be patient :-).
If you wish to comment about versions of the GW GPU app prior to the new V1.09, please use the existing thread for that purpose. Use this thread for comments about V1.09 or later, once it has been launched.
Please realise that tasks for test apps are disallowed by default and that, unless you have already made the change for previous versions, you will need to change your project preferences to 'allow' such tasks. By doing so you need to be aware that test tasks may fail to complete or fail to validate and there are no guarantees of stable and trouble free operation. The project is highly appreciative of those who agree to participate, despite these risks.
Cheers,
Gary.
I have my first three V1.09
)
I have my first three V1.09 validated, along with several of the 1.07s earlier. There are no invalids now.
https://einsteinathome.org/host/12790950/tasks/4/0
Interestingly for me is that my RX 570 (Win7 64-bit) was inadvertently overclocked to 1348 MHz (default 1244 MHz), and undervolted to 1.000 volts (default 1.150 volts). That is the setting I use for MW, and was a bit surprised that it worked here. But that is undoubtedly because the card is lightly utilized (GPU Load 42%). It is runs at 53 watts (GPU-Z) and 51 C. The fan is at 19%. And the work units are about 75 minutes each (1X).
Also, it is fed by two free cores of an i7-4771 and shows 103% CPU usage; all are exactly the same as 1.07, not surprisingly.
There has now been an
)
There has now been an announcement in Technical News concerning the new O2MD1 search. Another potential issue has been identified which might result in a further app change for the GPU version before it is released. This means that the new search will start as 'CPU only' until this is resolved. Please check the above link for current details and expect to see another announcement in due course.
The O2AS search is not affected by this so those wishing to comment on that search using the V1.09 app should do so in the O2AS discussion thread for the time being. Once the further potential issue is resolved and an O2MD1 GPU app is released, feel free to direct any discussion about that to this thread. It may be that the app version remains at V1.09 or there may need to be an amended version. There may not be further advice about the matter until next week, from what has been mentioned so far.
Cheers,
Gary.
O2MD1 v1.01 cpu tasks seem to
)
O2MD1 v1.01 cpu tasks seem to run about 20 % faster than O2AS v1.01 cpu tasks. This applies for both linux and windows hosts.
The tasks would likely have
)
The tasks would likely have different work content since it's a targeted search rather than 'All Sky'. Hopefully, this suggests that the GPU tasks might run faster too, although I guess it depends on which part of the search there is 'less' of - the CPU part or the GPU part :-).
Cheers,
Gary.
I am having no success
)
I am having no success getting any of the new O2MD1 cpu tasks. I have cpu work and beta app work enabled.
Darksider
8144 Einstein@Home 10/4/2019 7:34:37 AM choose_project: scanning
8145 Einstein@Home 10/4/2019 7:34:37 AM can fetch CPU
8146 Einstein@Home 10/4/2019 7:34:37 AM can fetch NVIDIA GPU
Darksider
8213 Einstein@Home 10/4/2019 7:39:19 AM sched RPC pending: Requested by user
8214 Einstein@Home 10/4/2019 7:39:19 AM [sched_op] Starting scheduler request
8215 Einstein@Home 10/4/2019 7:39:19 AM Sending scheduler request: Requested by user.
8216 Einstein@Home 10/4/2019 7:39:19 AM Reporting 1 completed tasks
8217 Einstein@Home 10/4/2019 7:39:19 AM Not requesting tasks: don't need (CPU: job cache full; NVIDIA GPU: job cache full)
8218 Einstein@Home 10/4/2019 7:39:19 AM [sched_op] CPU work request: 0.00 seconds; 0.00 devices
8219 Einstein@Home 10/4/2019 7:39:19 AM [sched_op] NVIDIA GPU work request: 0.00 seconds; 0.00 devices
8220 Einstein@Home 10/4/2019 7:39:22 AM Scheduler request completed
I have no cpu work on the host at all. So why does the client say the cpu cache is full?
The server status page shows over 8000 cpu tasks available for O2MD1.
What's up?
Just checking... Have you
)
Just checking... Have you selected the "Gravitational Wave search O2 Multi-Directional" on the applications list (project preferences page) ?
Yes.Run only the selected
)
Yes.
Gravitational Wave search O2 Multi-Directional is checked. This is what my last connection reply showed. ??
Why is it stating no app version is available. The applications page shows one for Linux running on an AMD x86_64 or Intel EM64T CPU version 1.01
In
)
In preferences|Project|Resource settings
So you have Use CPU selected?
In Other settings, so you have
Run CPU versions for which GPU versions are available selected?
Yes.
)
Yes.
Do you use app_config.xml ?
)
Do you use app_config.xml ? Have you added there lines for 'einstein_O2MD1' ?