Make network loading gap epsilon configurable for sLTM #118
Labels
documentation
Improvements or additions to documentation
done pending merge
enhancement
New feature or request
sLTM
Milestone
there are three iterative procedures within sLTM each of which may benefit from its own configurable epsilon:
currently we use the default of 0.001but it is fixed which is not ideal
The text was updated successfully, but these errors were encountered: