Documentation/Nightly/Modules/DatabaseInteractor - Revision history

Mirclem: /* Use Slicer as a job computer */

2017-05-25T18:51:48Z

Use Slicer as a job computer

Mirclem: /* Use Slicer as a job computer */

2017-05-25T18:45:28Z

Use Slicer as a job computer

Mirclem: Added more tutorials and a table of contents

2017-05-25T16:55:34Z

Added more tutorials and a table of contents

Mirclem: /* Use Slicer as a job computer */

2017-05-25T16:45:44Z

Use Slicer as a job computer

Mirclem: /* Use Slicer as a job computer */

2017-05-25T16:44:55Z

Use Slicer as a job computer

Mirclem: /* Use Slicer as a job computer */

2017-05-25T16:44:38Z

Use Slicer as a job computer

Mirclem: /* Use Slicer as a job computer */

2017-05-25T16:43:43Z

Use Slicer as a job computer

Mirclem at 16:43, 25 May 2017

2017-05-25T16:43:22Z

Mirclem at 16:15, 4 May 2017

2017-05-04T16:15:35Z

Mirclem at 18:14, 12 December 2016

2016-12-12T18:14:01Z

@@ Line 128: / Line 128: @@
 Be careful, it is possible to submit jobs for a full dataset and then connect Slicer to run those jobs during nights. But, some user could have sent a job that can take three weeks to run and so Slicer will run this one instead of the one just sent.
 |-
-| [[Image:DisconnectJobListener.png|500px]] || At any time, the Slicer instance can be disconnected from the server.
+| [[Image:DisconnectJobListener.png|500px]] || At any time, the Slicer instance can be disconnected from the server and a new period can be set.
 |}
 <!-- ---------------------------- -->

@@ Line 124: / Line 124: @@
 ===Use Slicer as a job computer===
 {|
-|[[Image:RunJobs.png|500px]]
+|-
-|With this panel, any Slicer can be used as a computation instance. After connecting to the server, the user can select a period for Slicer to check if there is a job waiting. If a job is pending and the Slicer version matches with the job executable, the CLI will be computed and the outputs uploaded to the server.
+| [[Image:RunJobs.png|500px]] || With this panel, any Slicer can be used as a computation instance. After connecting to the server, the user can select a period for Slicer to check if there is a job waiting. If a job is pending and the Slicer version matches with the job executable, the CLI will be computed and the outputs uploaded to the server.
 Be careful, it is possible to submit jobs for a full dataset and then connect Slicer to run those jobs during nights. But, some user could have sent a job that can take three weeks to run and so Slicer will run this one instead of the one just sent.
+|-
-At any time, the Slicer instance can be disconnected from the server.
+| [[Image:DisconnectJobListener.png|500px]] || At any time, the Slicer instance can be disconnected from the server.
 |}
 <!-- ---------------------------- -->
 {{documentation/{{documentation/version}}/module-section|Similar Modules}}

@@ Line 22: / Line 22: @@
 </gallery>
 {{documentation/{{documentation/version}}/module-introduction-end}}
 <!-- ---------------------------- -->

@@ Line 125: / Line 125: @@
 |[[Image:RunJobs.png|500px]]
 |With this panel, any Slicer can be used as a computation instance. After connecting to the server, the user can select a period for Slicer to check if there is a job waiting. If a job is pending and the Slicer version matches with the job executable, the CLI will be computed and the outputs uploaded to the server.
-Be careful, it is possible to submit jobs for a full dataset and then connect Slicer to run those jobs during nights. But, some user could have sent a job that can take three weeks to run and so Slicer will run this one instead of the one just sent. <br />
+Be careful, it is possible to submit jobs for a full dataset and then connect Slicer to run those jobs during nights. But, some user could have sent a job that can take three weeks to run and so Slicer will run this one instead of the one just sent.
 At any time, the Slicer instance can be disconnected from the server.
 |}

@@ Line 125: / Line 125: @@
 |[[Image:RunJobs.png|500px]]
 |With this panel, any Slicer can be used as a computation instance. After connecting to the server, the user can select a period for Slicer to check if there is a job waiting. If a job is pending and the Slicer version matches with the job executable, the CLI will be computed and the outputs uploaded to the server.
-Be careful, it is possible to submit jobs for a full dataset and then connect Slicer to run those jobs during nights. But, some user could have sent a job that can take three weeks to run and so Slicer will run this one instead of the one just sent.
+Be careful, it is possible to submit jobs for a full dataset and then connect Slicer to run those jobs during nights. But, some user could have sent a job that can take three weeks to run and so Slicer will run this one instead of the one just sent. <br />
 At any time, the Slicer instance can be disconnected from the server.
 |}

@@ Line 42: / Line 42: @@
 <!-- ---------------------------- -->
 {{documentation/{{documentation/version}}/module-section|Tutorials}}
 ===Login to the database===
 {|
@@ Line 108: / Line 109: @@
 |[[Image:AddDateToPatientId.png|500px]]
 |In the case the "admin" user gets more data for a patient with a different date than the ones already created, this panel gives the possibility to add a new one. First, it needs to select the collection, then a patient Id and finally the date wanted. The last step is to click on the button and check in the collection folder that everything has been correctly done.
 |}
@@ Line 121: / Line 141: @@
 {{documentation/{{documentation/version}}/module-section|Information for Developers}}
 This extension has been designed to work with this [https://ec2-52-42-49-63.us-west-2.compute.amazonaws.com:8180/DCBIA-OrthoLab/public/ website] and should not work with other architectures.
-If you want to use this plugin on another server, you need to make sure your documents are stored by CouchDB and your documents contains a field "type" set to "morphologicalData".
+If you want to use this plugin on another server, you need to make sure your documents are stored by CouchDB and your documents contain a field "type" set to "morphologicalData".
 Your user would need to connect using [https://jwt.io/ JWT] and have a "scope" field.<br>
 For more information, you can take a look at the website source code [https://github.com/DCBIA-OrthoLab/shiny-tooth here].<br>

@@ Line 9: / Line 9: @@
 {{documentation/{{documentation/version}}/module-introduction-row}}
 Extension: '''Database Interactor'''<br>
-Acknowledgments: This work was supported by the National Institues of Dental and Craniofacial Research and Biomedical Imaging and Bioengineering of the National Institutes of Health.<br>
+Acknowledgments: This work was supported by the National Institues of Dental and Craniofacial Research and Biomedical Imaging and Bioengineering R01DE024450 of the National Institutes of Health.<br>
 Author: Clément Mirabel (University of Michigan)<br>
 Contributor1: Juan Carlos Prieto (UNC)<br>

@@ Line 28: / Line 28: @@
 This extension contains multiple panels that allow the user to manage data from a CouchDB database stored on a server. It has been developed to work with this [https://ec2-52-42-49-63.us-west-2.compute.amazonaws.com:8180/DCBIA-OrthoLab/public/ website], so the user will need to have an account on this website.
 The data currently stored on this website is for a pilot study which needs to federate biological, morphological and clinical data. At the end of the development of the website, this should be available for other projects. For more information about the website status, contact <email>juanprietob@gmail.com</email>.<br>
-The data displayed in this extension dynamically reacts with user local folders and online database. The user should login with the same credentials than on the server entered as input.
+The data displayed in this extension dynamically reacts with user local folders and online database. The user should login with the same credentials than on the server entered as input.<br><br>
 <!-- ---------------------------- -->