Falk Amelung

For MiNoPy there were some FAQs. We should transfer what is useful to MiaplPy. https://github.com/geodesymiami/MiNoPy/issues/60

Suggest to use a different symbol for the step number announcement then MintPy. This will make it easier to know whether it stalled in MiaplPy proper or MintPy. Currently we...

- We could simplify by moving everything network-related into the `network_*` folder, i.e. move `/inverted/interferograms_single_reference` into `/network_single_reference/interferograms` . Edited 30 Oct: - Can we generate `/network_sequential_3/inputs` when it is needed?...

In the unwrapping step the `*.o` file may contain the `NaN or infinity found in input float data` error message below, which should be in the `*.e` file (Capturing the...

miaplpyApp.py has the `--tmp` option but in the documentation we don't have much explanation on what it means (please excuse me if I have missed it). I would talk somewhere...

When a previously run command is run again, are we consistent regarding overwriting? ISCE overwrites everything which is how it should be. `generate_ifgram.py` does not overwrite. If the output files...

**Useful information to provide in `--help`, FAQs or elsewhere in the doc::** - Why is `unwrap_ifgram.py` given the height of the satellite and the earth radius? Some explanation in the...

The order of arguments of `generate_ifgram.py` is counterintuitive. I would expect the input data and processing parameters at the beginning and the output_dir or file at the end. ``` generate_ifgram.py...

There are a few python scripts where the errors don't show up in stderr (*.e) file but in the *.o file. I suspect the error below is created by snaphu....

The number of connections is not consistent with ISCE naming: `connNum` versus `--num_connections`. So `numConn` would make more sense.