save_rmf
- sherpa.astro.ui.save_rmf(id, filename=None, resp_id=None, bkg_id=None, clobber=False)
Save an RMF data set to a file.
Added in version 4.16.0.
- Parameters:
id (int or str) – The identifier for the data set containing the RMF or the filename (the latter is used when filename is set to None, and in this case the id is set to the default identifier, as returned by
get_default_id
).filename (str or None) – The name of the file to write the RMF to (when the id value is explicitly given). Note that the format is always FITS.
resp_id (int or str, optional) – The identifier for the RMF within this data set, if there are multiple responses.
bkg_id (int or str, optional) – Set if the background RMF should be written out rather than the source RMF.
clobber (bool, optional) – This flag controls whether an existing file can be overwritten (
True
) or if it raises an exception (False
).
- Raises:
sherpa.utils.err.ArgumentErr – If the data set does not contain a RMF.
sherpa.utils.err.IOErr – If
filename
already exists andclobber
isFalse
.
See also
Notes
The function does not follow the normal Python standards for parameter use, since it is designed for easy interactive use. When called with a single un-named argument, it is taken to be the
filename
parameter. If given two un-named arguments, then they are interpreted as theid
andfilename
parameters, respectively. The remaining parameters must be given as named arguments.Examples
Write out the RMF data from the default data set to the file ‘src.rmf’:
>>> save_rmf('src.rmf')
Over-write the file it it already exists, and take the data from the data set “jet”:
>>> save_rmf('jet', 'out.rmf', clobber=True)