In the #RESQUE evaluation scheme („Research Quality Evaluation scheme for psychological research“), there is an indicator for publications: “Correctness of computational results has been independently verified“.
With CODECHECK, you can request and upload a verification certificate. This gives you "extra points“ in our evaluation scheme, as this is a real quality criterion.
#researchAssessment #CoARA @aufdroeseler https://nerdculture.de/@aufdroeseler/116165190898955396
Three Special Teams Formed To Rescue Injured Tusker After It Goes Rogue In Chandaka
Three Special Teams Formed To Rescue Injured Tusker After It Goes Rogue In Chandaka #injuredelephant #chandaka #forestdepartment #resque #odisha #otvnews #otvenglish --------------------------------------------------------------------------------------------------------- OdishaTV is Odisha's no 1 News Channel. OTV being the first private satellite TV channel in Odisha carries the onus…
I learned from @PLOSBiology about the Research Evaluation System for Quality Evaluation #RESQUE, which provides guidelines for responsible research evaluation:
https://doi.org/10.1371/journal.pbio.3002553
The RESQUE system was originally developed for psychology, but the creators are confident that it can be applied to other fields:
👉 https://nicebread.github.io/RESQUE/
Happy are those scientometrcans who not only have what to measure, but also what to measure)
Researchers would be more willing to prioritize research quality over quantity if the incentive structure of the academic system aligned with this goal. The winner of a 2023 Einstein Foundation Award for Promoting Quality in Research explains how they rose to this challenge.
@davetron5000 @Damax Not #MySQL; it's no longer fully #FOSS, but #MariaDB is. You'd have to look at #resque yourself before deciding to fork it, fix it, find alternatives, or build something new. I don't have the strong opinion you do about that, but will assume that someone gave it more than a passing thought.
New isn't always better, but neither is it inherently #NIHsyndrome. Nothing prevents using other #DBs, #ORMs, or #queues if willing to forego #conventionoverconfiguration.
Blogged: Jitter to the start time of your #resque jobs in #ruby
https://blog.gripdev.xyz/2023/08/21/ruby-resque-jobs-and-jitter-with-resque-scheduler/
@mat We are using Postgres. We were on a mix of #DelayedJob and #Resque, but recently totally replaced Resque with #Sidekiq. We're migrating DJ jobs over as we need to/touch them in any significant way.
We've moved everything to latency-based queues - Sidekiq and DJ both - and it's been a great change!
It's been years since I last used #DelayedJob. Like, the early 2010's or so? Back then it was a mix of DJ and #Resque. Then #Sidekiq came on the scene, I moved over pretty quickly.
Anyhow, the point is, I was under the impression that DelayedJob doesn't have a mechanism to recover from jobs that crash/SIGKILL’d (like, think OOM or something). And to be fair, DJ itself doesn't. But the ActiveRecord backend does, though it's not really advertised. https://github.com/collectiveidea/delayed_job_active_record/blob/97f26a3e1b82b338cd8270aad988c75b82ea5c86/lib/delayed/backend/active_record.rb#L57
Felix Schönbrodt
odnewsin
Serhii Nazarovets
Todd A. Jacobs | Rubyist
lawrencegripper
Steven Harman
kradtour