not a real issue, the sub-bunch period is not calculated from clock sensing, but…

not a real issue, the sub-bunch period is not calculated from clock sensing, but from configuration (call to Ffpg.SelectClock("external", 400.789))

not a real issue, the sub-bunch period is not calculated from clock sensing, but…
not a real issue, the sub-bunch period is not calculated from clock sensing, but from configuration (call to Ffpg.SelectClock("external", 400.789))
f71211b1 · Jan Pospisil · b89fca81 · f71211b1 · f71211b1
Commit f71211b1 authored Nov 03, 2016 by Jan Pospisil
Hide whitespace changes
Inline Side-by-side

Showing with 1 addition and 1 deletion

FFPG_CLI.py sw/FFPG_CLI.py +0 -1

Ffpg.py sw/Ffpg.py +1 -0

No files found.
--- a/sw/FFPG_CLI.py
+++ b/sw/FFPG_CLI.py
@@ -2,7 +2,6 @@
 # coding: utf8

 # TODO:
-#  - fixed sub-bunch period, just check (warning) against "real" input frequency
 #  - relax bunch boundary check, fix continuous pulses (25 ns puls in two subsequent bunches) -> constraint to the help

 import sys

--- a/sw/Ffpg.py
+++ b/sw/Ffpg.py
@@ -34,6 +34,7 @@
 ##-----------------------------------------------------------------------------

 import time
+import warnings
 from WbOverlay import *
 from DS18B20 import *
 from CommonFunctions import *