open TELEMAC-MASCARET The mathematically superior suite of solvers

I downloaded latest beta version and found that when mapping lidar using 2D interploator on to large Selafin mesh the program exists without any error warning

The old BK 3.3.4 managed this mapping with no problem

regards

Hi,

Can you share more details of what you're doing?

- How big is the mesh? (# of elements/nodes)?
- what is the size/resolution of the lidar coverage?
- Is it a GeoTIFF that you converted to a r2s?
- Which interpolation method have you chosen?

Cheers... Martin

Hi Martin,

The data is an xyz ascii format
I have explored this a bit more and sometimes it works and othertimes it does not for the same data which could be a system type problem
the mapping works always if i use triangulaton
but the interpolator for inverse distance might work and might just exit (could be a memory issue with this procedure)
but there appears to be inconsistency I will explore it on another computer to see

Aside to the above the linear interpolation gives an error warning when used

An example of the inconsistency is
the original file has c 250,000 xyz point and this file never works with the 2d interpolator on any size mesh
i extracted a smaller subset from this file of c. 38,000 data points
it works if i bring this file in first of all
then view it in the 2d plot viewer then
create an interpolator2d and pull the data tile into it and then open the mesh i want to map it onto and map it it will work

if i bring the xyz file in and dont view it and do everything else the same it will exit the porbram when i map it
as i said in the previous post it appears to me to be some sort of memory problem

Is the original data GeoTIFF that you've converted to xyz?
If so try saving the GeoTIFF to an r2s and just use MapOject directly.

Are you using BlueKenue 64 bit version?

Alan will be back online sometime this week.
He will have a more insight into this if it is a memory issue.

Not sure what the original lidar format was before i got the data
but the data supplied to be was lidar in ascii x,y,z with a horizontal spacing of 0.5m between data points and 251,725 xyz points with 2 decimal place resolution as a csv file, as below
725086.75,673047.75,-2.72
725087.25,673047.75,-2.77
725087.75,673047.75,-2.76
725086.25,673048.25,-2.55
725086.75,673048.25,-2.73
725087.25,673048.25,-2.88
725087.75,673048.25,-2.92
725084.25,673048.75,-2.80
725084.75,673048.75,-2.68
725085.25,673048.75,-2.66

I am using 64 bit version
and this data works when i use triangulation as opposed to interploator

OK, I've reproduced the error...
I'll have a stab at debugging this but We may have to rely on Alan to properly sort this.

Cheers... Martin

Please upgrade to BK 3.12.27-beta to get the most recent version as of 28 Jan 2025.

Kindly... Alan

That works fine thank you

Just to note that immediate error when importing a surfer grid file whereas the original version has no problem
error message is ERROR: while allocating data space

Great to hear and you're welcome.

To be clear; you've found another bug when importing a surfer grid file? If you have a very small example surfer grid file that reproduces the issue please share it. Then I will debug.

Kindly... Alan