Free Motion Capture for Everyone πβ¨
TypeScript
Correct use_saved_calibration parameter (#226)
philipqueen9abe4d19c2a2
diff --git a/OLD_README.md b/OLD_README.mdindex 931fe5ea..83541bc8 100644--- a/OLD_README.md+++ b/OLD_README.md@@ -185,7 +185,8 @@ def RunMe(sessionID=None,resetBlenderExe = False,get_synced_unix_timestamps = True,good_clean_frame_number = 0,- bundle_adjust_3d_points=False+ bundle_adjust_3d_points=False,+ use_saved_calibration = False,):```@@ -302,7 +303,7 @@ def RunMe(sessionID=None,- [Default] = False,- When set to `True`, the system will run a bundle adjust optimization of all recorded 3d points produced in `stage=4` using `aniposelib`'s `optim_points` method. This takes a rather long time, but can signicantly clean up the resulting recordings. However,it may also "over smooth" the data. We're in the process of testing this method out now-- `use_previous_calibration`+- `use_saved_calibration`- [Type] = BOOL- [Default] = False,- Choose whether to use a calibration file from a previous session. When `False`, FreeMoCap will automatically save out calibration data whenever stage 3 is successfully completed. Only one saved calibration file is stored, so running another session will overwrite the currently saved calibration file. When `True` , FreeMoCap will instead load in the saved calibration data, which allows users to create recordings without needing to show the cameras the Charuco board.