-
Notifications
You must be signed in to change notification settings - Fork 13
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
isofill broken #5
Comments
@danlipsa also I now get these warnings:
|
fixes the issue |
@doutriaux1 I'll take a look. How to you build/install cdat with the split vcs? |
you can use the uvcdat branch |
or simply install directly from the vcs repo. |
don't forget to use: |
@doutriaux1 Sounds good. I'll take a look. |
@danlipsa after reverting your commit i get these failures Shouldn't I get more? |
@doutriaux1 You should not get any failure - assuming I started from a repo with no failures. |
@doutriaux1 Everything I changed was in one commit, including the tests - this is the benefit of using just one commit 😄 |
https://open.cdash.org/viewTest.php?onlyfailed&buildid=4560986 actually looks like the baselines are more wrong |
@danlipsa will look into it as the priority. Looks like the labels are wrong in this test "https://open.cdash.org/testDetails.php?test=484965777&build=4560986". All other tests looks reasonable to me but please post message here if we are mistaken. |
@aashish24 Why do you say the labels are wrong? |
@danlipsa on the baseline of the test pointed to by @aashish24 the labels are on the right, they should be o the left, no? |
…points. We set scalar value for hidden points to a valid value.
* BUG #1265: Fix datawc zoom-in for geographic projections. * BUG #5: vtkPolyData::RemoveDeletedCells does not remove GlobalIds or points. We set scalar value for hidden points to a valid value. * BUG: Set hidden points scalars and vectors to minimum value from the range.
@doutriaux1 @danlipsa should we close this now? |
@danlipsa I think your PR broke vcs
using commit: 507d2bc the uvcmetrics test 04 works, any commit after that I get the wrong colors for an isofill on test 04
leads to bad plots, look for example at: https://open.cdash.org/testDetails.php?test=484915834&build=4560808
Notice that we now have a level that shows values greater than 300 when the max is at: 294.
We fixed a similar issue before: CDAT/cdat#1947
PR for fix was : CDAT/cdat#2027
This is an URGENT matter for the diags due out this week.
The text was updated successfully, but these errors were encountered: