You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In this example the information in both catalogs in the same. But the new syntax allows more possibilities, for example adaptive binning, or combining spectra from different instruments (or passbands) with large gaps in between or different spectral resolutions. The ```tr``` (transmission) column, which is just a binary "use/don't use" flag becomes useless since the grid does not need to be uniform anymore.
263
265
264
266
Even when using the old format, the treatment of these spectrum files is also more correct in FAST++. The ```bin``` column correctly combines multiple data points into a single measurement (using inverse variance weighting) rather than simply using the first value of a bin (why this is implemented in this way in FAST-IDL, I do not know). The order of the columns in the file do not matter, while FAST-IDL assumes a fixed format (but does not tell you).
267
+
268
+
269
+
# Additional documentation
270
+
271
+
## Adding new filters
272
+
273
+
For compatibility reasons, the filter database format is the same as that of EAzY and FAST. This is an ASCII/text file which contains all the filters, listed one after the other. The format must be:
274
+
```
275
+
num_pts [optional extra information...]
276
+
id lam trans
277
+
id lam trans
278
+
id lam trans
279
+
...
280
+
num_pts [optional extra information...]
281
+
id lam trans
282
+
id lam trans
283
+
id lam trans
284
+
...
285
+
```
286
+
287
+
In this example ```num_pts``` must be the number of data points in the filter response curve. Then for each data point, ```id``` is the identifier of that point. This ID is unused by FAST++, but it is recommended to make it start at one and increment by one for each data point (consistency checks may be implemented in the future). Then, ```lam``` is the wavelength in Angstrom, and ```trans``` is the filter transmission at that wavelength.
288
+
289
+
The overall normalization factor of the filter transmission does not matter, as the filters are automatically re-normalized to unit integral before the fit. If ```FILTERS_FORMAT=0```, the integral of ```lam*trans``` is normalized to unity, and if ```FILTERS_FORMAT=1``` then the integral of ```lam^2*trans``` is set to unity. The flux in a band is then computed as the integral of ```lam*trans*flx``` (for ```FILTERS_FORMAT=0```) or ```lam^2*trans*flx``` (for ```FILTERS_FORMAT=1```), where ```flx``` is the flux density (```Slambda```) in ```erg/s/cm^2/A```. This is exactly the same behavior as in FAST and EAzY.
290
+
291
+
To add new filters, simply append them to the end of the ```FILTER.RES``` file following the format above. For example, if your filter has 11 data points you would write:
292
+
```
293
+
...
294
+
11 my custom favorite filter (lambda0=5000 A)
295
+
1 4000.0 0.00
296
+
2 4200.0 0.10
297
+
3 4400.0 0.20
298
+
4 4600.0 0.40
299
+
5 4800.0 0.50
300
+
6 5000.0 0.55
301
+
7 5200.0 0.60
302
+
8 5400.0 0.40
303
+
9 5600.0 0.20
304
+
10 5800.0 0.10
305
+
11 6000.0 0.00
306
+
```
307
+
308
+
The wavelength step of the tabulated filter does not need to be constant, and the filter is assumed to have zero transmission below the minimum and above the maximum tabulated wavelength.
0 commit comments