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

[harmonize] additional path specification #39

Closed
jkosciessa opened this issue May 30, 2024 · 1 comment
Closed

[harmonize] additional path specification #39

jkosciessa opened this issue May 30, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@jkosciessa
Copy link
Collaborator

jkosciessa commented May 30, 2024

for nPaths = length(parameters.paths_to_add)

The main function adds additional paths as strings (?). I keep using cell strings specified in a call script to specify additional paths. This is a change that keeps getting reverted [e.g., 3989fe0], presumably because it is incompatible with the current yaml specification. To integrate, the function that reads the config.yaml should also turn additional paths in cellstrings.

I'll look into it.

@jkosciessa
Copy link
Collaborator Author

Should be taken care of with 548e2db. But I would be curious if someone ever specified paths that way and can test.

@jkosciessa jkosciessa added the bug Something isn't working label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant