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

Time to set samplerate #70

Open
Dominik-Vogel opened this issue Mar 15, 2018 · 1 comment
Open

Time to set samplerate #70

Dominik-Vogel opened this issue Mar 15, 2018 · 1 comment
Milestone

Comments

@Dominik-Vogel
Copy link
Member

Currently the sample rate has to be specified for every Blueprint. It is desirable to build entire sequences without having to specify the sample rate and set it once it needs to be forged.
We should think about the implications of setting the sample rate at that later stage.

@WilliamHPNielsen
Copy link
Contributor

Yes, we should. It it stupid that we specify the same information several times.

When do we need a samplerate?

  • When we plot.
  • When we forge.
  • Possibly when we consistency check, but that should not really be necessary.

So I think it should be possible to either assign a sample rate to an object or simply pass it to the plotter/forger as a kwarg when needed. That actually goes for any object. It should then not be possible to have two objects with different sample rates inside the same (higher-ranking) object; that should be a rejection-at-insertion.

@WilliamHPNielsen WilliamHPNielsen added this to the broadbean version 1.0 milestone Mar 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants