Sören Domrös

I tried to just add 1 pixel: It does not always seem to be the case (as seen below) that this fixes the issue.  But in some models it...

The issue seems to be the edgeLabel spacing (which is 2.0) per default.

@uruuru @le-cds Do we have a policy on naming conventions for new algorithms and how do we usually integrate them?

This is probably the same issue described in #766 and will hopefully be fixed. The issue was that ports are assigned a size of 1 instead of 0.

`fixed` does only take effect after an initial run of elk.force. `interactive` is designed to work with nodes that already have a position as seen [here](https://rtsys.informatik.uni-kiel.de/elklive/elkgraph.html?compressedContent=OYJwhgDgFgBCD28AuAoMAbY8QEslQFsAuGAZyRAFNTSVL0BrAOgjABM2cA7YEgIgDaSeBAC8AVgAMTSQBp0lAGZIJ0uQCNkwgqpmzcwKCqkyAunxRd4bSgGUcAL0pMAxvC7lw3JKX4DzKN6U4C5IOABulCQUAK6UKPAEeABy1pQAsjguCAAyYACe8DFI0SBxdBCkOOjuJACMMgCiALQALChQOMFgIC5Q+QASYFxs6Ny8MLaNAAoAggBKswAqjQD6AMIDAJI5ACLzjcmWaTBckjAA3igwNzDoBUVIMAIQ8FVhtTBSsjCSpte3RQ4AAelDYpXKtzuYHU9BgfDOFgAvscbKc6pcATd7oVis9Xu8cJ9vl8-liYEDQeCYLF4lD7rD0PCuHVkajKKcAEyY+kPPEvN54IlcEhyUn-KGUsEQum3BlwhGciwoFFWNFcADMPLlfKeAsJnzFZMlIOlNLKsuxMIVmrZYOAHMokhIZxgzQAfOi6GwHTBKHUXRiPVzvb7KJyXdzg2dQ46NZG3Z7NSggA). Nodes that are neither...

I somehow got a mail that you closed this and found a way to specify it correctly. Can I close the ticket or does it still not work as intended?

Thank you Timothy. If you can create it in the `ELK Demonstrator` it is fine. I prefer the `elkt` format over the `json` format but both work and you can...

Can you provide the corresponding graph in `elkt` or `elkg` format that reproduces this issue?

I am still unsure, why we need Math.ceil to calculate the port position.

maybe we also want to be able set the port label spacing on a port and override the default set by the node. This should be done by individualSpacings.