Re: fatal: Unable to look up git.sympy.org (port 9418) (Name or service not known)
Hi Sven,
thanks for trying sfepy.
The correct git repo url is the github one. We need to regenerate the docs, good catch.
The current documentation is at http://docs.sfepy.org/doc-devel - at the starting page there is a link to overview of all terms. The docs are also linked with the corresponding sources.
Does it help? Feel free to ask!
r.
----- Reply message ----- From: "kassbohm" <kass...@gmail.com> To: "sfepy-devel" <sfepy...@googlegroups.com> Subject: fatal: Unable to look up git.sympy.org (port 9418) (Name or service not known) Date: Sat, Feb 12, 2011 15:31
Hello,
very nice project.
Two things:
- Following: http://docs.sfepy.org/doc/introduction.html#installation and doing: git clone git://git.sympy.org/sfepy.git I get the error-message mentioned above.
If you use git://github.com/sfepy/sfepy.git instead, all works fine. Is this an issue? Can I repair myself? If yes: How?
- I am a newbie to sfepy. I would like to unserstand how hyperelastic.py works under /examples/large_deformation. For example I would like to know, where documentation and/or the coding of the mooney-rivlin and neo-hookean material can be found. And also about where the terms dw_tl_he_neohooke.i1.Omega etc. are coded/documented. Anybody out there, who would give me some hints?
Sven
Hello Robert,
thanks for your reply.
I certainly already had a look at the docs and already tried to find info concerning material laws for large deformation. I did read the "user documentation". Then I tried the "devel documentation" and found, e.g. http://docs.sfepy.org/doc-devel/_modules/sfepy/terms/terms_hyperelastic_tl.h..., "term_function" is defined. So I could have a look at that. The problem seems to be a different one, though.
For me: A 'nice-to-have' would be e.g. a diagram, which shows, how the modules work together or call each other successively. The calling order and calling hierarchy must be clear from that... Such a thingy would make the start much easier for somebody like me. And such a thingy could be defined as a subtopic in your Developer Guide. It could be called 'Example Program Flow' or 'Calling Sequence'.
Anyway, thanks again for your response. I'll dive into it deeper first and eventually will get back to you. Sven
2011/2/14 Robert Cimrman <cimr...@ntc.zcu.cz>:
Hi Sven,
thanks for trying sfepy.
The correct git repo url is the github one. We need to regenerate the docs, good catch.
The current documentation is at http://docs.sfepy.org/doc-devel - at the starting page there is a link to overview of all terms. The docs are also linked with the corresponding sources.
Does it help? Feel free to ask!
r.
----- Reply message ----- From: "kassbohm" <kass...@gmail.com> To: "sfepy-devel" <sfepy...@googlegroups.com> Subject: fatal: Unable to look up git.sympy.org (port 9418) (Name or service not known) Date: Sat, Feb 12, 2011 15:31
Hello,
very nice project.
Two things:
- Following: http://docs.sfepy.org/doc/introduction.html#installation and doing: git clone git://git.sympy.org/sfepy.git I get the error-message mentioned above.
If you use git://github.com/sfepy/sfepy.git instead, all works fine. Is this an issue? Can I repair myself? If yes: How?
- I am a newbie to sfepy. I would like to unserstand how hyperelastic.py works under /examples/large_deformation. For example I would like to know, where documentation and/or the coding of the mooney-rivlin and neo-hookean material can be found. And also about where the terms dw_tl_he_neohooke.i1.Omega etc. are coded/documented. Anybody out there, who would give me some hints?
Sven
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
Hi Sven,
On Mon, 14 Feb 2011, S. Ka�bohm wrote:
Hello Robert,
thanks for your reply.
I certainly already had a look at the docs and already tried to find info concerning material laws for large deformation. I did read the "user documentation". Then I tried the "devel documentation" and found, e.g. http://docs.sfepy.org/doc-devel/_modules/sfepy/terms/terms_hyperelastic_tl.h..., "term_function" is defined. So I could have a look at that. The problem seems to be a different one, though.
For me: A 'nice-to-have' would be e.g. a diagram, which shows, how the modules work together or call each other successively. The calling order and calling hierarchy must be clear from that... Such a thingy would make the start much easier for somebody like me. And such a thingy could be defined as a subtopic in your Developer Guide. It could be called 'Example Program Flow' or 'Calling Sequence'.
I see. Yes, this information would be useful. Maybe we could use pycallgraph [1] for this purpose?
Otherwise, some additional documentation may be built using doxygen by running
$ make htmldocs
- then view doc/html/index.html in the sfepy directory. This gives an overview of all classes, their inheritance etc.
You can also try running/looking at:
$ ./examples/standalone/interactive/linear_elasticity.py -s
where you can roughly see how a problem definition is built and the problem solved. Running this through pycallgraph might be interesting.
Anyway, thanks again for your response. I'll dive into it deeper first and eventually will get back to you. Sven
Great!
r.
Yes, great, thanks, Robert. Much appreciated.
Talk later (all of you, group), Sven
2011/2/14 Robert Cimrman <cimr...@ntc.zcu.cz>:
Hi Sven,
On Mon, 14 Feb 2011, S. Kaßbohm wrote:
Hello Robert,
thanks for your reply.
I certainly already had a look at the docs and already tried to find info concerning material laws for large deformation. I did read the "user documentation". Then I tried the "devel documentation" and found, e.g. http://docs.sfepy.org/doc-devel/_modules/sfepy/terms/terms_hyperelastic_tl.h..., "term_function" is defined. So I could have a look at that. The problem seems to be a different one, though.
For me: A 'nice-to-have' would be e.g. a diagram, which shows, how the modules work together or call each other successively. The calling order and calling hierarchy must be clear from that... Such a thingy would make the start much easier for somebody like me. And such a thingy could be defined as a subtopic in your Developer Guide. It could be called 'Example Program Flow' or 'Calling Sequence'.
I see. Yes, this information would be useful. Maybe we could use pycallgraph [1] for this purpose?
Otherwise, some additional documentation may be built using doxygen by running
$ make htmldocs
- then view doc/html/index.html in the sfepy directory. This gives an overview of all classes, their inheritance etc.
You can also try running/looking at:
$ ./examples/standalone/interactive/linear_elasticity.py -s
where you can roughly see how a problem definition is built and the problem solved. Running this through pycallgraph might be interesting.
Anyway, thanks again for your response. I'll dive into it deeper first and eventually will get back to you. Sven
Great!
r.
[1] http://pycallgraph.slowchop.com/
-- You received this message because you are subscribed to the Google Groups "sfepy-devel" group. To post to this group, send email to sfepy...@googlegroups.com. To unsubscribe from this group, send email to sfepy-devel...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
participants (2)
-
Robert Cimrman -
S. Kaßbohm