Posts

Showing posts from September, 2017

Important update about Herschel PACS and SPIRE filters

A correction that was made a while ago but I thought I'd point out for those who did not notice the update on the filter file. Will try to update in real time now that we have a MAGPHYS user blog! The Herschel PACS and SPIRE response functions originally introduced in the MAGPHYS filter file were in the wrong units (filters #169 to #174). The effect on SED fits is small, but can be noticeable at the level of a few K for the coldest dust component. Thanks very much to Steve Maddox and Loretta Dunne for spotting this! I updated the filter file with the correct response functions in Nov 2016. The new PACS and SPIRE filters are #441 to #446 in the filter file and they are labelled "recommended": those are the ones that should be used for Herschel point source fits. Please note that for extended sources we include recommended SPIRE response functions (#447 to #449) provided by Steve Maddox.

Bug found in high-z version of the fitting code

There was a bug on the fitting code of the MAGPHYS-HIGHZ package (fit_sed_highz.f), related to the way it deals with fluxes ~ 0 in the model SEDs at high-z where some filters sample the SED bluewards of the Lyman break. Thanks to M. Maseda for finding the bug! The bug has been fixed and you can get the corrected version of the code on the main site (please go to Download and look under MAGPHYS high-z extension).

Bug found on Subaru g+ filter

A bug was recently found on the filter file regarding the Subaru g+ filter response function (#333). Thanks to the users who wrote to me about it! The response function was wrongly entered in the file, which resulted in bad fits when that filter was used. This bug has been corrected in the filter file. If you are using an older version, please download the new filter file in the MAGPHYS main site and replace it in your MAGPHYS directory. To check if you have the correct version, check the filter name line (e.g. in the file filters.log). If you are using the correct version, it should be labelled as: 333 Subaru g+ [added June 2012; CORRECTED Aug 2017]