Test PcCoarsen2D.cpp

[WorkGitAccount]

References #18

The constructor in the preprocessing phase calls the cyPackage through PcCoarsen2D.cpp.

Test and verify behavior in python.

• [ ] Passes discrete test case (squarepoissond case with 64 points coarsened to 16)
• [ ] Passes demo test case (size n=400 in squarepoissond case)

[WorkGitAccount]

Stepped through matlab debugger paying attention to the constructor.

PcCoarsen2D is called in just one line of code in the constructor. Can export matlab data at certain break points to create expected test data like how it is done in other tasks. Input data can be generated in python with the squarepoisson provided function.

The rewrite of PcCoarsen in #25 needs to be finished and working to proceed.

[t:30]

[WorkGitAccount]

X and Y data is sometimes flipped compared to matlab expected data. Possibly an ordering difference between languages.

The discrete case gave slightly inconsistent results after coarsening. Could be a datatype issue or rounding error. Will investigate these issues with larger test cases.

[t:30]

[seanbsu]

• didn't know where you were Tanner on the constructor function so just in case you were still working on this coarsen function I started a tenative port for the constructor function. If its not needed then i can easily delete my local branch that has it.
• got the port up to initalizing the levels data ported over but not tested

[t:120]

[WorkGitAccount]

Added more discrete test case and code to track down inconsistencies. Want to verify other cases from the gallery example data as well.

[t:60]

[WorkGitAccount]

Tested Coarsen from 64->16 by Sorting [x,y] ascending by x first then by y. Then compare np.allclose() with expected to python output after coarsening. One [x,y] point in the list is different between matlab and python. Demonstrated by RunPcCoarsen.py.

Could be a weighted rounding discrepancy with data types between languages

With the anomaly here, cannot guarantee test cases will pass.

[t:120]