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

Solve issue with assigning inputs/outputs in a Jupyter cell #49

Open
StefanVriend opened this issue Jan 11, 2024 · 1 comment
Open

Solve issue with assigning inputs/outputs in a Jupyter cell #49

StefanVriend opened this issue Jan 11, 2024 · 1 comment
Labels
hurdle Hurdles/problems we encounter throughout the workflow. shortcut Temporary solution to a problem that needs a better or more stable fix in the long run

Comments

@StefanVriend
Copy link
Collaborator

The code analyser in the NaaVRE recognises per cell which declarations are inputs and which are outputs. Cell inputs and outputs are required to link cells (or building blocks, if you will) through the Experiment Manager (i.e., a workflow builder). Currently the code analyser has a hard time interpreting R syntax; it's overly sensitive in assigning variables as inputs. To make our workflow run in the NaaVRE, this should be solved.

Gabriel and Spiros will tackle this issue.

@StefanVriend StefanVriend added the hurdle Hurdles/problems we encounter throughout the workflow. label Jan 11, 2024
@StefanVriend StefanVriend added the shortcut Temporary solution to a problem that needs a better or more stable fix in the long run label Jan 17, 2024
@CherineJ
Copy link
Collaborator

Shortcut

Updates in the VRE make it now possible to specify the inputs, outputs and dependencies of a cell through a commented header section. In this header it can also directly be specified of which type the inputs and outputs are, so that this does not need to be done in the code analyser. This is however only a temporary solution and in the long run the code analyser should be smart enough to detect inputs and output of a cell correctly on its own.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
hurdle Hurdles/problems we encounter throughout the workflow. shortcut Temporary solution to a problem that needs a better or more stable fix in the long run
Projects
None yet
Development

No branches or pull requests

2 participants