-
Notifications
You must be signed in to change notification settings - Fork 66
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
Refresh problem with 2.1 #1007
Comments
Hi, Also, is this for the same system? There are some issues with the graphics card for UVCDAT so it'd be great if you can test it on other computers as well. |
@hgohil2805 I think it wa because of #1008 then the GUI was becoming completely unresponsive. I'm leaving this open until we can confirm it's better. @stott could you try a build from master? the fix is in. Thanks. |
Yes. We'll rebuild and try it. Lowell On Thursday, February 26, 2015, Charles Doutriaux [email protected]
Professor |
@doutriaux1 Sounds good. If it works then we should close the issue. Thanks |
Hi Charles, thanks, On Thu, Feb 26, 2015 at 3:33 PM, Hardik Gohil [email protected]
Professor |
no worries
More at: https://github.com/UV-CDAT/uvcdat/wiki/Build |
Thanks. I downloaded 2.1.0 from ResourceForge over the weekend but I Lowell On Monday, March 2, 2015, Charles Doutriaux [email protected]
Professor |
Charles, After multiple attempts I'm unable to build the 2.1.0 version from git. thanks, On Mon, Mar 2, 2015 at 7:10 AM, Lowell Stott [email protected] wrote:
Professor |
ok doing this right away |
Thanks! On Mon, Mar 2, 2015 at 10:51 AM, Charles Doutriaux <[email protected]
Professor |
@stott ok I built on your system it is at
for me via X11 there's a lot of hanging. I still an pop-up error message about the bad time units but it doesn't seem to prevent resizing. I chmoded everything 777 so you can give it a try, let me know if it is also painfully slow for you or not and if the reszie issue seems to be worked out |
I just tried your build on Atmosphere. There does not appear to be a lot of The refresh problem is fixed and resizing works fine. However, the time steps do not display so that when stepping through time And, when clearing a plot, the "Clear cell" pop-up window hangs (does not Lowell On Mon, Mar 2, 2015 at 1:48 PM, Charles Doutriaux [email protected]
Professor |
yes the "time" cannot disply because your time units are broken. I guess we could fallback on simply plotting the plain time value (not converted to time since we cant) in such cases? Or should we use index? @stott if you think it is something useful please submit a new issue for this and i will put it in for 2.3 |
This worked fine in version 1.5. It is absolutely necessary to display time And what about freezing while clearing the plot? I left this open if you On Monday, March 2, 2015, Charles Doutriaux [email protected]
Professor |
@stott can you point me to the data on atmosphere please |
The data is at: atmosphere-00/stott/GENIE-Output On Mon, Mar 2, 2015 at 5:25 PM, Charles Doutriaux [email protected]
Professor |
sorry, a more explicit link would be: atmosphere-00/stott/GENIE-Output/TEST71a/biogem with in the folder biogem you'll see two .nc files. Use the "fields_biogem_3d.nc" On Mon, Mar 2, 2015 at 5:37 PM, Lowell Stott [email protected] wrote:
Professor |
On our system, we have centos 6.5 (2.6.32-504 kernel) installed. We downloaded UVCDAT 2.1.0 and Qt 4.8.4 from UVCDAT's sourceforge page, set the environment variables as specified on the website.
We can launch and plot an initial plot okay, but the application's GUI doesn't refresh or render if we maximize the window or try to plot something else. The menus are technically there, but we can't see them.
I'm not sure if it's related, but this happens often when we load a file that has error messages about time units. The smaller examples that come with UVCDAT all seem to work fine.
If we do the same thing on version 1.5 with it's appropriate Qt, we still get the warnings about time units, but we do not encounter the refresh problem with graphics.
We tried the same with Ubuntu and get exactly the same refresh problem
The text was updated successfully, but these errors were encountered: