Forum > Discussion Forum
When corrupted results get validated...
Jason G:
--- Quote from: Raistmer on 30 Dec 2010, 12:57:50 pm ---What they (project admins) did in those cases? Maybe SETI project can learn from it ?
--- End quote ---
Don't know. Some point of responsibility lies with the 3rd party developers, IMO of course, and as we take pains to improve validation & stability at every step, we endeavour to meet those responsibilities. But let's face it, if erroneous app results can get through 'the system', then so can hardware faults, bad configurations, and sheer vandalism. the 'science' catches that, not validators or mySQL queries (unless relational databases have become more sophisticated than I remember, it's a reduced database, not a knowledgebase ;) Thise are project staff. NTPCKR & RFI systems to handle that further on.)
For our purposes here, I think we need to devalue the integrity of a single detection in our minds, when the reality says it would go through a whole persistence & re-observation process before publication of any WoWness. We don;t need another WoW like signal, we have one of those and it has proven insufficient to scientifically confirm the presence of an extraterrestrial civilisation.
Jason
Raistmer:
BTW, there is another possibility for such long unmaintained host setup.
Sometime host can escape grasp of initial installer. I have such host in my fleet for example. It still produces correct data, but even if it will go wrong - I will not able to do anything with it.
Perhaps host deletion/blocking from SETI web site should be added....
Jason G:
--- Quote from: Raistmer on 30 Dec 2010, 01:13:56 pm ---Perhaps host deletion/blocking from SETI web site should be added....
--- End quote ---
Joking, Automated system to contact ISP, requesting to connect 240 Volts down the cable ? ;D
More seriously, updated version/planclass described earlier should cut work off from that host, though as mentioned I don't know the practicalities of that.
Richard Haselgrove:
--- Quote from: Raistmer on 30 Dec 2010, 12:36:22 pm ---
About "suicide pill" - if it's implemented as library with enough easy to use interface I'm ready to include it in my builds. But have no intentions to develop such thing.
--- End quote ---
When I was asked to produce a 'trial' version of one of my programs, many years ago, I found some shareware which could be applied to the completed, compiled .exe file - a sort of wrapper. That, of course, meant that the trial version of the program was identical to the paid-for version, and the wrapper was completely independent of the development environment used to produce it. But IIRC, it popped up a nag screen saying how many more days it could be used - not advisable for an app with no other UI ::). There were other restriction policies available, but that's the only one I used.
It's only installed on a now-retired development machine - I could fire that up and retrieve it if anyone wants. Similarly, newer/better products should be available?
Jason G:
--- Quote from: Richard Haselgrove on 30 Dec 2010, 01:32:52 pm ---It's only installed on a now-retired development machine - I could fire that up and retrieve it if anyone wants. Similarly, newer/better products should be available?
--- End quote ---
OK, a dumb idea along those lines from me. Induce an update cycle & reset the project (via bonccmd.exe or similar mechanism) if not current.
[Later:] Something looking potentially relevant to today's discussion... NTPCKR seems to be configured to ignore spikes (my guess, nothing more, from the command line).
--- Quote ---+ <daemon>
+ <host>maul</host>
+ <cmd>ntpckr.x86_64 -nospikes -mod 4 0 -hpsd -dayscool 5 -summarize -projectdir /home/boincadm/projects/sah</cmd>
+ <output>ntpckr1.log</output>
+ <pid_file>ntpckr1.pid</pid_file>
+ <disabled>1</disabled>
+ </daemon>
...
<task>
+ <host>maul</host>
+ <cmd>update_candidate_counts.x86_64 -projectdir /home/boincadm/projects/sah</cmd>
+ <output>update_candidate_counts.log</output>
+ <period>1 hours</period>
+ <disabled>0</disabled>
+ </task>
--- End quote ---
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version