Skip to content
This repository was archived by the owner on Dec 2, 2021. It is now read-only.

Feature/use endaq #8

Open
wants to merge 4 commits into
base: development
Choose a base branch
from
Open

Feature/use endaq #8

wants to merge 4 commits into from

Conversation

CrepeGoat
Copy link
Contributor

This is a big one, but I don't expect a thorough review of all the changes. The big ones are:

  • removed all references to the nre_utils code and replaced it with the corresponding endaq.calc functions
  • changed batch to use endaq.ide.get_doc
  • changed the unit tests to install endaq.ide/calc directly from GitHub -> this lets me use any fixes in those codebases (e.g., Fix/butterworth endaq-python-calc#55)

Comment on lines -171 to +143
return np.empty((3, 0), dtype=np.float)
return pd.DataFrame(
np.empty((0, 3), dtype=np.float),
index=pd.Series([], name="time"),
columns=pd.Series(["X", "Y", "Z"], name="axis"),
)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not sure what specifically is using this output, but it can be risky returning data initialized by np.empty.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Generally I'd agree, but in this case the generated array is of shape (0, 3), meaning it has no elements. So here there's not really any risk of e.g. non-determinism or pseudo-memory-leaking or anything like that.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants