The project progress listings page is currently static. Consider getting data from JSON and also include progress on the same page so that progress for all projects can be seen on a single page.

This would require completion calculations to be copied or moved from the Javascript into the current project specific JSON files and then aggregated into a summary JSON file.

When a project is terminated early (before all WUs are assigned) due to any number of reasons, to get the % complete to 100, a skipped flag needs to be added at the project level (manual entry into project json).

There is currently one at the clone level that handles this. This can be retained and replicated at the project and run levels. I'm not 100% sure if certain clones or runs are yanked or the decision is made at the project level but it would be trivial to add support in all 3 levels.

Suggested by PantherX -- TPF can handle Copy/Paste from FAHControl and also HFM since manually typing it can take too long. Thus, it would be one field instead of two.

Use digit grouping (separators) for displaying atom counts and credits.

Note: Ensure sorting isn't impacted.

Suggestion from bruce:

For projects that have Completed WUs and Remaining WUs it might fill it a date of the last completed WU but a clicking link to collect that information is probably a better idea than pre-searching for each one.

Suggestion from bruce:

Since I happen to be interested in why or how badly the WUs failed/aborted/etc. my first action was to click on the ⚠️.
The only place we can gather information beyond what you've presented i https://apps.foldingathome.org/wu
It probably makes sense to have links to that URL, passing it the PRCG numbers directly from an item of interest

Suggested by PantherX - Would it be possible to start of with 3 rows and an option to add additional? That way, the interface is compact but can be expanded for those that have multiple clients.

Use query parameters to show filtered list of active/ public/ beta projects

It would be useful to have URL query parameters pre-populate form fields (such, targetPPD1=1000000, targetPPD2=800000 etc.). Users can bookmark links with these parameters to avoid having to enter values for their clients repeatedly

Some projects have a number of runs/ clones resulting in large table. While paginating is one option to be considered, it'd also be good to have the headers be "sticky" to know what the columns represent when you've scrolled quite a bit.

Suggestion from bruce:

"On the top page, I think you want to add a column for Aborted WUs. (The headings can be two lines to make more horizontal room)"

Rounding of % completion leads to misleading indicators of completion.

Use digit grouping (separators) for display. Suggested by PantherX

Wrap long column headers to make columns (e.g., Length of trajectory (ns)) fit better.

Consolidate active, public, beta flags into a single "status" column. Also add support for internal projects

Consider proritising columns (especially in project summary overview) so that only the most important columns are shown by default when screen sizes do not permit all columns to be displayed without horizontal scrolling.

The invisible columns would need to be made visible based on user selection if they wish to see the not-so-important details.

The current participating orgs page is a static hand-coded page that arose out of a handful of entities. As we now have close to 50 orgs, and there is a need to insert breaks for responsive cards, this needs to be generated dynamically. Consider a js solution that reads content from a json file.

Need a way to handle runs with large number of clones better in the graph. For example, p16801 has 1000 clones per run and the chart is a wall of green.

Suggestion from muziqaz:

There might be some questions from eagle eyes when 95% completed project gets new batch of WUs generated, and project now is reported as 70% completed, even though an hour ago it was 95%. Maybe add a count of new added WUs in past day or hour or something 🙂 if possible, obviously

Suggestion by toTOW:

You could add a FAQ item explaining that by nature of FAH project can be extended

Suggested by PantherX - Manually entering a deadline seems too much work, how about, entering the Project number would automatically fetch that data for you? It can be in real-time. An option to manually override the deadline that was automatically fetched would be cool.