And yet I don't remember any other car company being bailed out.

Good god, you are a clown. A sad, angry clown, but a clown nonetheless.

All four major US automakers participated in the auto industry bailout. Ford didn't need it, but wanted capital to develop new technologies to remain competitive against GM

The government gave money to a company that didn't need it. The mind boggles.

, Chrysler, and GMAC, so they got government loans and lines-of-credit instead of TARP funds.

Anyone can take a few seconds to use Google and find out things like this. Anyone but you. I think that you are just an attention whore. Twit.

I'm not interested enough, especially as I don't live in America.

How To Multiple boinc clients on the same computer
Although for the life of me i can't seen any point in doing so.

Only time I've ever thought of doing it was to get around a limit on the server. For example Milkyway will only hand out 900 tasks per client. But since they only hand out 300 per GPU, you'd need a 4th GPU before there was any point.

Although.... it would get around the 10 minute wait as per the can't upload and download at once bug. Run two clients, start the second one when the first one has half used its buffer. One of them would always have work (I did a quick timeline sketch).

-duplicate-

How To Multiple boinc clients on the same computer

Although for the life of me i can't seen any point in doing so.

One idea is to have different cache sizes for the cpu and gpu crunching projects

Yeah, but it still doesn't make any sense to me.
If you run one project, and if they're flaky then you'll set the cache to cover hiccups inline with Task deadlines. If you run multiple projects, then set it to no cache, and your Resource share settings will take care of themselves as work is or isn't available. I just don't see any advantage in making something that really is relatively simple, orders of magnitude more complicated.

Buffers are not simple. Primegrid for example has no idea how long GPU tasks will take. Even after running them for months, I still get tasks saying they will take 250 days when they take 4. So to get 8 days work, I'd need to set the buffer to 500 days. But not for the CPUs. Or not for other projects on the GPU. But yes, you add problems like not being able to prioritise between projects so easily.

I'm still waiting for this alledged rinse.

Awww, isn't that cute? Karen wants some attention. C'mere, Karen, let me scratch you behind the ears. Who's a good boy? YOU ARE!!! Yes you are! Yes you are!

Grow up.

It doesn't matter how many old people die of it, the important thing is how many young people die of it, and that we let them die, so they don't make a weaker next generation.

"[The state] must see to it that only those who are healthy shall beget children; that there is only one infamy, namely, for parents that are ill or show hereditary defects to bring children into the world and that in such cases it is a high honour to refrain from doing so."

You're a real POS, Karen.

Why did you have a problem with that exceedingly good idea? You need to understand the difference between killing people and preventing more undesirables from being born. The second one is not cruel.

[quote]And yet I don't remember any other car company being bailed out.

Good god, you are a clown. A sad, angry clown, but a clown nonetheless.

All four major US automakers participated in the auto industry bailout. Ford didn't need it, but wanted capital to develop new technologies to remain competitive against GM

The government gave money to a company that didn't need it. The mind boggles.

Ford and the others argued it was unfair to give money to one and not the others as it would be seen as the Government supporting one company and not another, they made a compelling argument and got the money. The Government doesn't really care who succeeds as long as jobs aren't lost at which point the Government has to start taking taxpayer money to keep them from being homeless if they can't find new jobs. It's part of the 'too big to fail' thinking as literally MILLIONS of workers would be out of a job overnight if one of them went under, that's bad for politics.

double post

[snip]

Buffers are not simple. Primegrid for example has no idea how long GPU tasks will take. Even after running them for months, I still get tasks saying they will take 250 days when they take 4. So to get 8 days work, I'd need to set the buffer to 500 days. But not for the CPUs. Or not for other projects on the GPU. But yes, you add problems like not being able to prioritise between projects so easily.

I've had no problem getting PrimeGrid to give a good estimate of how long tasks will run once my computer has returned 10 successful tasks for the same version of the sane application, All BOINC projects seem to have problems giving good estimates until they return 10 successful tasks for a particular version, due to the way the estimates are calculated.

Do you have a situation likely to cause problems with this, such as two GPUs of very different speeds on the same computer, both doing tasks of the same type?

I'm seeing some compute errors around "Unable to open constraints file"

<core_client_version>7.16.11</core_client_version>
ERROR: [ERROR] Unable to open constraints file: f506a88e740dc1433a9792f2e819aa3f_0001.MSAcst
ERROR:: Exit from: ......srccorescoringconstraintsConstraintIO.cc line: 457
BOINC:: Error reading and gzipping output datafile: default.out
05:40:41 (2928): called boinc_finish(1)
</stderr_txt>
]]>

Same today.
Please fix this bug

