This repository has been archived by the owner on Feb 23, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 24
printing data frames with validation function information #115
Merged
Merged
Changes from 14 commits
Commits
Show all changes
23 commits
Select commit
Hold shift + click to select a range
d6d481b
first test functions for validate_mesh_structure_pairs
viktorpm 512cd63
storing atlases and successful/failed validation functions in a data …
viktorpm 3aaf90a
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 4e29467
restoring test_validation.py to the original merged version. Chages a…
viktorpm 84de0d1
restoring test_validation.py to the original merged version. Chages a…
viktorpm f6b0dc0
validate_atlases.py: going back to the version on main, appending onl…
viktorpm fd8a6a8
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] a0ba87b
populating dictionaries in for loop, writing JSON files
viktorpm 6d9707b
Merge branch 'cosmetics' of github.com:brainglobe/bg-atlasgen into co…
viktorpm 0bd3163
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] a980f67
saving JSON files to ~/.brainglobe/atlases/validation
viktorpm eec486a
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 398dccc
printing where to find the result files
viktorpm 56686e1
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 576d8d2
Update bg_atlasgen/validate_atlases.py
viktorpm d7a7d3b
Update bg_atlasgen/validate_atlases.py
viktorpm defaa29
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 16dee78
Merge branch 'main' into cosmetics
viktorpm 8773286
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] da4cc8f
saving only one JSON file with all the information
viktorpm 6c00f6d
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] 58722fd
uncommenting test functions
viktorpm dea87e4
Merge branch 'cosmetics' of github.com:brainglobe/bg-atlasgen into co…
viktorpm File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(:arrow_up: Just a sketch... and just a discussion point)
Should we combine the two lists while we're refactoring this, and have them have the same format (
str(error)
if failed, andNone
if valid)? The advantage would be simplicityBut it's entirely possible there's value in keeping the things separate? What do you think?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this suggestion! I was also thinking about doing this but wanted to have a chat first, as I wasn't sure how to implement it. I think it would be much better to have only one file with all the necessary information.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alessandrofelder, I implemented these changes and tested them locally and on the HPC. Could you check them, please? 🙂
I think it's ready to be merged if you approve the changes.
result file:
validation_results.json
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @viktorpm - As per our developer's guide around PRs, you have the liberty to merge if your reviewer approves with optional comments without asking for another round of review :) I have had another look though and looks great!