@Cadair, I admire your appeal to logic :-) But, as far as I can tell, the only routine in GOES that ever calls CHIANTI is make_goes_chianti_response.pro - this is the file that remakes the SSW routines that have the temperature and emission measure lookup tables inside them (see discussion by @ehsteve elsewhere in this PR) - the tables that @DanRyanIrish has ported to CSV here. 

For radiative losses, the GOES object seems to rely exclusively on this extra lookup text file 'chianti5p1_rad_loss.txt' (which @DanRyanIrish has ported as chianti_rad_loss.csv), and there is no routine that updates it automatically. It looks like the text file was created entirely manually by someone running rad_loss.pro and dumping the output by hand into a text file. The file is then read by GOES as required to work out radiative losses via interpolation (the exact file that does this is calc_rad_loss.pro).

If anyone has better insights, please chime in!