f_gridFromSensorAMSU

Workspace.f_gridFromSensorAMSU(self: pyarts.arts._Workspace, f_grid: pyarts.arts.WorkspaceVariable | pyarts.arts.Vector | None = self.f_grid, lo_multi: pyarts.arts.WorkspaceVariable | pyarts.arts.Vector | None = self.lo_multi, f_backend_multi: pyarts.arts.WorkspaceVariable | pyarts.arts.ArrayOfVector | None = self.f_backend_multi, backend_channel_response_multi: pyarts.arts.WorkspaceVariable | pyarts.arts.ArrayOfArrayOfGriddedField1 | None = self.backend_channel_response_multi, spacing: pyarts.arts.WorkspaceVariable | pyarts.arts.Numeric | None = .1e9, verbosity: pyarts.arts.WorkspaceVariable | pyarts.arts.Verbosity | None = self.verbosity) None

Automatically calculate f_grid to match the sensor.

This method is handy if you are simulating an AMSU-type instrument, consisting of a few discrete channels. The case that channels touch, as for MHS, is handled correctly. But the case that channels overlap is not (yet) handled and results in an error message.

The method calculates f_grid to match the instrument, as given by the local oscillator frequencies lo_multi, the backend frequencies f_backend_multi, and the backend channel responses backend_channel_response_multi.

You have to specify the desired spacing in the keyword spacing, which has a default value of 100 MHz. (The actual value is 0.1e9, since our unit is Hz.)

The produced grid will not have exactly the requested spacing, but will not be coarser than requested. The algorithm starts with the band edges, then adds additional points until the spacing is at least as fine as requested.

There is a similar method for HIRS-type instruments, see f_gridFromSensorHIRS().

Author(s): Stefan Buehler, Mathias Milz

Parameters: