Hopefully the admins will get around to a libc215 version of the O2AS20 app at some point.
It is there, but seems not to be sent. Probably that's a scheduler bug. I've just changed my libc setting, just to see if it's evaluated the wrong way.
@Markj
You're running debian stretch which is using glibc 2.24. This works with the "native" application.
I'm running debian sid/buster, which would require the LIBC215-version to be used.
i tried Buster on one machine with a GTX1660Ti. It stalled at boot and refused to give the desktop or login prompt after I installed Nvidia-kernel-dkms. It’s not ready for regular use. You can install Stretch and use Stretch-backports to get more up to date packages like the 4.19 kernel without having to use a beta version of the OS.
Thanks, the libc215-version is running well on my side and all 24 tasks were validated successfully so far.
Just one thing: the search progress on the server status page seems to have wrong values for O2. FGRPB1G values are also a bit dodgy, it always shows 0.5 days left.
Is O2AS20-500 looking for specific frequency ranges which are expected to contain signals, or is it a broadband search covering the entire spectrum?
What is the expected duration of this run?
O2AS20-500 is a complete 'blind' search in O2 data, i.e. all-sky (hence the "AS") continuous frequency range (originally 20-500Hz, now partially extended a bit beyond 500Hz). It will continue to run for a few months.
There is another analysis where we specifically look to recover injected signals. We started this yesterday as 'Beta test', it's called "O1OD1I" an will use GPUs Apps. It will consist of three "charges" or "instances" with different injection parameters, each one is targeted for a couple of weeks.
MarkJ schrieb:Hopefully the
)
It is there, but seems not to be sent. Probably that's a scheduler bug. I've just changed my libc setting, just to see if it's evaluated the wrong way.
floyd wrote:I've just changed
)
No difference.
With "vsyscall=emulate"
)
With "vsyscall=emulate" boincmgr doesn't start anymore.
I'll just disable O2 until it's fixed.
Is there a reason the O2
)
Is there a reason the O2 tasks are being sent with a 1 week deadline instead of the normal 2 weeks?
Stef wrote:@MarkjYou're
)
i tried Buster on one machine with a GTX1660Ti. It stalled at boot and refused to give the desktop or login prompt after I installed Nvidia-kernel-dkms. It’s not ready for regular use. You can install Stretch and use Stretch-backports to get more up to date packages like the 4.19 kernel without having to use a beta version of the OS.
BOINC blog
Sorry, was away last week
)
Sorry, was away last week weith less internet than expected.
Plan class LIBC215 should work now, O2AS deadline back to 14d..
BM
Bernd Machenschalk wrote:Plan
)
Thanks Bernd, I can confirm its now giving out the lib215 version and deadline has indeed gone to 2 weeks.
BOINC blog
Thanks, the libc215-version
)
Thanks, the libc215-version is running well on my side and all 24 tasks were validated successfully so far.
Just one thing: the search progress on the server status page seems to have wrong values for O2. FGRPB1G values are also a bit dodgy, it always shows 0.5 days left.
Is O2AS20-500 looking for
)
Is O2AS20-500 looking for specific frequency ranges which are expected to contain signals, or is it a broadband search covering the entire spectrum?
What is the expected duration of this run?
O2AS20-500 is a complete
)
O2AS20-500 is a complete 'blind' search in O2 data, i.e. all-sky (hence the "AS") continuous frequency range (originally 20-500Hz, now partially extended a bit beyond 500Hz). It will continue to run for a few months.
There is another analysis where we specifically look to recover injected signals. We started this yesterday as 'Beta test', it's called "O1OD1I" an will use GPUs Apps. It will consist of three "charges" or "instances" with different injection parameters, each one is targeted for a couple of weeks.
BM