.csfiles, and importing it again
failedstatus will not be updated on disk until they enter
completedstatus - either by actually completing, or by the user choosing the
mark as completedoption in the Job Details panel. This action will ensure that the job directory is updated, and therefore that importing the project into another instance will contain the latest information about the job.
.csfiles in cryoSPARC. Along with the
.csfile, a separate text file in
.csgformat describes the overall metadata for the group.
.csgfile that was created during export when creating the import job.
-hoption, these links will be copied into the
.tarfile as actual files, using up more disk space. If you do not use the
-hoption, you will need to make sure you separately archive the raw data from the project if it was stored outside the project directory.
.tarfile, you can send this by any available means to another user or machine/system. The receiving user should decompress the
.tarfile into a directory accessible by cryoSPARC. To keep things tidy, create a new folder inside the parent directory of cryoSPARC's projects called
.csgfiles (more details below in FAQ: What are .cs and .csg files?) and symbolically link all of the job's outputs into a folder inside the project directory. The exported job will be found at
.csfile and a
.csgfile is a YAML file that contains metadata information related to the output group itself (including the name of the
.csfile, type of results, and number of items). The
.csfile is a highly-optimized array-based file containing specific metadata for every item in the group. Alongside these files, the consolidated data will be symbolically linked into this folder.
-hargument if you want to include all the referenced raw files.
imports/jobsinside the project directory you want to import the job into. This could be in the same or a different instance.
PXX/exports/groupsfolder of the project. The functionality is similar to what happens when you export a job.
.mrcfiles for a particle stack). This export directory can be consolidated using
taror by uploading to a repository. Ensure that the symbolic links are followed during upload or consolidation by "dereferencing."
.csgfile of the exported output result group, which will be inside of the export directory. This will import the group of items (eg. particle stack) with all associated metadata, so that it can be used for further processing.
.csgfile formats used by cryoSPARC. More details about these and source code for reading/writing them are forthcoming.
.csgfiles contain text-format high level information about an importable group of items in cryoSPARC. The individual metadata about each item (e.g., particle alignments) are stored in
.csfiles which are binary and efficient.
.csfiles describing all of its outputs. These files are also created when a job or output group is exported.
.csfile of the particle output group.
.csfile using python/numpy (see FAQ - details and code forthcoming) to apply the desired transformation.
.csgfile with any text editor to ensure that it points to the new
>means that the path should be relative to the
.csgfile that you copied. This job will import the particle stack, preserving the identity of the particles (i.e., the
uidcolumn in the
.csfile) but with new alignments that you have manually modified.
.csfiles yourself from scratch and import these as well.
.cs) are numpy-array wrapped data structures used to store metadata for millions of input and output files in cryoSPARC. Code and details for easily dealing with
.csfiles are forthcoming. You can load and read a
.csfile using the
numpy.loadfunction (see here).
.csfile can be visualized in a tabular manner:
.csg) are YAML-formatted (for readability) text files that hold metadata about the output result groups themselves:
.csgfiles should use the above format.
killedjobs, since these jobs have not finished yet. Once the jobs finish, they will written to disk as
completedjobs. All other jobs will retain their status as-is and can be imported in another instance immediately once migration is complete.
cryosparcm stop- it will resume from where it left off the next time cryoSPARC is turned on
st_sizevalue for each file.
duto dereference symbolic links to get a similar value. Please note you will also get discrepancies based on how
ducalculates system block sizes.