I don't think the LISST functions are able to remove variables from the final outputs, so un-used analoginputs still show up in the final nc files, at the moment. Can the LISST codes be updated so that adding "drop_vars: ['AnalogInput1','AnalogInput2']" to the .yaml file would result in those fields not showing up in the final nc?
Similarly, it might be nice if the command line output said something about drop_vars, i.e. 'Dropping variables 'x and y' from the final nc file.'
I don't think the LISST functions are able to remove variables from the final outputs, so un-used analoginputs still show up in the final nc files, at the moment. Can the LISST codes be updated so that adding "drop_vars: ['AnalogInput1','AnalogInput2']" to the .yaml file would result in those fields not showing up in the final nc?
Similarly, it might be nice if the command line output said something about drop_vars, i.e. 'Dropping variables 'x and y' from the final nc file.'