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

reports: get descriptive parameters from settings-file #83

Open
vicfabienne opened this issue Jun 23, 2021 · 2 comments
Open

reports: get descriptive parameters from settings-file #83

vicfabienne opened this issue Jun 23, 2021 · 2 comments
Labels
prio:Low issues needs to be fixed in long term question Further information is requested type:enhancement any enhancement that doesn't fit into aesthetics, bug or documentation

Comments

@vicfabienne
Copy link
Collaborator

The reports (varaint and QC) are mentioning some settings and values in their descriptive markdwon part (e.g. the assembly number of the reference genome, some setting parameter that are good to know for an overview).
I think it should be able to change those values - so either grabbing them from the settings file or maybe providing as additional optional input? Or maybe an optional section in the settings file?

@vicfabienne vicfabienne added question Further information is requested prio:Low issues needs to be fixed in long term labels Jun 23, 2021
@al2na al2na added the type:enhancement any enhancement that doesn't fit into aesthetics, bug or documentation label Jul 1, 2021
@rekado
Copy link
Member

rekado commented Jul 1, 2021

In order to be actionable, this issue needs a list of actual locations that you would like to change.

@jonasfreimuth
Copy link
Member

This commit already makes a lot of things in the variantreport dynamic. But lofreq params are still not adjustable. Also I don't understand what parameters you mean in the QC report, @vfschumann. Are those already dealt with?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
prio:Low issues needs to be fixed in long term question Further information is requested type:enhancement any enhancement that doesn't fit into aesthetics, bug or documentation
Projects
None yet
Development

No branches or pull requests

4 participants