Skip to content

Conversation

dabeycorn
Copy link

No description provided.

@dabeycorn
Copy link
Author

Currently, it seems that while running 'test_nmf_mapping_code' the actual output is different than the expected output causing the tests to fail. It also probably isn't a formatting issue, as after reverting the pre-commit changes to the expected output the tests still fail.

Copy link
Contributor

@sbillinge sbillinge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I made a few suggestions.

@@ -15,6 +15,7 @@ repos:
hooks:
- id: check-yaml
- id: end-of-file-fixer
exclude: ^tests/output/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

remove these excludes?

@@ -12,12 +12,12 @@
data_dir = os.path.join(dir, "data/synthetic_r_vs_gr")

test_map = [
([data_dir, "--xrange", "5,10"], "output_1", "Number of components: 3\n"),
([data_dir], "output_2", "Number of components: 3\n"),
([data_dir, "--xrange", "5,10"], "output_1", "Number of components: 10"),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rather than change the number of components from 3 to 10 in the output, maybe set the number of components to 3 in CLI inputs? I am not sure the flag for that, but it will be in the arg parser.

@dabeycorn
Copy link
Author

Since the plan is to fix the tests later on after the migration process, I'll just close this PR for now

@dabeycorn dabeycorn closed this Jul 1, 2025
@dabeycorn dabeycorn deleted the fix-tests branch July 1, 2025 04:23
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.

2 participants