nam issueshttps://gitlab.gwdg.de/groups/nam/-/issues2023-05-05T07:27:57Zhttps://gitlab.gwdg.de/nam/ProxPython/-/issues/17Orbital experiment bug2023-05-05T07:27:57ZRussell LukeOrbital experiment bugI get this error when running the regression_tests.py script in mode = Mode.UpdateTestData
********************
Exception has occurred: TypeError
'str' object is not callable
File "/home/russell/git/ProxPython/proxtoolbox/proxoperato...I get this error when running the regression_tests.py script in mode = Mode.UpdateTestData
********************
Exception has occurred: TypeError
'str' object is not callable
File "/home/russell/git/ProxPython/proxtoolbox/proxoperators/P_M.py", line 19, in __init__
self.prop = experiment.propagator(experiment)
File "/home/russell/git/ProxPython/proxtoolbox/proxoperators/P_M.py", line 78, in __init__
super(Approx_P_M, self).__init__(experiment)
File "/home/russell/git/ProxPython/proxtoolbox/algorithms/feasibilityIterateMonitor.py", line 26, in __init__
prox = proxClass(experiment)
File "/home/russell/git/ProxPython/proxtoolbox/experiments/experiment.py", line 433, in instanciateAlgorithm
iterateMonitor = iterateMonitorClass(self)
File "/home/russell/git/ProxPython/proxtoolbox/experiments/experiment.py", line 274, in initialize
self.instanciateAlgorithm()
File "/home/russell/git/ProxPython/proxtoolbox/experiments/experiment.py", line 36, in __call__
obj.initialize() # initialize experiment objecthttps://gitlab.gwdg.de/nam/ProxPython/-/issues/16Making norm_data in the expriment class a default value other then None2022-12-12T11:04:07ZConstantin HöingMaking norm_data in the expriment class a default value other then NoneIt does not become clear in the docs what norm_data in experiment.py is. Nor is it mentioned that it needs to be set.
Proposal: make norm_data=1 as default and explain in documentation what it does.It does not become clear in the docs what norm_data in experiment.py is. Nor is it mentioned that it needs to be set.
Proposal: make norm_data=1 as default and explain in documentation what it does.https://gitlab.gwdg.de/nam/ProxPython/-/issues/15master clean2023-05-07T11:02:24ZRussell Lukemaster cleanDemos still not working in master branch:
* Elser
name 'S' is not defined
File "/home/russell/git/ProxPython/proxtoolbox/experiments/phase/Elser_Experiment.py", line 118, in loadData
self.support_idx = np.nonzero(S)
* Deg...Demos still not working in master branch:
* Elser
name 'S' is not defined
File "/home/russell/git/ProxPython/proxtoolbox/experiments/phase/Elser_Experiment.py", line 118, in loadData
self.support_idx = np.nonzero(S)
* DegenerateOrbital, PlanarMolecule, OrthogonalOrbitals:
TypeError: 'str' object is not callable
Untested: nothinghttps://gitlab.gwdg.de/nam/ProxPython/-/issues/11NoLips TO DO2021-01-31T16:28:21ZRussell LukeNoLips TO DOCurrent structure:
nolipsExperiment.py is the top-level experiment class in this folder.
randomExperiment.py is onle level down and will inherit the class defined by nolipsExperiment.py
I imagine eventually having a JWSTExperim...Current structure:
nolipsExperiment.py is the top-level experiment class in this folder.
randomExperiment.py is onle level down and will inherit the class defined by nolipsExperiment.py
I imagine eventually having a JWSTExperiment.py with, say, the JWST data, and maybe a sensor localization one too.
But we will start with randomly generated quadratics. The only problem with this is that we don't know what the solution is.
# TO DO:
* Algorithm initialization and
* putting in the functions f and phi (see Teboulle notes).
Not sure yet how to do this since these could vary. Initialization could be
done at the individual experiment level. f and phi should probably be coded
at the level of nolipsExperiment.py, which is the top-level experiment class for the NoLips folder.
These are in principle independent of the particular quadratic forms, but we would want these
to be parameters with defaults that the user could change.lausterlausterhttps://gitlab.gwdg.de/nam/ProxPython/-/issues/1simplification of evaluateChange in gretchko2020-06-17T16:07:42ZGijsbert Simon Matthijs Jansensimplification of evaluateChange in gretchkoI think the whole if loop can be avoided if you use something like
np.sum(abs(u-u_new)**2).
This should work for arrays (u, u_new) of arbitrary size and dimension - it will simply sum over all.I think the whole if loop can be avoided if you use something like
np.sum(abs(u-u_new)**2).
This should work for arrays (u, u_new) of arbitrary size and dimension - it will simply sum over all.