Hi all,

There has been some reports of validation inconclusive issues occurring with the Nbody workunits. It seems to be isolated to the nbody app. I believe this coincided with a database issue on our end. I am working on resolving the issue.

Thank you for you patience and continued support,
Sidd

Thank you for the heads up!!

Yea, about 95% of tasks are inconclusive valid. I waiting to solve to solve this. :)

Yea, about 95% of tasks are inconclusive valid. I waiting to solve to solve this. :)

Te unsent problems are back though! I have a whole page of workunits I finished that are unsent to a 2nd pc!!

I have many tasks computed by me and the second compute is "Canceled by server" or "Unnecessary" or "unsend".

I think tha the unsend one is mater of time...

I have many tasks computed by me and the second compute is "Canceled by server" or "Unnecessary" or "unsend".

I think tha the unsend one is mater of time...

Yes it does seem to have caught up again for me, I do not like these ongoing problems they seem to be having.

I have ~1,500 inconclusive wu's now. If not resolved soon I will have to move over to another project. Any updates?

---

And I just noticed I'm building up inconclusives for the MilkyWay@Home app, not just the N-Body, as was the case in the last couple of days.

---

I have ~1,500 inconclusive wu's now. If not resolved soon I will have to move over to another project. Any updates?

At least mine aren't 'unsent" anymore!! I still have 78 of them after not returning any workunits since last night, I had about 130 then with almost all of them "unsent". I going to resume crunching on my one machine I have here and see how bad it gets when I check later on. With the 10 day or so time frame and only getting 80 workunits at a time I can suspend MW whenever it gets too many "inconclusive" and within that too many "unsent" workunits.

Hi all,

Can you please list some of the workunits that are marked as inconclusive and unsent?


Thanks,
Sidd

How about this?

Task- - - - - - - -Work unit
1555379414 1555377127
2214992488 1555377227
2214990445 1555375193
2214990446 1555375194
2214988358 1555373133
2214988359 1555373134
2214949997 1555335629
2214949998 1555335630
2214949999 1555335631
2214950079 1555335711
2214947692 1555333328
2214947701 1555333337
2214945106 1555330913

Can you please list some of the workunits that are marked as inconclusive and unsent?

For me, the N-Body inconclusives are clearing out nicely. It seems now that it's the MilkyWay@Home app that's lagging. Recent examples:

1560210075
1560204482
1560197795
1560195886
1560188186

---

Hi all,

Can you please list some of the workunits that are marked as inconclusive and unsent?


Thanks,
Sidd

I have a fricking page full of them!!!

1560426341
1560321565
1554916207
1560425463
1560279897
1560226938

I could go on and on but if they are showing up that way for me WHY can't YOU see them too? Validation inconclusive (132)

For me, the N-Body inconclusives are clearing out nicely. It seems now that it's the MilkyWay@Home app that's lagging...

Looks like progress is being made. All of my inconclusives have wingmen now.

---

Hi all,

Can you please list some of the workunits that are marked as inconclusive and unsent?


Thanks,
Sidd

Thanks Sidd for looking into this.It appears my wu's are clearing up as well.

---

whole day and until now i can not log in here or read.. database error. but some like this i see sometimes from autumn 2017 and last 1 month nearly every day .
if they work on database WHY not annoucment like other project?
Or "half failure state" on this project is new "normal" ??
turn project to beta or alfa state

For me, the N-Body inconclusives are clearing out nicely. It seems now that it's the MilkyWay@Home app that's lagging...

Looks like progress is being made. All of my inconclusives have wingmen now.

Mine appear to be also but then I have crunched any new ones since yesterday either! This is a royal pain having to babysit this project, I lost over 500 completed workunits during the last database crash and I'm very hesitant to let that happen again. I assume they are trying but something isn't working.

I own a measly laptop and have been trying to contribute what i can using the decent computation , but the Nbody tasks have interesting properties where at least half tend to get 'caught' in their own processing, to the state where after a day of running, they claim they will be done in two days, or on occasion get trapped for a few days and report a completion time beyond the reporting time.

Is there a way to allow these processes that literally get stuck at a certain component to automatically abort and report the troublesome step or stage to you guys to permit improvements to the code?
As of right now if after a few hours the time remaining starts ballooning i abort manually as there is no way that a 95% complete process that has been running for 2 hours should still be at 95% completion an hour later, which is something i have witnessed.
I note that Bio-inc doesn't even notice when the predicted time to completion ends up beyond the report time and cancel the process then. which is what was previously happening to Nbody before i started manually monitoring it's progress.
I don't know why Nbody is doing this, but i have offered plenty of memory (which it hasn't used) it steadily reduces the CPU usage as it jams up and bioinc has access to a few gigs of storage which it has barely scratched while doing this computation, so i am puzzled if the issue is a bottleneck or a crashing component.

Anything going to happen to the inconclusive.... Cancelled Results?

some of the 35 I have

workunit 1551469684
workunit 1555077585
workunit 1555224430
workunit 1555253384
workunit 1555405588

I own a measly laptop and have been trying to contribute what i can using the decent computation , but the Nbody tasks have interesting properties where at least half tend to get 'caught' in their own processing, to the state where after a day of running, they claim they will be done in two days, or on occasion get trapped for a few days and report a completion time beyond the reporting time.

Is there a way to allow these processes that literally get stuck at a certain component to automatically abort and report the troublesome step or stage to you guys to permit improvements to the code?
As of right now if after a few hours the time remaining starts ballooning i abort manually as there is no way that a 95% complete process that has been running for 2 hours should still be at 95% completion an hour later, which is something i have witnessed.
I note that Bio-inc doesn't even notice when the predicted time to completion ends up beyond the report time and cancel the process then. which is what was previously happening to Nbody before i started manually monitoring it's progress.
I don't know why Nbody is doing this, but i have offered plenty of memory (which it hasn't used) it steadily reduces the CPU usage as it jams up and bioinc has access to a few gigs of storage which it has barely scratched while doing this computation, so i am puzzled if the issue is a bottleneck or a crashing component.

Some people have said if you suspend then resume them they finish right up.