Hi team,
I was wondering if there was any appetite for including acquisition parameters (eg. waveform, gate times, frequency, filters etc) in the AEM netcdf files. This would facilitate easier inversion using a range of different inversion frameworks. Obviously it would be different for each system but if we use a yaml file to account for different inputs then I imagine it could be accounted for.
Here is a copy of some of the system files that we currently use for inversion here at GA.
SkyTEM_LM_HM_system_details.docx
Neil
Hi team,
I was wondering if there was any appetite for including acquisition parameters (eg. waveform, gate times, frequency, filters etc) in the AEM netcdf files. This would facilitate easier inversion using a range of different inversion frameworks. Obviously it would be different for each system but if we use a yaml file to account for different inputs then I imagine it could be accounted for.
Here is a copy of some of the system files that we currently use for inversion here at GA.
SkyTEM_LM_HM_system_details.docx
Neil