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

Obfuscate nxsdk information #228

Merged
merged 5 commits into from Jun 21, 2019
Merged

Obfuscate nxsdk information #228

merged 5 commits into from Jun 21, 2019

Conversation

@drasmuss
Copy link
Member

@drasmuss drasmuss commented Jun 10, 2019

Intel has requested that we obfuscate information related to the nxsdk API (since it is not publicly available). This is an attempt at doing so.

Note that the goal here is not to make the obfuscated information unrecoverable, but simply to obscure it from a surface viewing.

There are three major things I was considering in the obfuscation:

  1. Hiding any direct calls to nxsdk objects
  2. Renaming any nengo-loihi classes/functions/variables that directly correspond to equivalent nxsdk objects
  3. Hiding any constant values (e.g. register sizes) that are based on information inside nxsdk
nengo_loihi/builder/connection.py Outdated Show resolved Hide resolved
Loading
nengo_loihi/builder/connection.py Outdated Show resolved Hide resolved
Loading
nengo_loihi/conv.py Outdated Show resolved Hide resolved
Loading
nengo_loihi/block.py Outdated Show resolved Hide resolved
Loading
@tbekolay tbekolay force-pushed the obfuscate branch 5 times, most recently from 0c9b587 to 1756408 Jun 20, 2019
drasmuss added 5 commits Jun 21, 2019
This decouples Nengo Loihi from NxSDK in preparation for
obfuscating the NxCore API.
The test failure seems to be a very small floating point
difference that doesn't happen in earlier TensorFlow versions,
so we downgrade for now and will look into the differences
in more detail later.
This seems to be the underlying issue when two processes attempt
to build Loihi models at the same time. Reproducing the error and
fully debugging it is time consuming, so we're adding these print
statements in for now so that if the tests randomly fail again we
can get some more insight for further debugging.
@tbekolay tbekolay merged commit 09053af into master Jun 21, 2019
1 of 3 checks passed
Loading
@tbekolay tbekolay deleted the obfuscate branch Jun 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants