Skip to content

Bug fix: filters could be None#416

Open
haukekoehn wants to merge 2 commits into
mainfrom
bugfix/setup_detection_limit
Open

Bug fix: filters could be None#416
haukekoehn wants to merge 2 commits into
mainfrom
bugfix/setup_detection_limit

Conversation

@haukekoehn

Copy link
Copy Markdown
Collaborator

When doing an analysis, one should be able to leave the filters unspecified, so that in the end just the filters from the data are taken. This happens later, when filters_to_analyze is determined. But before that, it tries to find a detection_limit depending on filter, which will fail if filter is not specified.

This edit fixes this, although I am not sure if it's in the most elegant way imaginable.

haukekoehn and others added 2 commits March 24, 2026 19:28
When doing an analysis, one should be able to leave the filters unspecified, so that in the end just the filters from the data are taken.
This happens later, when filters_to_analyze is determined.
But before that, it tries to find a detection_limit depending on filter, which will fail if filter is not specified.

This edit fixes this, although I am not sure if it's in the most elegant way imaginable.
Now the function ignores lines starting with a #, so that the header line is ignored.
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

Successfully merging this pull request may close these issues.

1 participant