-
Notifications
You must be signed in to change notification settings - Fork 75
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
Move random functions to their own file #196
base: master
Are you sure you want to change the base?
Conversation
This makes tools/g3c a slightly more manageable length. It also makes it easier to switch to the new numpy random API in future, which would solve our non-deterministic CI woes.
This pull request introduces 2 alerts when merging c7a5058 into aec1960 - view on LGTM.com new alerts:
|
c7a5058
to
9968d86
Compare
This pull request introduces 2 alerts when merging 9968d86 into aec1960 - view on LGTM.com new alerts:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a good plan
Except I screwed up and CI fails. Some of the functions in |
Yeah this brings us to the difficult problem of moving between algebras... The tools in tools.g3 actually just use clifford.g3c as I had no really good way of mixing algebras. This is obviously not a dream situation. @arsenovic has a blade map setup but to my shame I never worked out how to use it |
Maybe it's time we opened this can of worms again #34 |
This makes tools/g3c a slightly more manageable length.
It also makes it easier to switch to the new numpy random API in future, which would solve our non-deterministic CI woes.