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

Standardising atlas file downloading #351

Merged
merged 24 commits into from
Nov 11, 2024

Conversation

viktorpm
Copy link
Contributor

@viktorpm viktorpm commented Aug 9, 2024

Description

This PR introduces a standardized method for downloading atlas files using pooch.

  • Bug fix
  • Addition of a new feature
  • Other

How has this PR been tested?

Scripts were tested locally

Is this a breaking change?

No

Does this PR require an update to the documentation?

Potentially

Checklist:

  • The code has been tested locally
  • Tests have been added to cover all new functionality (unit & integration)
  • The documentation has been updated to reflect any changes
  • The code has been formatted with pre-commit

@viktorpm viktorpm marked this pull request as ready for review September 4, 2024 10:50
Copy link
Member

@alessandrofelder alessandrofelder left a comment

Choose a reason for hiding this comment

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

Thanks a lot @viktorpm - this is good progress!
And sorry for letting this sit so long 🙈

I've suggested some minor changes and asked for minor clarifications.

Some high-level comments

  • there's quite a bit of commented out code that I think should be removed
  • I'm confused by the ### comments, but if we want to keep them we should add them everywhere.

We should open issues for

  • removing the current way of parallelising mesh creation everywhere
  • decide what to do with __version__ and __atlas__
  • make mesh creation parallel in a more robust way

What do you think?

@@ -1,52 +1,58 @@
__version__ = "1"

### Import
Copy link
Member

Choose a reason for hiding this comment

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

Are these comments useful and why do they start with ###? I may be missing something. If they are useful, should they be added to the admba_3d_dev_mouse script too?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

They are just there to structure the code into sections.

  • Import: loading packages
  • Settings: options to turn on and off
  • Metadata: atlas related information

If it's confusing or not good practice, we can get rid of them. Ideally, all packaging scripts should follow this structure including admba_3d_dev_mouse. I probably just forgot to add the headers. That script is a bit of an exception as the generated atlases are treated as separate atlases not as variations of the same atlas.

Copy link
Member

Choose a reason for hiding this comment

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

If it's confusing or not good practice

My take on this is that at least the Metadata and Import ones are redundant.
I'm doubtful that we want to keep settings hard-coded on a per-atlas level going forward.

there to structure the code into sections.

Hopefully the structure introduced by #400 will sufficiently structure the scripts.
So I would lean towards removing them.

That script is a bit of an exception as the generated atlases are treated as separate atlases not as variations of the same atlas.

This, on the other hand, is possibly useful contextual explanation that might be a good comment to have in that script (if it's not there yet)!

Copy link
Member

@alessandrofelder alessandrofelder left a comment

Choose a reason for hiding this comment

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

Thanks @viktorpm - I've replied to your questions, I think.

Could you resolve the conflicts with main and ask for my review when you have please? Then we will be almost there!

@@ -1,52 +1,58 @@
__version__ = "1"

### Import
Copy link
Member

Choose a reason for hiding this comment

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

If it's confusing or not good practice

My take on this is that at least the Metadata and Import ones are redundant.
I'm doubtful that we want to keep settings hard-coded on a per-atlas level going forward.

there to structure the code into sections.

Hopefully the structure introduced by #400 will sufficiently structure the scripts.
So I would lean towards removing them.

That script is a bit of an exception as the generated atlases are treated as separate atlases not as variations of the same atlas.

This, on the other hand, is possibly useful contextual explanation that might be a good comment to have in that script (if it's not there yet)!

@alessandrofelder
Copy link
Member

We should open issues for

Crosslinking issues here for documentation purposes.

Copy link
Member

@alessandrofelder alessandrofelder left a comment

Choose a reason for hiding this comment

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

Thanks a lot for this @viktorpm

I've made some final beautifications and will merge when (if!) the tests pass :)

@alessandrofelder alessandrofelder merged commit e9fdb99 into main Nov 11, 2024
12 of 13 checks passed
@viktorpm viktorpm deleted the standardising_atlas_file_downloading branch November 11, 2024 15:02
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