Page History
...
- 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
...
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.
Figure 6:
Numbered figure captions | ||||
---|---|---|---|---|
| ||||
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.
Figure 7.
Numbered figure captions | ||||
---|---|---|---|---|
| ||||
|
Figure 9.
Numbered figure captions | ||
---|---|---|
|
| ||
Numbered figure captions | ||||
---|---|---|---|---|
| ||||
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,
Figure 10.
Numbered figure captions | ||||
---|---|---|---|---|
| ||||
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.
Figure 11. Expanded sample
Numbered figure captions | ||||
---|---|---|---|---|
| ||||
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
Figure 12.
Numbered figure captions | ||||
---|---|---|---|---|
| ||||
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
Figure 13.
Numbered figure captions | ||
---|---|---|
|
Note that this can only be done on a blank project... once you have any import
Issue with Pairing KB-6392 reopened
| ||
Additional assistance |
---|
|
Rate Macro | ||
---|---|---|
|
Numbered figure captions | ||||
---|---|---|---|---|
| ||||
|