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

Move random functions to their own file #196

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

eric-wieser
Copy link
Member

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.

@eric-wieser eric-wieser added the Maintenance Code cleanup without behavior changes label Nov 9, 2019
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.
@lgtm-com
Copy link

lgtm-com bot commented Nov 9, 2019

This pull request introduces 2 alerts when merging c7a5058 into aec1960 - view on LGTM.com

new alerts:

  • 2 for 'import *' may pollute namespace

@lgtm-com
Copy link

lgtm-com bot commented Nov 10, 2019

This pull request introduces 2 alerts when merging 9968d86 into aec1960 - view on LGTM.com

new alerts:

  • 2 for 'import *' may pollute namespace

Copy link
Member

@hugohadfield hugohadfield left a 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

@eric-wieser
Copy link
Member Author

eric-wieser commented Nov 11, 2019

Except I screwed up and CI fails.

Some of the functions in tools.g3 seem to assume len(Multivector.value) == 32 - which actually makes them g3c tools, right?

@hugohadfield
Copy link
Member

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

@hugohadfield
Copy link
Member

Maybe it's time we opened this can of worms again #34

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Maintenance Code cleanup without behavior changes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants