Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
Jupyter Kernel terminated: This might be caused by running out of memory or hitting a bug in some library (e.g., forking too many processes, trying to access invalid memory, etc.). Consider restarting or upgrading your project or running the relevant code directly in a terminal to track down the cause, as explained here.
---------------------------------------------------------------------------
NameError Traceback (most recent call last)
<ipython-input-1-f989cd57b657> in <module>()
----> 1 c = curves[Integer(0)]
2 c
NameError: name 'curves' is not defined
---------------------------------------------------------------------------
ValueError Traceback (most recent call last)
<ipython-input-33-4c0091c2dd0b> in <module>()
----> 1 j = fib.j()
/ext/sage/sage-8.1/src/sage/misc/cachefunc.pyx in sage.misc.cachefunc.CachedMethodCallerNoArgs.__call__ (build/cythonized/sage/misc/cachefunc.c:13511)()
2377 if self.cache is None:
2378 f = self.f
-> 2379 self.cache = f(self._instance)
2380 return self.cache
2381
/home/user/elliptic_fibration.pyc in j(self)
877 y^2 = x^3 + g2*x + g3.
878 """
--> 879 return 4 * self.g2()**3 / self.delta()
880
881 def plot3d(self):
/home/user/elliptic_fibration.pyc in g2(self)
832 return self._g2
833 except AttributeError:
--> 834 self._compute_invariants()
835 return self._g2
836
/home/user/elliptic_fibration.pyc in _compute_invariants(self, d)
771 else:
772 f0 = SingularFiber(self._top, degenerate=True)
--> 773 d = degree_shift(f0)
774 self._f_0 = f0
775
/home/user/elliptic_fibration.pyc in degree_shift(f0)
755 d = (evo[2] - dvo) / 6
756 if not d.is_integral():
--> 757 raise ValueError("degree shift %s is not integer!" % d)
758 if (g2vo + 2 * d < evo[0]
759 or g3vo + 3 * d < evo[1]
ValueError: degree shift -1/3 is not integer!
Points: [2, 3, 6, 7, 8, 13, 14]
Skeleton points: [2, 3, 6, 7, 8, 13]
Normal to the slice hyperplane: (1, -1, 0)
Vertices of the slice polytope:
M(-1, -1),
M(-1, 0),
M( 0, -1),
M( 1, 1),
M( 0, 1),
M( 1, 0)
in 2-d lattice M
Coordinate points:
Monomial points:
Equation of a hypersurface:
Projection to the base:
Coordinate on the base:
Fiber over :
Top: ExtA3, generic :
Bottom: ExtA3, generic :