Errors with large number of splays

[ggpls]

I have been trying to process a survex raw data file with a lot of splays. It failed with numerous error msgs. I checked that it wasnt a format issue by re-running the initial part of the file with splays for the 3_n survey which had run OK before I added the additional splays from 4_n stations. Then I added just the splay data for station 4_1, again it ran. More splays it fails.

Attched raw data files Lagans_entrance will run. lagans_entrance-4splays wont.

I wonder whether this is a memory allocatiion error as the errors listed dont describe stations that are included in the data eg entrance 150.06. I could sort it out by reducing tthe number of stations incuded in the file, but at a min it should say somewhere how many splays the prog can deal with and rather better it work for the sort of numbers of splays that people are using in survey now.

Comments/Fixes???

Sorry cant see where I attach the files, does it come later?

[ggpls]

file with splays runs OK

[ggpls]

File with more splays wont run

[Olly Betts]

There is no fixed limit on the number of splays.

The station 150.06 comes from this line:

4_3             150.06  -10.58  7.404

The .. is missing there, so that's from station 4_3 to station 150.06. There's another case of this further down.

You also have some 4.2 instead of 4_2, which is why you get warnings like:

lagans_entrance-4splays.svx:791: error: “lagans_entrance.4” can’t be both a station and a survey

Since 4.2 would be station 2 in survey 4 inside the current survey, and this survey already has a station 4.

And finally some of your lines have control character hex 0x1f in, which is why you get:

lagans_entrance-4splays.svx:791:2: error: Character “” not allowed in station name (use *SET NAMES to set allowed characters)

The station names in question look like 4X_15 where X is that control character. I guess that's a bug in the script you seem to be generating this with.

Fixing all the above issues, the file processes for me - I'm not seeing any bugs in Survex here, just several issues in your input file (quite likely bugs in the script which apparently produced it).