-
Notifications
You must be signed in to change notification settings - Fork 101
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Separate solve, solve_eit, compute_b, and compute_jac (#43)
- Docstrings style back to numpy-style, NDArray>> np.ndarray - Move the computation of H in setup() - transform EitBase to an absclass with absmethod "setup" and "_compute_h" - add "_check_solver_is_ready()" which raise SolverNotReadyError if setup() not called before solving for example. - modify msg of _check_solver_is_ready and fix missing call in jac.gn - bp, jac, greit and svd modified to fit ne EitBase - "map" method only in eitBase (same impletation in fac, bp, greit) - add/enhance doctring (numpy-format) in all 4 files and add typehints - spliting computation of potential dist, jac, b (see new methods compute_*) - using those directly in EitSolvers - solve and solve_eit (assuring bck compatibility) with new implementation - the method still return Fwd results (to minimize back compatility ) but contain only the voltages, can be extended with futher computed data e.g. diff_op or others info - fix gn solver jac and v0 were not actualizated, now passing x0 - put old test in unit test frame! now bay calling the script all test are run and a protocols is printed in term - to set the ref electrode a new set method has been added to Forward - solve >> handle ex_line (return f[0, :].ravel()) - jac=np.vstack(jac) also in compute_jac returns jac and not jac_i like the older solve - b=np.vstack(b_matrix) - Suppression of K^-1 for nodes potential - the inversion is still used but only for building the jac - correction of the output of f (ex_mat has not been cheke in the scope of of solve) - add intern _get_boundary _volt method to avoid multple code reapting and add note for v0 after calculation of jac!
- Loading branch information
Showing
21 changed files
with
1,454 additions
and
569 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.