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.

Sign up for GitHub

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

Jump to bottom

Handling of tracer input properties #39

Open
mcgibbon opened this issue Aug 13, 2018 · 1 comment
Open

Handling of tracer input properties #39

mcgibbon opened this issue Aug 13, 2018 · 1 comment

Comments

@mcgibbon
Copy link
Owner

Currently Sympl (as of 0.4.0) does not include tracers in input properties. This was done in part for internal reasons, but I'm not convinced this is optimal. If I can find a way around those internal reasons, I think it's better to be explicit and list tracers in the input properties (automatically), the same way they're listed in output properties. Making this issue so I remember to take care of this.
@mcgibbon
Copy link
Owner Author

This is a follow up to #36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@mcgibbon