For new projects, a sample table can be automatically created from a tab-delimited text file. There are several advantages of creating a sample table in this manner:
- You can define multiple samples and attributes even before data has been imported, and therefore you can:
- customize the name of your samples (and not use the automatic sample names generated based on file names)
- import sample sheets as defined by the instrument that generated your data
- You can simultaneously create the sample table and import data, which allows you to:
- combine several files into one sample
- import data located in multiple subdirectories
This process of generating a sample table based on a text file can only be done once per project. Additional samples or attributes can still be added using the Import data or Manage attributes buttons.
Selection of the Text File
The text file must be created outside of Partek® Flow® (you can use software such as Partek® Genomics Suite®, Microsoft® Excel® or any text editor). A valid text file is a tab-delimited text file that contains one sample per row and columns containing sample information. At least one column must have unique entries and will be suggested as Sample IDs. Additional columns may contain numeric or categorical attributes and (optional) filenames. Examples of text files are shown in Figures 3 and 6.
To select the text file, create a new project and in the blank Data Tab (no samples have been imported yet), click the Assign sample attributes from a file button (Figure 1).
Navigate to the file using the browser as shown in in Figure 2. The text file may be located in either the Partek Flow server, My computer, or from a URL. However, if you wish to create the sample table and start importing the data at the same time, (explained later in this section), the text file must be on the Partek Flow server.
Check the box next to the text file that you want to use and click Next.
Creating a Sample Table without Data Import
Text files that contain only sample IDs and attributes such as the one shown in Figure 3 can be imported to create a sample table with no associated files. For this type of import, the text file may be located in either the Partek Flow server, My computer, or from a URL (Figure 2).
The text file will be summarized as in Figure 4. The first two columns show the headers and example terms parsed from the text file in Figure 3. The suggested attribute names can be renamed before import. Columns that contain unique entries are recognized as possible Sample IDs and can be selected using the radio button. You can choose which attributes to be included and, if applicable, whether they are numeric or categorical. The Show/hide file preview link allows you to preview the text of the tab delimited text file you are using.
In the example in Figure 4, the columns for "Sample name" and "Freezer Location" are both unique and the former is selected as the Sample ID. The "Freezer location" has been deselected and it will not be included in the resulting Sample table. Since "Age" has all number terms, the Attribute type column for it is a drop down menu to choose between Numeric and Categorical. There are no filenames in the text file so the Files column is empty.
Creating a Sample Table with Data Import
If you have a text file that contains sample IDs and attributes as well as the filenames of your data, you can create the sample table and start the data import at the same time. This is particularly useful for projects where multiple files are associated with the same sample (e.g., a sample ran in multiple lanes in the sequencer). For this type of import, the text file must be located in the Partek Flow server (Figure 2).
In the text file, each filename to be associated with the sample must be separated by a tab. That means, if you are using a spreadsheet software to generate the text file, there is a maximum of one file per column. You also need to add headers such as file1, file2, etc., to define the columns. There is no limit on the number of columns on the text file.
The filenames must show the proper extensions of data types compatible with Partek Flow (see Types of Data).
The actual files can be in the same directory as the text file or in a different directory. If the files are in a different directory, you must include the file paths.
Text file and data are in the same directory
If the text files are in the same directory as the Data files, simply include the filenames in the text file as shown in Figure 6. You do not have to specify the file path.
The text file will be summarized as in Figure 7. Filenames that are recognized as valid file types and also located in the same folder as the text file are presented in the Files column.
At this stage, you can also go to the Analyses Tab of the project and see that the data node has been created but the color is light blue, which indicates the import is not complete.
Once all the files have been imported from the queue, Analyses Tab will show the data node to be dark blue,
To view the files associated with the data, go to the Data Tab and click Show data files to expand the table. Figure 11 shows that 4 files were successfully imported for each sample. You can add more or delete samples as described in the Adding samples section.
Text file and data are in different directories
If your samples are in different subdirectories, you must include the path in for your file name. You can use either a relative path or an absolute path.
Relative paths
This means the the path you will include is relative to the location of the text file. For example in Figure 12, the text file is located in a directory called "download" while the files are in a subdirectory called MyData, then the filenames must include the path /MyData/. An example is shown below:
/MyData/NA1031_S25_L007_R1_001.fastq.gz
Absolute path
This means the the path you will include is the full file path to the file based on the file structure of Partek Flow. Where the text file is located you can simply add the directories based on the Partek Flow home directory (see region in red box in Figure 13). For typical installations, the path begins with /home/flow/FlowData/ and so the filenames to include in the text file may look like this:
/home/flow/FlowData/download/MyData/NA1031_S25_L007_R1_001.fastq.gz
Additional Assistance
If you need additional assistance, please visit our support page to submit a help ticket or find phone numbers for regional support.
Your Rating: | Results: | 0 | rates |