-
Notifications
You must be signed in to change notification settings - Fork 57
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
New style tests closes #44 #47
Conversation
…e, projected area, and surface area constraints using a box geometry
I added some new tests and unfortunately it looks like the test 9 (colinearity constraint) derivatives are producing different values on different architectures. It passes on my machine and one of the Docker images. Our choices are:
I don't have time to fix the underlying issue. (edit: I at least identified the underlying issue and opened a ticket) |
… post constraint, deactivated test 9
I vote for option 1. I don't see much value in maintaining features that aren't ever used. Could you post something in slack to see if anyone can think of a reason it should not be deprecated? |
Differences in compilers were causing some pygeo pointsets to have exactly and nearly zero values in different places which was causing the ColinearityConstraint and PlanarityConstraint to have spurious derivative values in the baseline case, which has a lot of true zero input values. I will open an issue and we can decide later whether to accept the issue or deprecate |
… Stop checking the derivs for the baseline case
Other than those two points, the tests look good and they run fine on my installation. Do you want me to check anything else in the tests themselves? |
No, I don't have anything else in particular to review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, I would prefer if the tests have more descriptive names (along with the ref files), but I guess that's more of a "nice to have".
Let's pull it in for now, I need to move on to some other tasks. Right now the test names match the DVGeo tests which are numbered sequentially |
Yeah fair, I'm not actually a maintainer for pygeo so I'll wait for others to review. |
e19f71b
Sorry @anilyil , @nwu63 |
🍾 Thanks @bbrelje for your hard work on this |
…olab#47 is merged. Updated the input file archive to include sabet's fuselage FFD
* checkpoint * fix typo in docstring * several fixes related to use cases with a symmetry plane * fixed some integer divisions * added the optional coordinate transformation routines * bug fix in the section local dv class * editing the symmetry fix a bit * clarified comments * too many typo fixes. added test for the coord xfer feature * format and lint. changed "dir" argument to "mode" * added pyspline solver test. this should fail until the pyspline pr #47 is merged. Updated the input file archive to include sabet's fuselage FFD * flake fix * minor tolerance adjustment on ffd generation test. this fails on my laptop with 1e-15 rel tolerance. the error is at 1.1e-15. Moved the tolerance to 1e-14, which should be plenty accurate * addressing todos * minor rewording * addressing comments
Purpose
This PR updates all unit tests to the new testflo standard and adds a little bit of new coverage for DVconstraints. There is also a small bugfix that gets the blocks tests to run (they didn't since scipy 1.3.0)
Type of change
What types of change is it?
Select the appropriate type(s) that describe this PR
Testing
All the old test data was ported over into the new file format so all the DVGeometry tests are producing the exact same results as before. Test coverage is significantly expanded and more maintainable going forward.
Checklist
Put an
x
in the boxes that apply.flake8
andblack
to make sure the code adheres to PEP-8 and is consistently formatted