Currently the code assumes that all metallicity files contain the same number (and values) of ages defined. This number is taken (arbitrarily) from the first metallicity file (alphabetically).
This means that if for some reason this file contains a different number of ages, the checker will not notice this and the best fit function will fail down the line thus wasting a lot of time.
Currently the code assumes that all metallicity files contain the same number (and values) of ages defined. This number is taken (arbitrarily) from the first metallicity file (alphabetically).
See: https://github.com/asteca/ASteCA/blob/master/functions/_in/get_met_ages_values.py#L128
This means that if for some reason this file contains a different number of ages, the checker will not notice this and the best fit function will fail down the line thus wasting a lot of time.