-
Notifications
You must be signed in to change notification settings - Fork 2
Separate hardware library #46
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
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Stephan Lachnit <[email protected]>
Satellite: adapt to CDTP2 for COnstellation v0.6+
|
This should probably be rebased since the merge of #47. I see some parts that are identical. |
|
Just gave this branch a try, and there seems to be a bug in here. I get the following error: Does not happen when I use main. |
|
Ok, it seems like this only happens when using constellation. And only at the first initialization step. If the TLU is already initialized when starting constellation then everything works. This does not happen, when using the pure Python side, but I will investigate this further. |
Fix: Write Clock File
Updated descriptions with minor language-related points
DOC: update category and add parent class in Constellation README
|
The constellation issues were solved in #49, right? Then we could continue here |
|
Yes, this branch should work now. |
|
™️ |
FIX: frames_as_blocks now called write_as_blocks in EudaqNativeWriter BOR
|
@rpartzsch @cbespin FYI we have testbeam next week and will use this branch together with Constellation v0.6.1, if we find something we'll let you know, if not it would be nice to get a new release with this. |
|
Sounds good! Small celebration before the end of the year then |
|
Overall it worked really well, there is however still an issue if the |
Refactored the TLU main script into a hardware side controller. This separates the functionalities of the constellation satellite further from the rest of the Python package and makes it easier to handle status logs and data differently for the different use cases.