Skip to content

Conversation

@blairlyons
Copy link
Collaborator

Time Estimate or Size

x-large (sorry!)

Problem

Visualization and post processing scripts were inefficiently organized and out of date.

Solution

I refactored code and tested all of the notebooks in simulation.readdy and visualization modules.

Type of change

Please delete options that are not relevant.

  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

Keyfiles:

Main changes are in simulation.readdy and visualization modules, but I had to make some changes to analysis and other places to support these.

Blair Lyons and others added 30 commits June 25, 2024 16:34
@blairlyons blairlyons requested review from jessicasyu and mogres July 19, 2024 20:49
Copy link
Collaborator

@jessicasyu jessicasyu left a comment

Choose a reason for hiding this comment

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

Looks great! Mostly minor things. The only major issue is with the Cytosim simularium trajectories, where the linkers seem to be off.

There's also some missing docstrings, but we can add those in a separate PR so this one doesn't keep getting bigger ;)

Copy link
Contributor

@mogres mogres left a comment

Choose a reason for hiding this comment

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

Thanks for making the changes, the visualization updates are very helpful! The PR overall looks good to me. I was able to run the visualization notebooks and generate the simularium trajectories but ran into a couple of issues along the way.

  1. In the individual readdy and cytosim visualization notebooks, I ran into an error due to the missing h5py package. After installing it using pdm add h5py the notebooks ran as expected.

  2. I also ran into the issue Jess mentioned regarding the linkers in Cytosim trajectories. They seem to be offset from the main fiber.
    image

@blairlyons
Copy link
Collaborator Author

@jessicasyu @mogres I think I addressed everything, the Cytosim issue depends on this PR getting merged. I tried fixing the mypy error in the analysis module without success, would be great if someone knows how to fix that.

@blairlyons blairlyons requested review from jessicasyu and mogres July 25, 2024 20:30
Copy link
Collaborator

@jessicasyu jessicasyu left a comment

Choose a reason for hiding this comment

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

Looks great! Just a couple more things but good to merge after that. I can take a final pass through everything once we get the PRs all merged.

run: |
pdm run pytest --cov --cov-report html
rm htmlcov/.gitignore
Copy link
Collaborator

Choose a reason for hiding this comment

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

I would keep the build workflow as is (it'll break the coverage badge otherwise). It just won't find any tests to run, which I think is fine.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

it breaks the build otherwise. We can add one test that passes, or maybe the coverage badge should be removed since we know it's zero, unfortunately

Copy link
Collaborator

Choose a reason for hiding this comment

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

I can refactor the existing test so it passes? It doesn't need to be in this PR

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

can I leave it like this for this PR and you can pull this back in with the fixed test?

@jessicasyu
Copy link
Collaborator

@blairlyons @mogres I believe that last mypy issues is fixed in #61

@blairlyons blairlyons merged commit c1e8080 into main Jul 29, 2024
@blairlyons blairlyons deleted the debug-update-viz branch July 29, 2024 23:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

4 participants