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

Make pipeline more develop-friendly #17

Open
ViktorHy opened this issue Sep 20, 2023 · 2 comments · Fixed by #38
Open

Make pipeline more develop-friendly #17

ViktorHy opened this issue Sep 20, 2023 · 2 comments · Fixed by #38
Assignees
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@ViktorHy
Copy link
Contributor

To make it easier to load data generated from pipeline into coyote:

  1. Gens data needs to be tabixed
  2. Gens data can only be loaded from /fs1/results/, maybe publishdir to there? Or some other solution. Needs to be backed up as well. Gens only stores paths and as such we will lose data for dev runs if not in /fs1/results
  3. Plot-data. Only supported folders in coyote is supported. Either make it easier to load image paths into coyote (defined in mongo and loaded dynamically?) or make sure image are output into correct folders/backup/symlink. See gens issue above
@ViktorHy ViktorHy added enhancement New feature or request help wanted Extra attention is needed labels Sep 20, 2023
@sailepradh
Copy link
Contributor

sailepradh commented Sep 20, 2023

I can take this and maybe the header could be alittle more informative as "Improve visulization issues with the pipelines"

@ramsainanduri ramsainanduri linked a pull request Nov 1, 2023 that will close this issue
@ViktorHy
Copy link
Contributor Author

ViktorHy commented Apr 2, 2024

Maybe add a script to solve third problem. To be used during development

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants