Skip to content

Add PyEITMesh, PyEITProtocol, PyEITAnomaly - #47

Merged
liubenyuan merged 21 commits into
eitcom:devfrom
DavidMetzIMT:dev_metz_refact
May 10, 2022
Merged

liubenyuan merged 21 commits into
eitcom:devfrom
DavidMetzIMT:dev_metz_refact

Conversation

@DavidMetzIMT

Copy link
Copy Markdown
Contributor

Hy @liubenyuan,

I added PyEITMesh, PyEITProtocol, PyEITAnomaly.
now Forward, EITforward and EITbase are much better, and have less responsabilities, I could move the data checking in the dataclass directly, also by creating some usefull properties we can use them directly in the code and it is more understandable from where the data are coming from (e.g self.mesh.node or self.mesh.n_elems).
just for fun I added PyEITAnomaly abc class now your anomaly are based on your shape functions! (in the future you can than implememt more complexe anomaly or with other shape!)

I tested all examples run!
I will modify my custom software to use that version of pyEIT (maybe i will found other errors...)

davmetz added 20 commits May 9, 2022 07:58
- add ref_el (chekc and set (for user))
- add prop n_el
- replace internal attribute by calling directly the date from the mesh object (e.g. self.mesh.node, etc)
- now a lot of size of date can be accessed from self.mesh.... (beetr for pylance or u.a)
-remove  used attributes
- use  data of mesh directly!
- Only replace the dict calls
- some small corrections
- remove all usued attributes
- in fem remove checks of data (less responsabiltity for fwd)
- use of the package warning to make non blocking warnings
- fix some errors
- use the PyeitProtocol cls to build a protocol_obj using pyeit.eit.protocol.create wrapper function
- pyeit.eit.protocol.create can accepe multiple el_dist (for stacked excitation)
-add n_el in examples..
- rename eit_scan_lines (utils.py is now oselete, ... not used, ) to build_exc_pattern_std
- correct error in set_perm (d was not diamerter but r...)
@liubenyuan
liubenyuan merged commit e2c39a1 into eitcom:dev May 10, 2022
@DavidMetzIMT
DavidMetzIMT deleted the dev_metz_refact branch May 10, 2022 06:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants