epol / acts Goto Github PK

I'm in a hurry, I just copypaste the chat lines, if needed I'll refine the exposition later.

22:03:44 - Io: devi esporre quanti elementi ha la eventmemory
22:04:13 - Io: o io metto un loop da 0 a 10 e nelle prime 9 iterazioni raccolgo garbage
22:07:25 - Io: oltre al fatto che (-1)%N fa -1, il che mada tutto a troie
22:07:32 - Io: *manda
22:08:02 - Io: (N!=0,1, perchè te sei un matematico)

Use the new methods from the commit ad5f996 in computer.cpp in the zerofinder.

This is a reminder
Move fitter.update_values() from public to private. See commit 3b5cf32 (and its comments) for more informations.

When using calculate_launch_parameters the zero finder may stop without finding a zero. There are two cases:

• the simulated point of arrival is far from the desired point (>1%)
• the simultaed point of arrival is near the desired point (<1%), but not enough to stop successfully the iterator (>.5%).

Experiments without friction (TODO with friction) shows that the first case is unlikely and that the second is very common.

I think we should throw an exception in the first case, but what to do in the second?

(actually a warning is printed to user in either case, but I don't like printing)