Changes between Version 6 and Version 7 of xQTLBiologistRun


Ignore:
Timestamp:
2011-09-07T16:09:05+02:00 (13 years ago)
Author:
jvelde
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • xQTLBiologistRun

    v6 v7  
    1212* Give a name to the output data matrix. If it happens to exist, a timestamp will be added to make it unique.
    1313* Select the kind of analysis you would like to run, e.g. ''Rqtl_analysis''.
    14 * Select the amount of subjobs this computational task should be divided into. For larger sets of traits, it is beneficial to set this to higher value, so many jobs will run in parallel. However, if little power (CPUs) is available, a high setting may actually slow the task down. If you are in doubt, use the default of 5.
     14* Select the amount of parts this computational task should be divided into. For larger sets of traits, it is beneficial to set this to higher value, so many parts will run in parallel. However, if little power (CPUs) is available, a high setting may actually slow the task down. If you are in doubt, use the default of 5.
    1515
    1616Step 2:
    1717* Select the datasets to use for this analysis. When many datasets are uploaded and tagged as pheno- and genotype data, be careful to select the right combination.
    1818* Select the parameters you would like to use.
    19 * Start the analysis by pressing ''Start'', this will take you to the job manager where you can follow its progress.
     19* Start the analysis by pressing ''Start'', this will take you to the running analysis view where you can follow its progress.
    2020
    2121Note that if you cannot find back your dataset, or are unhappy with any of the parameters, a bioinformatician (or admin) can configure them for you.
     
    2323
    2424=== Monitoring job progression ===
    25 * In the ''Run QTL mapping'' screen, click on ''Go to job manager''. This will take you to the job manager.
     25* In the ''Run QTL mapping'' screen, click on ''View running analysis''. This will take you to the running analysis monitor.
    2626* The status of all running subjobs can be seen here. The color coding indicates the status. Failed is red/-1, submitted orange/0, queued yellow/1, running blue/2, completed green/3.
    2727* Provenance is kept by storing all analysis parameters in the database. This can be viewed by holding your mouse cursor over the text marked as ''hover''.
     
    3030* Note that you must have supplied your remote login credentials for resubmission of cluster jobs. (Needs a fix: currently this can only be done by submitting a new job)
    3131* The ''refresh page'' box can be used to speed up or slow down the polling interval. (5, 15, 30, 60 seconds or off)
     32
     33=== Result data ===
     34
     35* When the analysis has finished running, click the given name of your result in the column ''Output'' to start browsing result.
     36* Renaming the result data afterwards will break this link and is not advised.
     37* The result data is stored in the same investigation as the first data matrix in the !DataSet list used for this analysis.