Observation
Possible cause
Recommended action
Library batch import fails
(continued)
The library batch import
spreadsheet contains a
nonunique Library Batch ID.
Every Library Batch ID in the software must be
unique. Ensure that the spreadsheet does not
contain any duplicate IDs, and repeat the
import. Note that the system check is not
case-sensitive, so a Library Batch ID of ABC1
conflicts with abc1.
A sample name entered in the
library batch import
spreadsheet does not match a
sample name listed in the
Manage Samples screen.
Ensure that the sample names entered into the
spreadsheet are correct and match an existing
sample name added to the software.
The Barcode ID name format
does not exactly match the
format that is used in the
Prepare Library Batch dialog
box.
Use the name format following the Barcode ID
name format found in the Barcode Set
reference lists
(Settings
4
References
4
Barcode Set), for
example: IonDual_0101 through IonDual_0196,
or IonHDdual_0101 to IonHDdual_0132.
An invalid library, control, or
panel kit barcode has been
entered in the spreadsheet.
Ensure that you have correctly entered a valid
kit barcode in the appropriate cell of the
spreadsheet.
The assay I created does not
appear in the menu when I plan
a run
Forgot to lock your assay.
Go to Assay tab
4
Manage Assays and make
sure that the assay is locked.
Cannot upload my panel or
hotspots
Issues with BED file format or
files do not end in (.bed).
Ensure your file is in the correct BED format
and has a (.bed) extension.
Allele coverage does not match
hotspot coverage
The coverage value reported
under the Variants tab and
Allele Coverage tab can be
different.
No action required. The coverage value
reported under the Variants tab is the coverage
after down-sampling, while the Allele
Coverage tab reports the raw coverage without
down-sampling. Down-sampling can speed up
variant calling for some over-sampled
positions.
Variants tab is missing hotspot
entries.
The remaining entries are
present.
Hotspot BED file contains
entries that are incorrectly
formatted.
Check that BED file entry is correctly
formatted. See the following examples:
SNP entry: chr1 2337276 2337277 SVA_322 0 +
REF=C;OBS=T;ANCHOR=G AMPL
Deletion entry: chr1 201341175 201341180
SVA_497 0 + REF=AGAAG;OBS=;ANCHOR=C
AMPL
Insertion entry: chr1 236978992 236978992
SVA_621 0 + REF=;OBS=TCTG;ANCHOR=T
AMPL
Confirm the REF values match the actual
reference coordinate of hg19.
The results of the run are not
showing up in the Completed
Runs & Reports screen
The instrument disk space is
full.
Clear disk space on the sequencer. For more
information, see “Manually delete run data“ on
Appendix A
Troubleshooting
Genexus
™
Software
A
118
Genexus
™
Integrated Sequencer User Guide