silviana amethyst
silviana amethyst
this is part of a larger conversation about precision. * how much automagic should happen with respect to precision? * should the user be required to make sure that things...
indeed, i have replicated the problem on my machine.
the precision of the system is drifting from the default precision...
so, while the tracker does indeed change the precision of the homotopy (the system that it is tracking, which must have a path variable), the tracker does NOT adjust the...
here's a file that worked for me: ``` import pybertini import copy sys = pybertini.System() x = pybertini.Variable("x") y = pybertini.Variable("y") vg = pybertini.VariableGroup() vg.append(x) vg.append(y) sys.add_variable_group(vg) sys.add_function((x+2)*(y-3)**6) sys.add_function((x**2 -...
this is a battle i fight in bertini_real, too. precision of variable-precision objects is a real PITA to maintain synchronicity for.
jeb, you have any thoughts on how to resolve this? probably the best solution is to make start systems automatically change their precision to match default when making a start...
the core should suffer from this, too. i think that the solution is to make start systems automatically adjust the precision to match default when a start point is requested....
that part is already implemented, it just needs to be exposed. i am struggling with how to deal with the explosion of combinations of tracker and endgame types in exposing...
there is a todo in the endgame tutorial, which must be taken out when this is resolved