Good choice. I only found 7.16.3 and while it has some extra settings to use, it seems to fall out of memory a lot and even when it's running it seems to suspend itself when it's not the foreground task.
Not recommended at all. Having adjusted my Android settings, I'm thinking of downgrading again

It's working perfectly on my phone. Only one tiny problem - if you expand a task for details, you cannot unexpand it. But so what, I can just select "tasks" view again and it collapses them.

I'd much rather use the very latest version (Beta or not) of every program.

But you would probably be fine downgrading to the official version now, since LHC and Rosetta (and presumably Numberfields) have fixed it at their end.

The directory structure has to be maintained and I am not aware of any way to create a directory in the project directory and keep it sticky. Can we extract into the project directory without the client cleaning it up? Any solution will require an application update, and to my knowledge a solution can be developed but would most likely require a BOINC client update.

== File references ==

The BOINC client uses the following directory structure:



Each project has its own '''project directory''' where its file reside.
The names of files in this directory are physical names.

Each job executes in its own '''slot directory''' ({{{slots/0}}}, etc.).
The slot directory contains links to the job's input and output files.
The name of each link is a '''logical name'''.
(These links aren't symbolic or hard links, because Windows doesn't have them;
rather, they're XML files containing the path of the file in the project directory).
Applications call a BOINC API function [BasicApi#filenames boinc_resolve_filename()]
to map logical names to physical names prior to opening them.

This architecture provides two advantages:

* Multiple concurrent jobs can access a given file without having separate copies of it.
* Applications can contain hardwired (logical) file names, but can be run against different physical files.

The way a job uses a file is called a '''file reference''',
and is specified in [JobTemplates job input and output templates].
A file reference includes the logical name.
It can also specify a '''copy file''' attribute;
if present, the linking mechanism described above is not used;
rather, the BOINC client copies the file from the project directory to
the slot directory before running the application (for input files)
or copies the file from the slot directory to the project directory
after running the application (for output files).
This mechanism is needed for
[WrapperApp legacy applications]
that don't use BOINC's API functions.

Indeed this is not efficient but there currently is no easy workaround that we know of since Rosetta is dependent on the database directory structure. If anyone knows of an easy workaround, I'm all ears. The Rosetta application depends on the database directory structure. This database holds all the required score, chemical, sampling, rotamer, etc. parameters and libraries that are the backbone of all the computations and a result of many years of research and development. These parameters may or may not change with application updates. For example, for the COVID-19 specific jobs, we had to significantly increase the size of the database to include an improved local protein structure fragment library in addition to side chain motif libraries to enable the interface design protocol. These are parameters/libraries that have been developed and continue to be developed in the lab through careful analysis and research of native protein structures and molecular structures in general.