I've finally got round to examining this issue involving "ERROR:: Exit from: ......srccorescoringconstraintsConstraintIO.cc line: 457"
I didn't realise I'd been getting this error as much as everyone else and I've now reported it, probably for the first time, which is likely why it's been going on for so long.
I thought there were two types of error resulting from this, but there are actually three.

The one you quote above gives a gzip error and reports in the task list as a Computation Error - boinc_finish(1) - and usually only has a cpu runtime of 15 seconds or less so awards no credit,
There's another with no gzip error that has a cpu runtime of 3 or 4 minutes and reports a Validate Error - boinc_finish(0) - and awards a few credits when the daily cleanup job runs
The third one also has no gzip error, has a runtime of only 6-9 minutes and reports as Completed and Validated correctly, but obviously doesn't run fully either.

My main PC is reporting 3 Computation errors, 3 Validate Errors and 50 Validating properly, but 2 of them are running short, so 8 of 56 have a problem - 1 in 7.
All bar 3 are awarding credit for runtime - and those 3 for less than a minute of cpu runtime in total across all 16 cores - so it's a far bigger issue for the project than it is for any user, and I've reported it as a project issue on that basis.

---

It doesn't matter how many old people die of it, the important thing is how many young people die of it, and that we let them die, so they don't make a weaker next generation. You can protect the old by shutting them in their homes, but everyone of reproducing age should be allowed to get the virus and see if they're worthy.

[snip]

So you're volunteering to get the virus and see how good your genes are?

I've probably already had it. 80% of us won't get any symptoms.

[snip]

Buffers are not simple. Primegrid for example has no idea how long GPU tasks will take. Even after running them for months, I still get tasks saying they will take 250 days when they take 4. So to get 8 days work, I'd need to set the buffer to 500 days. But not for the CPUs. Or not for other projects on the GPU. But yes, you add problems like not being able to prioritise between projects so easily.

I've had no problem getting PrimeGrid to give a good estimate of how long tasks will run once my computer has returned 10 successful tasks for the same version of the sane application, All BOINC projects seem to have problems giving good estimates until they return 10 successful tasks for a particular version, due to the way the estimates are calculated.

Do you have a situation likely to cause problems with this, such as two GPUs of very different speeds on the same computer, both doing tasks of the same type?

Yes, but only one of the three GPU machines. I have two machines with only one GPU. But I run all the GPU subprojects in Primegrid, if that confuses it. It does with Einstein if you run gamma and gravity. When the timer was designed in Boinc they never anticipated projects with more than one subproject. And it still does it when I'm not doing Primegrid on the CPU for a couple of months, so it's not the interaction with that.

I'm seeing some compute errors around "Unable to open constraints file"

<core_client_version>7.16.11</core_client_version>
ERROR: [ERROR] Unable to open constraints file: f506a88e740dc1433a9792f2e819aa3f_0001.MSAcst
ERROR:: Exit from: ......srccorescoringconstraintsConstraintIO.cc line: 457
BOINC:: Error reading and gzipping output datafile: default.out
05:40:41 (2928): called boinc_finish(1)
</stderr_txt>
]]>

Same today.
Please fix this bug

I've finally got round to examining this issue involving "ERROR:: Exit from: ......srccorescoringconstraintsConstraintIO.cc line: 457"
I didn't realise I'd been getting this error as much as everyone else and I've now reported it, probably for the first time, which is likely why it's been going on for so long.
I thought there were two types of error resulting from this, but there are actually three.

The one you quote above gives a gzip error and reports in the task list as a Computation Error - boinc_finish(1) - and usually only has a cpu runtime of 15 seconds or less so awards no credit,
There's another with no gzip error that has a cpu runtime of 3 or 4 minutes and reports a Validate Error - boinc_finish(0) - and awards a few credits when the daily cleanup job runs
The third one also has no gzip error, has a runtime of only 6-9 minutes and reports as Completed and Validated correctly, but obviously doesn't run fully either.

My main PC is reporting 3 Computation errors, 3 Validate Errors and 50 Validating properly, but 2 of them are running short, so 8 of 56 have a problem - 1 in 7.
All bar 3 are awarding credit for runtime - and those 3 for less than a minute of cpu runtime in total across all 16 cores - so it's a far bigger issue for the project than it is for any user, and I've reported it as a project issue on that basis.

They're already aware of these bad tasks.
Because picking them out will likely take out some good tasks at the same time, and the impact on users is so minimal (if there's any impact at all - my view) they're going to be left to error out rather than distract researchers for little or no benefit to anyone.
So they're not going to be fixed. Just don't worry about them.

---

It doesn't matter how many old people die of it, the important thing is how many young people die of it, and that we let them die, so they don't make a weaker next generation.

"[The state] must see to it that only those who are healthy shall beget children; that there is only one infamy, namely, for parents that are ill or show hereditary defects to bring children into the world and that in such cases it is a high honour to refrain from doing so."
You're a real POS, Karen.

Why did you have a problem with that exceedingly good idea? You need to understand the difference between killing people and preventing more undesirables from being born. The second one is not cruel.

I wasn't going to continue with this pile of drivel thread, but it's worth being very clear what Peter Hucker means by "preventing more undesirables from being born" which "is not cruel" and asks "Why did you have a problem with that exceedingly good idea?"

The Untermensch were primarily Jews, but also Slavs and Romany, Black and Mulatto people. It was these who were explicitly targeted for extermination. For the purpose of genocide, in the way Peter openly describes and promotes.

Whether Peter knows this and denies it, or doesn't know it at all, as he seems to know so little about anything, let no-one be in any doubt what he's saying.

---

he seems to know so little about anything

It could be narcissistic personality disorder, or Asperger's, or maybe just expression from lingering trauma about being taunted as "Peter Sucker" in grade school. Whatever. What IS certain is that he is insulated from reason and is desperate for attention. I already ended attempts at the former and will now deny him the latter.

To everyone fighting in here and calling names: This is bug reporting thread. Please take your argument elsewhere. Nothing you all are posting has anything to do with the point of this particular thread.

foldit5_ Tasks seem to be having considerable issues. I've had 4 Validate, and 18 that are Invalid and all in less than 40 seconds.

For all of them the error is the same-

<core_client_version>7.16.11</core_client_version>
<![CDATA[
<stderr_txt>
command: projects/boinc.bakerlab.org_rosetta/rosetta_4.20_windows_x86_64.exe @foldit5_2010650_c015_global_dock_flags -in:file:boinc_wu_zip asym_dock_foldit5_2010650_c015_data.zip -patchdock foldit5_2010650_c015_patchdock.patchdock -patchdock_random_entry 1 7899 -in:file:s foldit5_2010650_c015_patchdock.pdb -nstruct 10000 -cpu_run_time 28800 -boinc:max_nstruct 20000 -checkpoint_interval 120 -mute all -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -boinc::cpu_run_timeout 36000 -run::rng mt19937 -constant_seed -jran 2808027
Using database: database_357d5d93529_n_methylminirosetta_database

[ ERROR ]: Caught exception:


File: ......srcprotocolsrosetta_scriptsRosettaScriptsParser.cc:1313
Input rosetta scripts XML file "asym_dock_global.xml" failed to validate against the rosetta scripts schema. Use the option -parser::output_schema <output filename> to output the schema to a file to see all valid options.
Your XML has failed validation.  The error message below will tell you where in your XML file the error occurred.  Here's how to fix it:

1) If the validation fails on something obvious, like an illegal attribute due to a spelling error (perhaps you used scorefnction instead of scorefunction), then you need to fix your XML file.
2) If you haven&#226;&#128;&#153;t run the XML rewriter script and this might be pre-2017 Rosetta XML, run the rewriter script (tools/xsd_xrw/rewrite_rosetta_script.py) on your input XML first.  The attribute values not being in quotes (scorefunction=talaris2014 instead of scorefunction="talaris2014") is a good indicator that this is your problem.
3) If you are a developer and neither 1 nor 2 worked - email the developer&#226;&#128;&#153;s mailing list or try Slack.
4) If you are an academic or commercial user - try the Rosetta Forums https://www.rosettacommons.org/forum


Error messages were:
Error: AttValue: " or ' expected

1:  <dock_design>
2: 	<SCOREFXNS>
3: 	   <fullatom weights=talaris2013 symmetric=0>
4: 	   </fullatom>
5: 	</SCOREFXNS>
6: 
7: 	<FILTERS>
8: 		<Ddg name=Isc scorefxn=fullatom threshold=0 jump=1 repeats=1 repack=0 confidence=1/>
Error: attributes construct error

1:  <dock_design>
2: 	<SCOREFXNS>
3: 	   <fullatom weights=talaris2013 symmetric=0>
4: 	   </fullatom>
5: 	</SCOREFXNS>
6: 
7: 	<FILTERS>
8: 		<Ddg name=Isc scorefxn=fullatom threshold=0 jump=1 repeats=1 repack=0 confidence=1/>
Error: Couldn't find end of Start Tag fullatom line 3

1:  <dock_design>
2: 	<SCOREFXNS>
3: 	   <fullatom weights=talaris2013 symmetric=0>
4: 	   </fullatom>
5: 	</SCOREFXNS>
6: 
7: 	<FILTERS>
8: 		<Ddg name=Isc scorefxn=fullatom threshold=0 jump=1 repeats=1 repack=0 confidence=1/>
Error: Opening and ending tag mismatch: SCOREFXNS line 2 and fullatom

1:  <dock_design>
2: 	<SCOREFXNS>
3: 	   <fullatom weights=talaris2013 symmetric=0>
4: 	   </fullatom>
5: 	</SCOREFXNS>
6: 
7: 	<FILTERS>
8: 		<Ddg name=Isc scorefxn=fullatom threshold=0 jump=1 repeats=1 repack=0 confidence=1/>
9: 		<Sasa name=sasa confidence=0/>
Error: Opening and ending tag mismatch: dock_design line 1 and SCOREFXNS

 1:  <dock_design>
 2: 	<SCOREFXNS>
 3: 	   <fullatom weights=talaris2013 symmetric=0>
 4: 	   </fullatom>
 5: 	</SCOREFXNS>
 6: 
 7: 	<FILTERS>
 8: 		<Ddg name=Isc scorefxn=fullatom threshold=0 jump=1 repeats=1 repack=0 confidence=1/>
 9: 		<Sasa name=sasa confidence=0/>
10: 		<ShapeComplementarity name=shape verbose=1  confidence=0 jump=1/>
Error: Extra content at the end of the document

 2: 	<SCOREFXNS>
 3: 	   <fullatom weights=talaris2013 symmetric=0>
 4: 	   </fullatom>
 5: 	</SCOREFXNS>
 6: 
 7: 	<FILTERS>
 8: 		<Ddg name=Isc scorefxn=fullatom threshold=0 jump=1 repeats=1 repack=0 confidence=1/>
 9: 		<Sasa name=sasa confidence=0/>
10: 		<ShapeComplementarity name=shape verbose=1  confidence=0 jump=1/>
11: 	</FILTERS>
12: 
------------------------------------------------------------
Warning messages were:
------------------------------------------------------------

 ------------------------ Begin developer's backtrace ------------------------- 
BACKTRACE:
 ------------------------- End developer's backtrace -------------------------- 


AN INTERNAL ERROR HAS OCCURED. PLEASE SEE THE CONTENTS OF ROSETTA_CRASH.log FOR DETAILS.


DummyMover::apply() should never have been called! (JobDistributor/Parser should have replaced DummyMover.)

ERROR: Function not implemented.
ERROR:: Exit from: ......srcappspublicboincminirosetta.cc line: 101
06:51:32 (4632): called boinc_finish(0)

</stderr_txt>
]]>

---

Grant
Darwin NT

It doesn't matter how many old people die of it, the important thing is how many young people die of it, and that we let them die, so they don't make a weaker next generation.

"[The state] must see to it that only those who are healthy shall beget children; that there is only one infamy, namely, for parents that are ill or show hereditary defects to bring children into the world and that in such cases it is a high honour to refrain from doing so."
You're a real POS, Karen.

Why did you have a problem with that exceedingly good idea? You need to understand the difference between killing people and preventing more undesirables from being born. The second one is not cruel.

I wasn't going to continue with this pile of drivel thread, but it's worth being very clear what Peter Hucker means by "preventing more undesirables from being born" which "is not cruel" and asks "Why did you have a problem with that exceedingly good idea?"

The Untermensch were primarily Jews, but also Slavs and Romany, Black and Mulatto people. It was these who were explicitly targeted for extermination. For the purpose of genocide, in the way Peter openly describes and promotes.

Whether Peter knows this and denies it, or doesn't know it at all, as he seems to know so little about anything, let no-one be in any doubt what he's saying.

You missed my point entirely. I quote directly from just up there: "You need to understand the difference between killing people and preventing more undesirables from being born." If you're an ugly or unhealthy person, not breeding is a good idea. Why put your offspring through being like you? When you say extermination, you're talking about killing those already alive. It's not murder to not be born.

he seems to know so little about anything

It could be narcissistic personality disorder, or Asperger's, or maybe just expression from lingering trauma about being taunted as "Peter Sucker" in grade school. Whatever. What IS certain is that he is insulated from reason and is desperate for attention. I already ended attempts at the former and will now deny him the latter.

Having a different opinion from you is not a medical problem, and I certainly don't seek attention from morons like yourself. And it was phucker actually - first initial plus surname - didn't bother me at all. Quite amusing at primary school when the teacher asked us what our nicknames were. She almost gave me detention. Then again at university the professor thought he was being funny reading out usernames for the computers and sounding them as they were spelt. He didn't stop himself in time.

To everyone fighting in here and calling names: This is bug reporting thread. Please take your argument elsewhere. Nothing you all are posting has anything to do with the point of this particular thread.

Yes mein fuhrer.