Development for LHC@home

The different runtimes of the scientific apps most likely cause a pitfall regarding the use in a production environment, especially if volunteers also participate in other projects.


Reason
Out of experience (e.g. SixTrack) we know that variable runtimes/CPU-times do not only result in credit variations (much too low <--> much too high).
They also result in a wrong runtime estimation. This is a minor problem if the estimated runtime is too long as the BOINC client would simply request fewer tasks.
It could become a major problem if the estimated runtime is far too low as the BOINC client would request lots of tasks that will hardly/never meet their due dates or block other tasks/projects.


Measure
As the <rsc_fpops_est> value is a major factor used to calculate the estimated runtime, this value must be set by the server as precise as possible.
This has to be done individually for each scientific app, e.g. Herwig, Pythia, Sherpa ...

Measure
As the value is a major factor used to calculate the estimated runtime, this value must be set by the server as precise as possible.
This has to be done individually for each scientific app, e.g. Herwig, Pythia, Sherpa ...

This should be possible.

Just for reference, here is a list of job types that I found.

epos
herwig++
herwig7
herwig++powheg
madgraph5amc
phojet
pythia6
pythia8
sherpa
vincia

Just for reference, here is a list of job types that I found.

agile-runmc??
It's currently running on one of my VMs.

What happens when one catch an endless running Sherpa job?

Will it be killed after xx hours runtime? -- without granting credits ;-(