My task list here says the tasks I got this morning are the x86_64 64 bit tasks. Yet, my tasks properties say they are i686 tasks. Why is that? Or is it that the tasks are intelligent and decide which app is gonna crunch them? lol ;) Or is it that the server itself does not know which app is gonna crunch the tasks so it shows the better of the 2? lol ;)

Something else I don't quite understand is why, if I'm running a 64 bit processor and a 64 bit OS (Linux Mint), do I run a 32 bit app for these tasks?

I may be out of date, but my understanding is that <all> tasks are 32-bit but some/many have a 64-bit wrapper.
I could easily be wrong - this isn't my strong point at all and lots of things have changed recently.

---

I noticed the other day that some completed tasks showed they were x86_64 in the WU header, but then in the WU output, you could see that the command used ran a i686.exe. So yes, it seems the WU itself doesn't care which app is used.

Do let us know if project reset gets predictable control of the app. I've been concerned about how this cc_config alt_platform stuff is going for Linux folks.

---

Rosetta Moderator: Mod.Sense

I noticed the other day that some completed tasks showed they were x86_64 in the WU header, but then in the WU output, you could see that the command used ran a i686.exe. So yes, it seems the WU itself doesn't care which app is used.

Do let us know if project reset gets predictable control of the app. I've been concerned about how this cc_config alt_platform stuff is going for Linux folks.

DK tells me they found a server-side change that they've implemented that should help machines get the app. desired. Please continue watching and reporting.

---

Rosetta Moderator: Mod.Sense

Greetings,

Well one thing is fer sure. I have eliminated the tasks running in high priority doing what I am doing.

Now I'm waiting for my last 8 to finish so I can reset the project and hopefully rid myself from the use of the i686 app. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings;

Is this [marked **] a cause for concern?

<core_client_version>7.14.2</core_client_version>
<![CDATA[
<stderr_txt>
command: ../../projects/boinc.bakerlab.org_rosetta/rosetta_4.15_i686-pc-linux-gnu -run:protocol jd2_scripting -parser:protocol jhr_boinc_v3_cart.xml @flags -in:file:silent Junior_HalfRoid_design4_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_6lv4ll1f.silent -in:file:silent_struct_type binary -silent_gz -mute all -out:file:silent_struct_type binary -out:file:silent default.out -in:file:boinc_wu_zip Junior_HalfRoid_design4_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_6lv4ll1f.zip @Junior_HalfRoid_design4_cart_COVID-19_SAVE_ALL_OUT_IGNORE_THE_REST_6lv4ll1f.flags -nstruct 10000 -cpu_run_time 28800 -watchdog -boinc:max_nstruct 1000 -checkpoint_interval 120 -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -run::rng mt19937 -constant_seed -jran 1834344
**Starting watchdog...
**Watchdog active.
**Starting watchdog...
**Watchdog active.
**Starting watchdog...
**Watchdog active.
BOINC:: CPU time: 29394.3s, 14400s + 14400s[2020- 4-18 20:59:37:] :: BOINC 
**WARNING! cannot get file size for default.out.gz: could not open file.
**Output exists: default.out.gz Size: -1
InternalDecoyCount: 0 (GZ)
-----
0
-----
Stream information inconsistent.
Writing W_0000001
======================================================
DONE ::     1 starting structures  29394.3 cpu seconds
This process generated      1 decoys from       1 attempts
======================================================
20:59:37 (2109): called boinc_finish(0)

</stderr_txt>
]]>

This is one of the 20 credit tasks. The non-20 credit tasks do not show as the [**] marked stuff above.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Normal tasks should show the starting watchdog, watchdog active. And there is usually a "watchdog shutting down". Which I have always found confusing, because it just means that at the end of the work unit, that the watchdog is ending, it does not mean the watchdog is ending the computation of the WU.

However...

BOINC:: CPU time: 29394.3s, 14400s + 14400s

This indicates that the watchdog did step in and end this thread. It may be an example of why they are extending the watchdog to 10hrs rather than the 4 hours (14400 seconds) you saw here.

---

Rosetta Moderator: Mod.Sense

Greetings,

It worked! It really, really worked!!! :)

I emptied my cache and reset the project. I got new tasks and set NNT. The ones running are using the x86_64 app. :) I got back from running World of Warcraft and all tasks continued were they left off. I also increased the CPU cores used to 9 and saved the others for SETI. :)

Thanks to all for the help. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Is the project out of COVID19 work? About 3 weeks ago I rejoined this project after several years away. I presently have 12 cores on 3 machines running Rosetta and up till now I have been getting about 40% COVID19 WU’s. In the last 12 hours all new work has been non-COVID WU’s. Are they all gone? Will there be more?

---

Is the project out of COVID19 work? About 3 weeks ago I rejoined this project after several years away. I presently have 12 cores on 3 machines running Rosetta and up till now I have been getting about 40% COVID19 WU’s. In the last 12 hours all new work has been non-COVID WU’s. Are they all gone? Will there be more?

COVID work comes and goes as researchers submit jobs, they get crunched, and then they look at the results to determine what the next best course of action is. There will most likely be more at some point once they determine what they next need to study.

Should be noted that all research here (even when not specific to COVID) involves principles that can possibly apply to COVID research, so just because you don't see "Covid" in the job name, doesn't mean you aren't doing immensely helpful work.

Is the project out of COVID19 work? About 3 weeks ago I rejoined this project after several years away. I presently have 12 cores on 3 machines running Rosetta and up till now I have been getting about 40% COVID19 WU’s. In the last 12 hours all new work has been non-COVID WU’s. Are they all gone? Will there be more?

COVID work comes and goes as researchers submit jobs, they get crunched, and then they look at the results to determine what the next best course of action is. There will most likely be more at some point once they determine what they next need to study.

Should be noted that all research here (even when not specific to COVID) involves principles that can possibly apply to COVID research, so just because you don't see "Covid" in the job name, doesn't mean you aren't doing immensely helpful work.

Agree with this very much. I consider the non-COVID-specific tasks even more important as they'll benefit COVID tasks and whatever the next one is down the line.
I didn't even notice tasks with COVID in the name had reduced (they have). Plus, just because they don't have COVID in the name, that doesn't make me think they're non-COVID. It's just a name.

---

Greetings,

Since I started I had not seen a "Validation pending"... until this morning! Woohoo! :) I have 1.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Quick question about changing work time. I have a few 24/7 machines running. Will changing my time setting affect RAM use? For example currently my 8 core machines seem to crunch fine with 16 or 32GB of ram using the default 8hour time limit. I never get "Waiting for memory" notices on them. If I swap them to 24hr tasks will they use 3 times the RAM since the tasks now will run ~3 times longer? Or will RAM use remain about the same even though time to complete has tripled?

/edit I would drop my work cache down to 0 for these machines, so basically 1 in when 1 goes out, but they would hit the server less since each task would take a day to complete.

Memory usage does not increase with WU runtime

---

Rosetta Moderator: Mod.Sense

Greetings,

Here's a good question for y'all:

I have 8 tasks on my Error list. 6 of those tasks have credit attached them. How is that possible?

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

We are awarding credit now even for jobs that were canceled, with errors, and invalid.

---

We are awarding credit now even for jobs that were canceled, with errors, and invalid.

Awarding credit for Validation errors makes sense as it's not the fault of users if jobs completed but something went wrong at validation.

And for those jobs with Computation errors it may be, but just as often isn't, an error on the host system, so again it seems right credit is awarded for the CPU time completed.

What I didn't expect, but actually makes sense now I think about it, is what looks like a default 10 credits being awarded for jobs cancelled by server.
Meaning they've been downloaded in good faith but, for some reason at the project end, need to be withdrawn before running. That shows good will at least.

If you carry on like this, there'll be nothing for us to moan about. Fair play.

Wondering what to do with myself now...

---

We are awarding credit now even for jobs that were canceled, with errors, and invalid.

Hi Admin,

Thanks! That answers my question. :)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Holy moley! What is up with this task? That is a BOAT load of errors!

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Uh oh! I believe I just discovered a problem:

Ok, I cannot figure out how to copy/paste from the tasks tab in BOINC. CTRL-C does not work and there is no pop up that shows when right clicking. So I will have to do my best to explain what I found.

I have 9 tasks running. Tasks 2 through 9 are showing the progress bar with various %s and I can see the numbers increase as they run. The 1st, however, seems to be stuck in a causality loop. It's been running for 2 hrs and 48 mins yet the progress bar is showing 0.455%. Task #2 has been running 10 minutes less than #1 and is at 53%. Do I need to abort task #1 or should I just let it run to see what happens?

Here we go, thought of another way to show:

The estimated remaining time is not decreasing either.

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

Greetings,

Well, I just discovered something new about that task that is not showing any progress:

It is showing a minute increase in progress. It's gone from 0.455% to 0.457%. And that remaining estimate has taken off. It is going UP. It is currently at 38 days 3 hours and counting.

This is weird! It should be running in PANIC mode since the deadline is this Friday May 1st. Should I abort or hope it settles down?

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr XO
USS Vre'kasht NCC-33187

"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath