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

Specify (short) input names in call to MultiQC #466

Open
tomkinsc opened this issue Apr 19, 2023 · 2 comments
Open

Specify (short) input names in call to MultiQC #466

tomkinsc opened this issue Apr 19, 2023 · 2 comments

Comments

@tomkinsc
Copy link
Member

tomkinsc commented Apr 19, 2023

The MultiQC output currently names samples using adapted versions of their full file paths. On machines where the inputs to MultiQC are stored within deep hierarchies (i.e. staged PAPI instances); this results in a MultiQC report where the input (sample) names are so long that they prevent the actual sample name from being displayed.

The call to MultiQC should be adapted to use shorter names—probably the basename of the input files stored within the input-filenames.txt created in the body of task MultiQC. The task should honor values passed via the sample_names input of the task MultiQC, overriding the auto-shortened sample names with those specified in the task input (if present).

Care will be likely be needed to ensure correct sample name ordering if the MultiQC report is extended to include other inputs in addition to those from FastQC.

@tomkinsc
Copy link
Member Author

Or we can simple omit --dirs from the MultiQC invocation, and provide a boolean to optionally enable display of full paths.

@tomkinsc
Copy link
Member Author

Changes in PR #467 to address this.

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

1 participant