s1tiling.libs.otbwrappers.SARCartesianMeanEstimation
- class s1tiling.libs.otbwrappers.SARCartesianMeanEstimation(cfg: Configuration)[source]
Bases:
OTBStepFactory
Factory that prepares steps that run SARCartesianMeanEstimation as described in Normals computation documentation.
SARCartesianMeanEstimation estimates a simulated cartesian mean image thanks to a DEM file.
Requires the following information from the configuration object:
ram_per_process
Requires the following information from the metadata dictionary
input filename
output filename
Note: It cannot be chained in memory because of the
directiontoscandem*
parameters.New methods & Specialized methods
__init__
Constructor.
_get_canonical_input
Helper function to retrieve the canonical input associated to a list of inputs.
_update_filename_meta_pre_hook
Injects the
reduce_inputs_insar()
hook in step metadata, and provide names clear from polar related information.Complete meta information with hook for updating image metadata w/ directiontoscandemc, directiontoscandeml and gain.
Extract back direction to scan DEM from SARDEMProjected image metadata.
Returns the parameters to use with SARCartesianMeanEstimation OTB application to compute cartesian coordinates of each point of the origin S1 image.
Return the requirement context that permits to fix missing requirements.
Set SARCartesianMeanEstimation related information that'll get carried around.
Methods inherited from parent
Directory used to store temporary files before they are renamed into their final version.
Duplicates, completes, and returns, the meta dictionary with specific information for the current factory regarding tasks analysis.
This specialization of
StepFactory.build_step_output_tmp_filename()
will automatically insert.tmp
before the filename extension.This specialization of
check_requirements()
checks whether the related OTB application can correctly be executed from S1Tiling.Instanciates the step related to the current
StepFactory
, that consumes results from the previous input steps.Permits to have steps force the output pixel data.
Returns the names of typical result files in case their production is required (i.e. not in-memory processing).
Accessor to where output files will be stored in case their production is required (i.e. not in-memory processing).
Attributes and properties
OTB Application property.
Property image_description, used to fill
TIFFTAG_IMAGEDESCRIPTION
Step Name property.
Name of the "in" parameter used by the OTB Application.
Name of the "out" parameter used by the OTB Application.
Property ram_per_process
- _do_create_actual_step(execution_parameters: Dict, input_step: AbstractStep, meta: Dict) AbstractStep
Instanciates the step related to the current
StepFactory
, that consumes results from the previous input step.We expect the step metadata and the GDAL image metadata to have been updated.
1. Steps that wrap an OTB application will instanciate this application object, and:
either pipe the new application to the one from the input step if it wasn’t a first step
or fill in the “in” parameter of the application with the
out_filename()
of the input step.
1-bis. in case the new step isn’t related to an OTB application, nothing specific is done, we’ll just return an
AbstractStep
- _update_filename_meta_post_hook(meta: Dict) None
Hook meant to be overridden to fix product metadata by overriding their default definition.
Called from
update_filename_meta()
- build_step_output_filename(meta: Dict) str | List[str]
Returns the names of typical result files in case their production is required (i.e. not in-memory processing).
This specialization uses
gen_output_filename
naming policy parameter to build the output filename. See the Available naming policies.
- build_step_output_tmp_filename(meta: Dict) str | List[str]
This specialization of
StepFactory.build_step_output_tmp_filename()
will automatically insert.tmp
before the filename extension.
- check_requirements() Tuple[str, str] | None
This specialization of
check_requirements()
checks whether the related OTB application can correctly be executed from S1Tiling.- Returns:
A pair of the message indicating what is required, and some context how to fix it – by default: install OTB!
- Returns:
None
otherwise.
- complete_meta(meta: Dict, all_inputs: List[Dict[str, AbstractStep]]) Dict [source]
Complete meta information with hook for updating image metadata w/ directiontoscandemc, directiontoscandeml and gain.
- create_step(execution_parameters: Dict, previous_steps: List[List[Dict[str, AbstractStep]]]) AbstractStep
Instanciates the step related to the current
StepFactory
, that consumes results from the previous input steps.1. This methods starts by updating metadata information through:
complete_meta()
on theinput
metadatas.2. Then it updates the GDAL image metadata information that will need to be written in the pipeline output image through
update_image_metadata()
.3. Eventually the actual step creation method is executed according to the exact kind of step factory (
ExecutableStepFactory
,AnyProducerStepFactory
,OTBStepFactory
) through the variation point_do_create_actual_step()
.While this method is not meant to be overridden, for simplity it will be in
Store
factory.Note: it’s possible to override this method to return no step (
None
). In that case, no OTB Application would be registered in the actualPipeline
.
- fetch_direction(inputpath, meta: Dict) None [source]
Extract back direction to scan DEM from SARDEMProjected image metadata.
- property image_description: str | List[str]
Property image_description, used to fill
TIFFTAG_IMAGEDESCRIPTION
- output_directory(meta: Dict) str
Accessor to where output files will be stored in case their production is required (i.e. not in-memory processing)
This property is built from
gen_output_dir
construction parameter. Typical values for the parameter are:os.path.join(cfg.output_preprocess, '{tile_name}'),
wheretile_name
is looked intometa
parameterNone
, in that case the result will be the same astmp_directory()
. This case will make sense for steps that don’t produce required products
- property param_in: str
Name of the “in” parameter used by the OTB Application. Default is likely to be “in”, while some applications use “io.in”, often “il” for list of files…
- property param_out: str
Name of the “out” parameter used by the OTB Application. Default is likely to be “out”, whie some applications use “io.out”.
- parameters(meta: Dict) Dict[str, str | int | float | bool | List[str]] [source]
Returns the parameters to use with SARCartesianMeanEstimation OTB application to compute cartesian coordinates of each point of the origin S1 image.
- property ram_per_process
Property ram_per_process
- requirement_context() str [source]
Return the requirement context that permits to fix missing requirements. SARCartesianMeanEstimation2 comes from normlim_sigma0.
- tmp_directory(meta) str
Directory used to store temporary files before they are renamed into their final version.
This property is built from
gen_tmp_dir
construction parameter. Typical values for the parameter are:os.path.join(cfg.tmpdir, 'S1')
os.path.join(cfg.tmpdir, 'S2', '{tile_name}')
wheretile_name
is looked intometa
parameter
- update_filename_meta(meta: Dict) Dict
Duplicates, completes, and returns, the meta dictionary with specific information for the current factory regarding tasks analysis.
This method is used:
while analysing the dependencies to build the task graph – in this use case the relevant information are the file names and paths.
and indirectly before instanciating a new
Step
Other metadata not filled here:
get_task_name()
which is deduced from out_filename by defaultout_extended_filename_complement()
It’s possible to inject some other metadata (that could be used from
_get_canonical_input()
for instance) thanks to_update_filename_meta_pre_hook()
.This method is not meant to be overridden. Instead it implements the template method design pattern, and expects the customization to be done through the specialization of the hooks:
_update_filename_meta_pre_hook()
,