Difference between revisions of "Step 4"

From ProcessDB
Jump to navigation Jump to search
(Created page with " == Collect Your Experimental Data == After completing Step 3, describing the experimental protocol in ProcessDB, you are now ready to enter experimental data into the pr...")
 
Line 4: Line 4:
 
After completing [[Step 3]], describing the experimental protocol in ProcessDB, you are now ready to enter experimental data into the program, so that ultimately you will be able to compare your hypothesis quantitatively with your experimental data (Steps 5 and 6). Each experiment that has been recorded in Step 3 can have as many sets of experimental data linked to it as needed. Here in Step 4 you will learn how to import data from an Excel file into ProcessDB, or to manually insert data. Both formats will consist of two columns where the first column is the time readings and the second column is the output data. Once captured, these data will appear in ProcessDB as part of the Experiments screen that was introduced in Step 3 (PRDB015), on the measurements tab.
 
After completing [[Step 3]], describing the experimental protocol in ProcessDB, you are now ready to enter experimental data into the program, so that ultimately you will be able to compare your hypothesis quantitatively with your experimental data (Steps 5 and 6). Each experiment that has been recorded in Step 3 can have as many sets of experimental data linked to it as needed. Here in Step 4 you will learn how to import data from an Excel file into ProcessDB, or to manually insert data. Both formats will consist of two columns where the first column is the time readings and the second column is the output data. Once captured, these data will appear in ProcessDB as part of the Experiments screen that was introduced in Step 3 (PRDB015), on the measurements tab.
  
Coming Soon: Step by step instructions for capturing experimental data into ProcessDB.
+
In progress: Step by step instructions for capturing experimental data into ProcessDB.
 +
 
 +
#Everything ProcessDB needs to know about an experiment can easily be entered in an Experiment file.
 +
#There are two kinds of information you need to enter: experimental protocols (see [[Step 3]]), and experimental data.
 +
#You can enter either protocols or data first, or you can work on both at the same time. Different users have different preferences. This page explains how to enter experimental data.
 +
#If you have already created an Experiment file, open it by double-clicking it in the Experiments tab of the database pane. This will allow you to pick up where you left off last time you worked with this Experiment.
 +
#If you are starting a new experiment, look closely at the Experiments tab of the ProcessDB database pane. Just below the tab is a toolbar with three tools:
 +
##New Experiment tool. The icon is a blue lab notebook with a + in the upper right of the icon.
 +
##Delete Experiment tool
 +
##Search Box
 +
#Click the New Experiment icon.
 +
#Enter a descriptive name for your experiment in the dialog that appears. The name should be chosen so you and your colleagues will recognize this experiment in a list of experiments.
 +
#Click OK
 +
#Your Experiment file will be created and displayed so that you can begin to work with it. Notice your experiment is also highlighted in the Experiments tab of the database pane.
 +
#Three items of information are filled in automatically
 +
##Experiment ID. This is a unique number assigned to this experiment. Many of us find that the easiest way to search for a particular Experiment is to write its Experiment ID in our lab notebook and enter it in the Search box.
 +
##Name. This is the name you entered in the dialog box. You can always edit this name by double-clicking it.
 +
##Date. This is the date you created the Experiment file.
 +
#The Description field defaults to {Unspecified}. You can double-click to edit this field with a short description.
 +
#If you want to annotate this experiment with more detailed notes, you can right click the Experiment in the Experiments tab of the database pane and select Experiment Notes. A Notes window appears.
 +
##Enter any text you find useful and click OK.
 +
##Some items that different experimental biologists like to enter here are
 +
###Date the experimental data were collected
 +
###Names of spreadsheets or other data files connected with this experiment
 +
###Cross-references to pages of your lab notebook
 +
###Textual description of your experimental protocol (What?, Where?, How much?, and When?)
 +
###Notes are not processed by ProcessDB; they are for your convenience only.

Revision as of 10:21, 9 October 2014

Collect Your Experimental Data

After completing Step 3, describing the experimental protocol in ProcessDB, you are now ready to enter experimental data into the program, so that ultimately you will be able to compare your hypothesis quantitatively with your experimental data (Steps 5 and 6). Each experiment that has been recorded in Step 3 can have as many sets of experimental data linked to it as needed. Here in Step 4 you will learn how to import data from an Excel file into ProcessDB, or to manually insert data. Both formats will consist of two columns where the first column is the time readings and the second column is the output data. Once captured, these data will appear in ProcessDB as part of the Experiments screen that was introduced in Step 3 (PRDB015), on the measurements tab.

In progress: Step by step instructions for capturing experimental data into ProcessDB.

  1. Everything ProcessDB needs to know about an experiment can easily be entered in an Experiment file.
  2. There are two kinds of information you need to enter: experimental protocols (see Step 3), and experimental data.
  3. You can enter either protocols or data first, or you can work on both at the same time. Different users have different preferences. This page explains how to enter experimental data.
  4. If you have already created an Experiment file, open it by double-clicking it in the Experiments tab of the database pane. This will allow you to pick up where you left off last time you worked with this Experiment.
  5. If you are starting a new experiment, look closely at the Experiments tab of the ProcessDB database pane. Just below the tab is a toolbar with three tools:
    1. New Experiment tool. The icon is a blue lab notebook with a + in the upper right of the icon.
    2. Delete Experiment tool
    3. Search Box
  6. Click the New Experiment icon.
  7. Enter a descriptive name for your experiment in the dialog that appears. The name should be chosen so you and your colleagues will recognize this experiment in a list of experiments.
  8. Click OK
  9. Your Experiment file will be created and displayed so that you can begin to work with it. Notice your experiment is also highlighted in the Experiments tab of the database pane.
  10. Three items of information are filled in automatically
    1. Experiment ID. This is a unique number assigned to this experiment. Many of us find that the easiest way to search for a particular Experiment is to write its Experiment ID in our lab notebook and enter it in the Search box.
    2. Name. This is the name you entered in the dialog box. You can always edit this name by double-clicking it.
    3. Date. This is the date you created the Experiment file.
  11. The Description field defaults to {Unspecified}. You can double-click to edit this field with a short description.
  12. If you want to annotate this experiment with more detailed notes, you can right click the Experiment in the Experiments tab of the database pane and select Experiment Notes. A Notes window appears.
    1. Enter any text you find useful and click OK.
    2. Some items that different experimental biologists like to enter here are
      1. Date the experimental data were collected
      2. Names of spreadsheets or other data files connected with this experiment
      3. Cross-references to pages of your lab notebook
      4. Textual description of your experimental protocol (What?, Where?, How much?, and When?)
      5. Notes are not processed by ProcessDB; they are for your convenience only.