Re: [sage-support] Re: Cartan moving frame formalism

2018-12-10 Thread Tevian Dray
Let me start by confirming that I have successfully used SageManifolds
to implement the several calculations I wanted to make using the Cartan
moving frames formalism.  So first a big "thank you" for developing this
code!

> If you find some missing functionalities and you would like to
> implement them, please visit ...

Thanks for the invitation, but I'm a newbie at both Python and Sage...

I do however have some further questions, some of which likely reflect
my lack of comfort with (and ignorance of) object-oriented programming;
others may be in the category of feature requests for the future.

1. First and foremost, what is the proper way to manipulate the
   components of both tensors and tensor-like objects such as the
   connection, the connection 1-forms, and the curvature 2-forms?

A basic example would be how to set the mass to zero in the
Schwarzschild geometry *after* calculating the curvature.  (I'm still
recovering from my shock at discovering that saying "m=0" is not
sufficient...)  The best I've been able to come up with is to do
something like
object[1,2].expr().subs({m:0})
for each component of each affected object.  Is there a better way?

A similar example would be how to apply simplifications to (all)
components of a given tensor or tensor-like object.

2. Is there a way to display (all) connection 1-forms or curvature
   2-forms, ideally in a format analogous to that produced by
   g.display_comp() or nab.display()?

(An answer involving a print loop is acceptable, although I can't get
the formatting right -- one entry per line, no extraneous symbols.)

3. Is there a way to specify the index labels on the connection 1-forms
   and curvature 2-forms, analagous to index_labels on the connection?

(For that matter, is there a way to specify the labels on the metric?
I get an error when trying to set index_labels in that case.)

4. Can default (non-numerical) index labels be specified, rather than
   repeating them in every display request?

Thank you,
Tevian

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-support] Re: Cartan moving frame formalism

2018-12-07 Thread Eric Gourgoulhon


Le jeudi 6 décembre 2018 17:28:39 UTC+1, Tevian Dray a écrit :
>
> >> The answer to your question is essentially "yes" ... 
>
> Thank you for your detailed response and links.  I had in fact found 
> some of them when searching, but clearly hadn't read them carefully 
> enough.  In particular, I had missed the use of vector_frame in the 
> documentation of Affine Connections, although I note that 2 of your 
> subsequent 3 examples appear to define frames without using this class. 
>
> I expect that these examples will indeed provide the guidance I need, 
> and will work through them more carefully. 
>
> Again, thank you. 
>


You're welcome. 
If you find some missing functionalities and you would like to implement 
them, please visit 
https://sagemanifolds.obspm.fr/contrib.html

Best wishes,

  Eric.

>
> Tevian 
>

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.


Re: [sage-support] Re: Cartan moving frame formalism

2018-12-06 Thread Tevian Dray
>> The answer to your question is essentially "yes" ...

Thank you for your detailed response and links.  I had in fact found
some of them when searching, but clearly hadn't read them carefully
enough.  In particular, I had missed the use of vector_frame in the
documentation of Affine Connections, although I note that 2 of your
subsequent 3 examples appear to define frames without using this class.

I expect that these examples will indeed provide the guidance I need,
and will work through them more carefully.

Again, thank you.

Tevian

-- 
You received this message because you are subscribed to the Google Groups 
"sage-support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to sage-support+unsubscr...@googlegroups.com.
To post to this group, send email to sage-support@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-support.
For more options, visit https://groups.google.com/d/optout.