Lukas Hauertmann

I tried to make the MWE example as small as possible and it seems I actually removed the important part which seems to create the OOM error in my use...

Yes, here is the full error message: ```bash julia> plot(rand(10)) connect: Connection refused GKS: can't connect to GKS socket application signal (11): Segmentation fault in expression starting at none:0 gks_drv_socket...

Yes, just tested both.

I don't think we should do this like that. Let's take just the `CartesianPoint` as an example (its the same for everything else including the primitives): ```julia CartesianPoint(1u"m", 2u"m", 3u"m")...

I just tested on the current main branch: ```julia julia> CartesianPoint(1u"m", 2u"m", 3u"m") 3-element CartesianPoint{Quantity{Int64, 𝐋, Unitful.FreeUnits{(m,), 𝐋, nothing}}} with indices SOneTo(3): 1 m 2 m 3 m ``` That...

#43 is related

I get an error in ```julia sim = Simulation(SSD_examples[:ContactIDTest]) simulate!(sim) calculate_capacitance_matrix(sim) ```

Also, ```julia sim = Simulation(SSD_examples[:ContactIDTest]) simulate!(sim) calculate_weighting_potential!(sim, 4) ``` does actually calculate some field and stores it into the dict. This should throw an error.

> > And what happens if two contacts have the same ID in the config file? > How do we want to handle that case? We can throw an error...

> ```julia > calculate_weighting_potential!(sim, 4) > ``` But there is no contact with `id == 4`. That's the issue.