2024-05-20 00:57:20 +0200 | received badge | ● Notable Question (source) |
2024-05-20 00:57:20 +0200 | received badge | ● Popular Question (source) |
2023-02-13 15:48:54 +0200 | received badge | ● Notable Question (source) |
2023-02-13 15:48:54 +0200 | received badge | ● Popular Question (source) |
2019-08-30 15:19:00 +0200 | commented answer | Changing chart multiple times in sagemanifolds @eric_g: Thanks for the further update, and I'm glad to learn this will be fixed in the next release. |
2019-08-29 23:39:32 +0200 | commented answer | Changing chart multiple times in sagemanifolds eric_g: Thanks for the answer. I assume it is correct, but it seems a surprising situation. Since $\psi_3\circ\psi_1^{-1} = (\psi_3\circ\psi_2^{-1})\circ(\psi_2\circ\psi_1^{-1})$, I don't see why the inverse maps should need to be defined. In particular, in the example I'm thinking of (converting standard Schwarzschild coordinates to Regge-Wheeler tortoise coordinates, then Eddington-Finkelstein null coordinates, and then Kruskal), it is impossible to invert the first coordinate transform. Does this mean that, while I can directly define a transition map from the first coordinate system to the third, I can't define it by going from the first to the second and then the second to the third? This seems like an unnecessary restriction. rburing: I would also like clearer error message. |
2019-08-29 19:28:21 +0200 | asked a question | Changing chart multiple times in sagemanifolds In sagemanifolds, I would like to change from an initial chart to a second and then, from the second to the third. My attempts fail. Is this my fault or a sagemanifolds problem? (Apologies if I already asked this.) Here is a minimal (not) working example. I run the following file: The output is and then a few screens of error messages, of which the most clear is "no common chart for the multiplication". |
2019-07-29 10:47:32 +0200 | received badge | ● Enlightened (source) |
2019-07-29 10:47:32 +0200 | received badge | ● Good Answer (source) |
2019-06-03 14:06:23 +0200 | asked a question | Trouble with spherical coordinates in sagemanifolds I'm probably doing something obviously wrong, but I'd appreciate help with the following. I load the following file Sage then gives the error message "ValueError: no solution found; use set_inverse() to set the inverse manually". If I replace the final two lines with then Sage gives the following unable to make sense of Maxima expression '[if((-pi/2<parg(_sage_var_xxxx0))and(-pi 2<parg(-_sage_var_xxxx0="" sqrt((4<em="">e^(2I_SAGE_VAR_xxxx1))/(e^(4I*_SA ... [dozens of lines of similar] ... tan(_SAGE_VAR_xxxx1)^2+1)],union())]' in Sage. I am aware that Sagemanifolds has native commands for using spherical coordinates. I'm attempting to work on a more complicated manifold, and this is is a minimal working example to demonstrate my problems. |
2019-06-03 13:44:40 +0200 | commented answer | Bel decomposition I think what you want is This gives a unit timelike one-form. Of course, relativity being relativity, there are infinitely many other choices of unit timelike vector. This becomes a more serious issue when working in Kerr. |
2019-05-22 11:42:30 +0200 | received badge | ● Scholar (source) |
2019-05-22 11:40:04 +0200 | commented answer | set_default_chart seems to fail When I set the defaults based for theOpenSet, I get (1/2) y dx⊗dx. If I use then I do get (1/8) y dy ⊗ dy, as desired. I don't see the logic, but thanks for getting this to work. |
2019-05-22 11:37:02 +0200 | received badge | ● Supporter (source) |
2019-05-22 00:01:32 +0200 | received badge | ● Nice Answer (source) |
2019-05-22 00:00:24 +0200 | received badge | ● Student (source) |
2019-05-21 23:47:04 +0200 | received badge | ● Teacher (source) |
2019-05-21 20:56:03 +0200 | answered a question | Bel decomposition The Bel decomposition does not appear in the sagemanifolds reference document, so I assume it is a default command. Nonetheless, it is fairly easy to implement. Assuming that one already has a metric g and a 1-form e0 (perhaps from the 0th element of the coordinate coframe) I have probably mangled some signs in the choice of order of raising and contracting indices on the volume form. (Some tricks to be aware of: When using up and down, since sagemanifolds stores all contravariant indices first, for a fully contravariant tensor, raising index 1 and then lowering index 1 gives an error since the raised index is automatically moved to index 0. The * operation on tensor only works on a pair of tensors. The latex notation for indices (e.g. ['^{ab}']) can be used to take products and contract tensors, but the latex indexing is lost once the * operation is complete. Thus for a product of three indices, one needs to open a parenthesis, apply the indices to get the correct contraction and product for the first two tensors, close the parenthesis, apply a new set of indices, and then multiply by the third tensor.) |
2019-05-21 13:34:53 +0200 | commented question | tangent space vector mapping Regarding (2), I couldn't reproduce this. In particular, when I create a manifold (and define some coordinates on it) and then run p = theManifold.point(name='p') TpM = theManifold.tangent_space(p) v = TpM.an_element() v.dipslay(), I get the error message ValueError: no basis could be found for computing the components in the None |
2019-05-21 13:16:05 +0200 | asked a question | set_default_chart seems to fail I load the following file The output is In particular, when the secondChart and secondChart.frame() have been set as defaults, the metric g is expanded with respect to the second frame, but the components are still expressed in the first coordinates. Is there a way to set defaults so that g appears as 1/8 y dy ⊗dy? |
2019-03-25 23:51:51 +0200 | commented answer | simplify_trig and sorting, for example in fractions I upgraded to sagemath 8.6 (the latest version with binaries available for my system), and this now works. Thanks for pointing out to use newer versions. |
2019-03-24 12:58:15 +0200 | asked a question | simplify_trig and sorting, for example in fractions The output of is Even worse, the result of is when it should be 1. Is there anyway to get sagemath to simplify trigonometric expressions more intelligently? |