HenriquesLab / HenriquesLab/NanoPyx
Unable to Implement Workflow Class due to functions lacking attribute '_run_types'
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 93
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Nanopyx Team,
Thank you for your thorough documentation and expansive library of high quality code. I have been testing several features of the library and ran into an issue with the Workflow class. When I try to wrap different functions, including their args and kwargs, from the Methods folder within the Workflow instance, I run into an attribute error stating that the 'function' object has no attribute '_run_types'. Perhaps, I am using functions incompatible with the Workflow class.
Below is the block of code raising the issue and the traceback:
I was hoping to use a Workflow instance to streamline my multi-step analysis (drift correction -> parameter sweep -> eSRRF), and would appreciate any pointers on implementation.
At the same time, the agent appears to chose random run types (often landing on threaded_guided despite significantly longer run times) for parameter sweep and drift correction functions, so I was hoping there might be a method to globally force a run type if the Workflow Class is incompatible with the Methods functions I am using. Any clarification/guidance would be much appreciate!
Thank you for your time,
Jake
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported Workflow usage with the functions from the Methods folder and inspect where the Workflow class expects the _run_types attribute. Check how drift correction, parameter sweep, and eSRRF functions declare or select run types; done means the supported usage or a fix is confirmed, including a way to control run-type selection if supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100