Currently, CLOVER can be broken by deleting the kerosene entry from a location's load data file.
The proposed fix would be that, if CLOVER detects that this data has been deleted, then it auto fills the value as zero. I.E., it assumes that, by deleting the kerosene information, the user does not wish to include kerosene in their set up. The profile generated will also contain zeros at all times.
Currently, CLOVER can be broken by deleting the kerosene entry from a location's load data file. The proposed fix would be that, if CLOVER detects that this data has been deleted, then it auto fills the value as zero. I.E., it assumes that, by deleting the kerosene information, the user does not wish to include kerosene in their set up. The profile generated will also contain zeros at all times.