Skip to content

updates in lims not reflected in voyager.  #28

@anoronh4

Description

@anoronh4

A cmoid change that is in the lims has not yet registered in voyager. The two igo ids 08039_CV_1 and 08039_CN_11 both had the sample id s_C_4HX0K5_M001_d and mapped to the following two fastq pairs:

s_C_4HX0K5_M001_d	idt	/igo/delivery/FASTQ/PITT_0522_AHJV3KBBXY/Project_08039_CV/Sample_P-0027816-T02-WES_IGO_08039_CV_1/P-0027816-T02-WES_IGO_08039_CV_1_S6_R1_001.fastq.gz	/igo/delivery/FASTQ/PITT_0522_AHJV3KBBXY/Project_08039_CV/Sample_P-0027816-T02-WES_IGO_08039_CV_1/P-0027816-T02-WES_IGO_08039_CV_1_S6_R2_001.fastq.gz	2
s_C_4HX0K5_M001_d	idt	/ifs/archive/GCL/hiseq/FASTQ/PITT_0495_BHHYJGBBXY_A1/Project_08039_CN/Sample_P-0027816-T02-WES_IGO_08039_CN_11/P-0027816-T02-WES_IGO_08039_CN_11_S21_R1_001.fastq.gz	/ifs/archive/GCL/hiseq/FASTQ/PITT_0495_BHHYJGBBXY_A1/Project_08039_CN/Sample_P-0027816-T02-WES_IGO_08039_CN_11/P-0027816-T02-WES_IGO_08039_CN_11_S21_R2_001.fastq.gz	2

However, the fastq pairs related to 08039_CN_11 change cmo id, and is now known as s_C_UE1MR5_M001_d. this can be seen in the lims. after updating both requests with the following command:

singularity exec beagle_0.0.1.sif beaglecli import-requests --request-ids=08039_CN,08039_CV --redelivery=True

the changes are still not reflected in the voyager database.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions