Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

manifest file : absolute-path vs absolute-filepath #18

Closed
RachBioHaz opened this issue Oct 31, 2023 · 3 comments
Closed

manifest file : absolute-path vs absolute-filepath #18

RachBioHaz opened this issue Oct 31, 2023 · 3 comments

Comments

@RachBioHaz
Copy link

RachBioHaz commented Oct 31, 2023

Hi,
I just wanted to know if there was a specific flag I should be using to have the manifest file column labelled with absolute-filepath instead of absolute-path.

The command I'm using is:

seqfu metadata ~/Project/NL3/01Raw/  > ~/Project/NL3/01Raw/manifest.tsv

The manifest file is created:
first column header = sample-id
second column header = absolute-path (should be absolute-filepath)

Thanks for your help.

@telatin
Copy link
Owner

telatin commented Oct 31, 2023

Thanks for reporting, will look into this and either fix or add a flag for it!

@telatin
Copy link
Owner

telatin commented Nov 2, 2023

Found the issue
Can you confirm you have single end reads in that directory please?

@RachBioHaz
Copy link
Author

Hi, sorry for the delay - have been away. Yes, the reads are single end reads.
Cheers

@telatin telatin closed this as completed Dec 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants