Closed kmpape closed 5 months ago
Sorry, my bad. I think that it should be
x_mother = self.position[0] - self.division_sign * self.length/2 * np.cos(self.angle - np.pi/2)
y_mother = self.position[1] + self.division_sign * self.length/2 * np.sin(self.angle - np.pi/2)
assuming that self.angle starts at the horizontal axis.
I have now simplified some stuff on my end and will make a pull request some time next week. I added division_sign above so one can specify whether the mother should be on top or bottom. It only matters for something related to IDs, which will be contained in the pull request.
Hi Idris, I think this can be a change which is made for the convenience of mother machine simulations, sure. Great that it's adjustable. The simulation is still stable yes? If we have a robust lineage tracking system then this will also help.
Hi @kmpape
I finally fully realised why you want you want to do this while implementing some stuff to export lineages from the simulation as directed graphs, and maintaining constant mask ID during the simulation. Having the mother stay at the top keeps its mask constant, with each daughter gaining a new mask label. This will be in a commit today.
Thank you very much for this.
Hello Georgeos,
I am about to push something, but before that I have a question:
https://github.com/georgeoshardo/SyMBac/blob/7b8244370f976a79d84f8b31dd53a2c49bba8df2/SyMBac/cell.py#L133 https://github.com/georgeoshardo/SyMBac/blob/7b8244370f976a79d84f8b31dd53a2c49bba8df2/SyMBac/cell.py#L134
Are you sure about the signs above? In my opinion, if the mother is kept at the top, new_x should have something subtracted and new_y something added. The other way around for the daughter.
Thanks!