It could be nice to have a note that says something like :

• Since solve() is computing an optimization, it is sensible to initials parameters. Thus having your shapes positioned roughly were you want them to be can give better results/ make the assembly converge. Especially if all your parts are overlapping at the beginning.

(I am not 100% sure this is true though lol)

• Since solve() is computing an optimization, it is sensible to initials parameters. Thus having your shapes positioned roughly were you want them to be can give better results/ make the assembly converge. Especially if all your parts are overlapping at the beginning.

Thanks @Jojain. Yeah, I won't word it exactly like that (I think no initial locations is fine for the majority of uses), but if I'm explaining how constraints work then I should also explain initial locations as well.

@marcus7070 Still seeing the following black error in CI.

would reformat doc\conf.py
Oh no! \U0001f4a5 \U0001f494 \U0001f4a5
1 file would be reformatted, 67 files would be left unchanged.
Command exited with code 1

@marcus7070 Still seeing the following black error in CI.

would reformat doc\conf.py
Oh no! \U0001f4a5 \U0001f494 \U0001f4a5
1 file would be reformatted, 67 files would be left unchanged.
Command exited with code 1

Thanks, I just had to add a comma to a list. Assuming this all passes I'll merge in a few minutes.

Just a leftover error because this branch doesn't contain #872, so I'll merge.