not fully consistent documentation, samples

[oe2lsp]

Hi,
thanks for the project!

I'm trying one of your samples (basic).
In the README the format of the CSV for the ports uses spaces as delimiter, but in the code (importer.py function: get_ports_from_file) "," is used as delimiter.

If someone is new to all of this, at least one example with all necessary files available would be great to get started.

I tried to generate the geometry and view the generated xml in AppCSXCAD but nothing looks correct. The top layer with the trace is missing, no vias and the position from the ports I read from an gerber-viewer are way off.
So I assume its my mistake, but without a working example getting started is quite a challenge :)

[pkatarzynski]

Hi,

We have added some samples to https://github.com/antmicro/gerber2ems/tree/main/examples for reference.

[bvernoux]

It is not very clear how to use paraview (https://github.com/antmicro/gerber2ems#paraview) with example provided especially as when I have built both example basic & differential (using gerber2ems -a with success) then there is lot of files generated as output in ems/simulation/... without any extension and documentation (https://github.com/antmicro/gerber2ems#paraview) speak about ems/simulation/<port_number>/e_field_<layer_number>_..vtr so we expect .vtr extension ?

Could you improve the "https://github.com/antmicro/gerber2ems#paraview" using examples/basic with all steps ?

[oe2lsp]

Thanks,
all examples and a test project of my own are working fine.

With the given examples one question rises. In job-simulation-part there are some lumped components defined as ports, is there a parsing of these parameters planed for the future?

[kevinjuszczyk]

ems/simulation/<port_number>/e_field_<layer_number>_..vtr so we expect .vtr extension ?

@bvernoux, vtr files are produced using the --export-field option
gerber2ems -a --export-field