Skip to content

Conversation

@nukenukenukelol
Copy link
Contributor

Add chord length test to the spherical case. The logic is similar to the polar one. We first find the expected chord length via the entry and exit time calculation. Then, we use an accumulator to keep track of total time we spend on traversal.

@cgyurgyik
Copy link
Contributor

I'm sorry, I'm still a bit lost on this. How would I actually write a unit test using this? Is there any way to add chord length tests to our testing .m file?

@ak-2485
Copy link
Contributor

ak-2485 commented Apr 17, 2020

@cgyurgyik our function could output [rVoxels, thetaVoxels, phiVoxels, traversal time] and we could then have a verification on this value where the expected value is calculated externally in a different function.

@ak-2485
Copy link
Contributor

ak-2485 commented Apr 17, 2020

@nukenukenukelol @cgyurgyik after you review the PR #103 can @nukenukenukelol migrate the above into the new code?

@nukenukenukelol
Copy link
Contributor Author

@nukenukenukelol @cgyurgyik after you review the PR #103 can @nukenukenukelol migrate the above into the new code?

Yes will do

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants