Check for data loaded prior to attemting render

Feature Requests
1

When working in UTM coordinates (X - 6 digits, Y - 7 digits) with the axes turned on + display grid, selecting a slice, clip or other daughter from an object in an existing state can cause PV to hang or at least become unresponsive for a long time. I believe that what is happening is that because the parent of the object to be rendered has not been loaded into memory the the axis are being extended back to an origin of 0,0,0 which could be 800,000 m in X and 7,000,000 m in Y and PV is going off and rendering a grid. Eventually it will load the data and shrink back to the project limits and all will be fine but it can take minutes to hours depending on the size of the parent.

Request that prior to rendering, PV check to see that the parent has been loaded into memory and if not then load prior to attempting to render. It would be nice to think that ticking the box to load all variables in the Settings menu would do this for you but it appears to have no effect or maybe only loads the data for those objects which are visible in the saved state.

2

The actual issue is this one: Transforming results to user-defined (local) coordinate systems

Lets fix things correctly :slight_smile:

3

Mathieu, you know the code better than me so I won’t argue BUT if it was simply a transformation issue then I’d expect to see the same lag when we select the daughter of an object which has already been loaded into memory. We don’t. My workflow, if I remember to do it in time, is to first select the parent and reload it before selecting the daughter. There is then very little lag.