Post disappeared

[arisu]

I wrote a post about a 15400 WU suffering a velocities blowing up error, complete with details. It's not a testing WU and was folded on a machine that retrieves beta WUs at most. The post disappeared and the forum claims there is no record of it.

Was it removed intentionally or is there a problem with the database?

[Joe_H]

It was merged with the existing topic you failed to see. Use the Your Posts link.

[arisu]

Oh! Thank you, I didn't notice that. I wish it displayed a message about being moved instead of just saying the topic was gone. Sorry for the noise!

Because it wasn't in the summary json file, I couldn't see if it was in beta. I should have looked harder!

[Joe_H]

First check the beta forum by project number and see if it has been listed as moved to FAH. Second, the usual summary list only shows those projects which are on FAH. Beta are listed separately the last I checked. There is a separate Project Summary for Beta, I would have to look up the link.

[arisu]

I haven't seen a separate project summary for beta. At least all the beta projects I've seen have been listed in it (with beta set to true in the json). I wrote a tool that gives me info about a project using the summary file and only internal WUs and old removed or disabled WUs don't exist in the summary file.

This is all I saw from my own tool:

Code: Select all

$ apps psummary 15400
Manager:     Adrija Dutta
Contact:     Unknown
Institution: UIUC
URL:         None
Cause:       cancer
Series:      15400
Work Server: Unknown
Core:        Unknown
Base credit: Unknown
Atoms:       Unknown
Timeout:     Unknown
Deadline:    Unknown
Beta:        Unknown
Public:      Unknown

**PFAS are contaminants in water that are toxic and can cause several adverse
health effects. We are studying interactions between polymer molecules and
PFAS ions and expect these studies to benefit PFAS remediation efforts.**

Usually if it's beta it will say Beta: True. Maybe the project just happened to be disabled when I checked.

Thanks for migrating anyway, I can't believe I didn't just check the beta forum first.

[muziqaz]

I received the notification about that thread, but when I clicked on the link it returned an error.

As a side note, any bad WU related issues you might encounter, report them in Slack, as that is direct line to all researchers, who rarely read forum, if ever. This is valid for any projects, new or old.

[BobWilliams757]

I received the notification about that thread, but when I clicked on the link it returned an error.

As a side note, any bad WU related issues you might encounter, report them in Slack, as that is direct line to all researchers, who rarely read forum, if ever. This is valid for any projects, new or old.

Speaking only for myself, I've never been given access to the slack channel. I was under the impression it was reserved for internal beta testers, devs, and researchers only. If it's available to all beta testers I could use the channel information so I can get on it.

Also, if you could clarify whether this particular instance only applies to bad work units in beta or work units that are out of beta.


If you and the other internal testers or long-term volunteers would feed me information I'd be glad to write up a post that we can use for a forum sticky and also on the discord. It would help make sure everybody is working on the same page and the overall process is a bit more efficient.

[muziqaz]

I received the notification about that thread, but when I clicked on the link it returned an error.

As a side note, any bad WU related issues you might encounter, report them in Slack, as that is direct line to all researchers, who rarely read forum, if ever. This is valid for any projects, new or old.

Speaking only for myself, I've never been given access to the slack channel. I was under the impression it was reserved for internal beta testers, devs, and researchers only. If it's available to all beta testers I could use the channel information so I can get on it.

Also, if you could clarify whether this particular instance only applies to bad work units in beta or work units that are out of beta.


If you and the other internal testers or long-term volunteers would feed me information I'd be glad to write up a post that we can use for a forum sticky and also on the discord. It would help make sure everybody is working on the same page and the overall process is a bit more efficient.

It is only for Internal testers
The reason I asked arisu to post to Slack, is because their issue would not be solved by anyone here. Any broken WUs, server issues, should be reported to the most direct channels possible. For Public donors: it is here, by creating a thread, or Discord. Beta testers: beta section of this forum (in project's thread). Internal testers: Slack

[arisu]

First check the beta forum by project number and see if it has been listed as moved to FAH. Second, the usual summary list only shows those projects which are on FAH. Beta are listed separately the last I checked. There is a separate Project Summary for Beta, I would have to look up the link.

Maybe the post shouldn't have been migrated, because it appears 15400 is not in beta. It just never got announced when it was moved to full FAH.

Code: Select all

Python 3.11.2 (main, Apr 28 2025, 14:11:48) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import requests
>>> r = requests.get('https://assign1.foldingathome.org/api/project/summary').json()
>>> [p for p in r if p['id'] == 15400][0]['beta']
False
>>> [p for p in r if p['id'] == 15400][0]['public']
True
>>>

Speaking only for myself, I've never been given access to the slack channel. I was under the impression it was reserved for internal beta testers, devs, and researchers only. If it's available to all beta testers I could use the channel information so I can get on it.

It is reserved for the internal team and researchers as muziqaz says. I'm an internal tester which is they only reason I have access to it.