Viktor parser - old GEF file

🚀 Support (Q&A)
1

Given the following .GEF file:

38-49.gef (3.8 KB)

The following InternalError was raised:

image
image769×139 11.5 KB

Any idea how to fix this?

2

Hi Johan,

It’s been a while since I looked into these GEF files, but I see that there are only 2 columns: depth and qc.

The internal error raises because it tries to calculate the Rf values, using Rf = fs / qc. However, since the ‘fs’ column is missing, it raises a KeyError here.

Unfortunately, since there is not enough data in this GEF to easily deduce these values, I don’t know how to solve this myself, but maybe @rweigand can help out?

3

It is a very old GEF, so not very common. I gues the value of the rf should be None in this case?

4

Hi

Indeed, there are lots of different versions of gefs out there, and we’ve in our implementation set a limit on the amount of data that needs to be in the gef: depth, Qc and either Rf or Fs. If any of those three things is missing, our parser will trip. This choice was made because all the other things we allow you to do with the SDK such as classifying, plotting, etc, all expect/need a friction signal (Rf/Fs).

So yes, you can still work you way around this by e.g.:

  • Adding a 0 column to the .gef file
  • Adding a 0 column during preprocessing and then sending that amended result into the parser during ParamsFromFile

Hope that helps!

5

Hi,

Thanks for the response. Yes those workaround sound logic to me. My main point was to share this use case as it might make the parser stronger. We did just what you said. Adjust the original .GEF file and parse it.