-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
List all linked out files in a single new table. #2
Comments
Currently, all input data is listed in Localization density is an output from the I/H modeling and relates to the molecular system and the ensemble of good scoring models obtained from the modeling. Localization densities can be included as Gaussian mixture models in Sequence alignments corresponding to the starting structural models can be included via Modeling scripts, associated documentation and other workflow-related files can be referred to via Wherever possible, we provide ways to incorporate data directly into the I/H model file and also provide the option to link out to external files in standard formats (eg: starting model coordinates, localization densities, alignments). The details of the linked out files are split into the different categories mentioned above because of the differences in the nature of the data that is stored in them. If these files and the data stored within are to be useful, they are best described in separate tables. The |
How does an IHM file reference a local file currently? For example a sequence alignment file, or localization density local file? How is a reference to a sequence alignment file using a URL done?
|
Reference to local file has been added. |
A new category ( |
In order to use IHM format as a working format while a modeling project is in progress, the externally linked files (comparative models, sequence alignments, EM maps, ensembles of result structures, localization maps, ...) should be listed in a table that refers to local files (on the local disk) instead of referencing a DOI zip archive.
One design would give an integer id to every external file, external database reference, external DOI reference, and all other tables would use this id. Any external data could be referenced in any of these 3 ways (local file, database, DOI archive).
Having external references in one table will simplify validating that deposited structures do not reference missing data.
The text was updated successfully, but these errors were encountered: