On 12/08/10 02:24, freevryheid wrote:
Robert
What do you think about moving the wiki to github?
I have heard a lot of good things about github recently, but have not tried it much myself except the source code management functions. I have nothing against moving more things to github - what exactly are the benefits?
So for the moment I am indifferent to this, but any effort towards improving the (wiki) pages is more than welcome. :)
r.
Benefits:
It may be easier to address, for example, Issue 109<http://code.google.com/p/sfepy/issues/detail?id=109>. Figures can be copied and linked to the git repo. It supports rst (although not exactly the same as Sphinx) but it should be easier to convert to/from documentation. Looks like it provides better latex math support.
On Wed, Dec 8, 2010 at 6:13 AM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
On 12/08/10 02:24, freevryheid wrote:
Robert
What do you think about moving the wiki to github?
I have heard a lot of good things about github recently, but have not tried it much myself except the source code management functions. I have nothing against moving more things to github - what exactly are the benefits?
So for the moment I am indifferent to this, but any effort towards improving the (wiki) pages is more than welcome. :)
r.
-- 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<sfepy-devel%...@googlegroups.com> . For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
-- Andre
That sounds good!
Maybe a good start would be to update your cool primer for current sfepy (as some things changed slightly in the input file syntax, term evaluation was simplified etc.) and put it to the github.
The updates to the problem description are as follows:
- from
fields = { 'displacement': ((2,1), 'real', 'Omega', {'Omega' : '2_3_P1'}), }
to
fields = { 'displacement': ('real', 'vector', 'Omega', 1), }
- remove 'integrals' and use the order directly in place of integral name in equations/terms:
equations = { 'balance_of_forces' : """dw_lin_elastic_iso.2.Omega(Asphalt.lam, Asphalt.mu, v, u ) = 0""", }
This is not necessary, but let's make the input as simple as possible.
remove 'fe'
in postprocessing/probe functions, replace
strain = eval_term_op(state, 'de_cauchy_strain.i1.Omega(u)', pb)
with
strain = pb.evaluate('de_cauchy_strain.i1.Omega(u)')
etc.
- Computing nodal stress can be done now IMHO in a simpler way, something like:
i. Create a variable to hold the nodal stresses:
sfield = Field('stress', nm.float64, (sym,), omega, 1) svar = FieldVariable('sigma', 'parameter', sfield, sym, primary_var_name='(set-to-None)')
where omega is some region, sym = (dim + 1) * dim / 2 is the symmetric tensor storage size (3 in 3D, 6 in 3D)
ii. Evaluate the stresses using the custom integral (this remains the same)
stress = pb.evaluate('dq_cauchy_stress.ivn.Omega(Asphalt.D, u)')
iii. Set the variable - this computes the nodal values given the quadrature point values:
svar.data_from_qp(stress, integrals['ivn'])
Then calling svar() will return the vector of nodal values.
Note that the above is just a "pseudo-code"... I can help you with it after other parts are updated.
What do you think about this?
r.
On 12/08/10 14:31, Andre Smit wrote:
Benefits:
It may be easier to address, for example, Issue 109<http://code.google.com/p/sfepy/issues/detail?id=109>. Figures can be copied and linked to the git repo. It supports rst (although not exactly the same as Sphinx) but it should be easier to convert to/from documentation. Looks like it provides better latex math support.
On Wed, Dec 8, 2010 at 6:13 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/08/10 02:24, freevryheid wrote:
Robert
What do you think about moving the wiki to github?
I have heard a lot of good things about github recently, but have not tried it much myself except the source code management functions. I have nothing against moving more things to github - what exactly are the benefits?
So for the moment I am indifferent to this, but any effort towards improving the (wiki) pages is more than welcome. :)
r.
Sounds good - I've made a start to show the wiki layout on Github. Probably best if you enable wikis on the sfepy page and give me write access and I'll continue to edit from there or we can just transfer at a later stage:
https://github.com/freevryheid/tmpWiki/wiki/Primer
On Thu, Dec 9, 2010 at 4:57 AM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
That sounds good!
Maybe a good start would be to update your cool primer for current sfepy (as some things changed slightly in the input file syntax, term evaluation was simplified etc.) and put it to the github.
The updates to the problem description are as follows:
- from
fields = { 'displacement': ((2,1), 'real', 'Omega', {'Omega' : '2_3_P1'}), }
to
fields = { 'displacement': ('real', 'vector', 'Omega', 1), }
- remove 'integrals' and use the order directly in place of integral name in equations/terms:
equations = { 'balance_of_forces' : """dw_lin_elastic_iso.2.Omega(Asphalt.lam, Asphalt.mu, v, u ) = 0""", }
This is not necessary, but let's make the input as simple as possible.
remove 'fe'
in postprocessing/probe functions, replace
strain = eval_term_op(state, 'de_cauchy_strain.i1.Omega(u)', pb)
with
strain = pb.evaluate('de_cauchy_strain.i1.Omega(u)')
etc.
- Computing nodal stress can be done now IMHO in a simpler way, something like:
i. Create a variable to hold the nodal stresses:
sfield = Field('stress', nm.float64, (sym,), omega, 1) svar = FieldVariable('sigma', 'parameter', sfield, sym, primary_var_name='(set-to-None)')
where omega is some region, sym = (dim + 1) * dim / 2 is the symmetric tensor storage size (3 in 3D, 6 in 3D)
ii. Evaluate the stresses using the custom integral (this remains the same)
stress = pb.evaluate('dq_cauchy_stress.ivn.Omega(Asphalt.D, u)')
iii. Set the variable - this computes the nodal values given the quadrature point values:
svar.data_from_qp(stress, integrals['ivn'])
Then calling svar() will return the vector of nodal values.
Note that the above is just a "pseudo-code"... I can help you with it after other parts are updated.
What do you think about this?
r.
On 12/08/10 14:31, Andre Smit wrote:
Benefits:
It may be easier to address, for example, Issue 109<http://code.google.com/p/sfepy/issues/detail?id=109>.
Figures can be copied and linked to the git repo. It supports rst (although not exactly the same as Sphinx) but it should be easier to convert to/from documentation. Looks like it provides better latex math support.
On Wed, Dec 8, 2010 at 6:13 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/08/10 02:24, freevryheid wrote:
Robert
What do you think about moving the wiki to github?
I have heard a lot of good things about github recently, but have not
tried it much myself except the source code management functions. I have nothing against moving more things to github - what exactly are the benefits?
So for the moment I am indifferent to this, but any effort towards improving the (wiki) pages is more than welcome. :)
r.
-- 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<sfepy-devel%...@googlegroups.com> . For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
-- Andre
On 12/09/10 15:44, Andre Smit wrote:
Sounds good - I've made a start to show the wiki layout on Github. Probably best if you enable wikis on the sfepy page and give me write access and I'll continue to edit from there or we can just transfer at a later stage:
Nice!
I sort of see how to add people to teams within the sfepy organization, but cannot see how to enable wikis. Write access = I put you among developers with push rights, right?
r.
On Thu, Dec 9, 2010 at 4:57 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
That sounds good!
Maybe a good start would be to update your cool primer for current sfepy (as some things changed slightly in the input file syntax, term evaluation was simplified etc.) and put it to the github.
The updates to the problem description are as follows:
- from
fields = { 'displacement': ((2,1), 'real', 'Omega', {'Omega' : '2_3_P1'}), }
to
fields = { 'displacement': ('real', 'vector', 'Omega', 1), }
- remove 'integrals' and use the order directly in place of integral name in equations/terms:
equations = { 'balance_of_forces' : """dw_lin_elastic_iso.2.Omega(Asphalt.lam, Asphalt.mu, v, u ) = 0""", }
This is not necessary, but let's make the input as simple as possible.
remove 'fe'
in postprocessing/probe functions, replace
strain = eval_term_op(state, 'de_cauchy_strain.i1.Omega(u)', pb)
with
strain = pb.evaluate('de_cauchy_strain.i1.Omega(u)')
etc.
- Computing nodal stress can be done now IMHO in a simpler way, something like:
i. Create a variable to hold the nodal stresses:
sfield = Field('stress', nm.float64, (sym,), omega, 1) svar = FieldVariable('sigma', 'parameter', sfield, sym, primary_var_name='(set-to-None)')
where omega is some region, sym = (dim + 1) * dim / 2 is the symmetric tensor storage size (3 in 3D, 6 in 3D)
ii. Evaluate the stresses using the custom integral (this remains the same)
stress = pb.evaluate('dq_cauchy_stress.ivn.Omega(Asphalt.D, u)')
iii. Set the variable - this computes the nodal values given the quadrature point values:
svar.data_from_qp(stress, integrals['ivn'])
Then calling svar() will return the vector of nodal values.
Note that the above is just a "pseudo-code"... I can help you with it after other parts are updated.
What do you think about this?
r.
On 12/08/10 14:31, Andre Smit wrote:
Benefits:
It may be easier to address, for example, Issue 109<http://code.google.com/p/sfepy/issues/detail?id=109>.
Figures can be copied and linked to the git repo. It supports rst (although not exactly the same as Sphinx) but it should be easier to convert to/from documentation. Looks like it provides better latex math support.
On Wed, Dec 8, 2010 at 6:13 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/08/10 02:24, freevryheid wrote:
Robert
What do you think about moving the wiki to github?
I have heard a lot of good things about github recently, but have not
tried it much myself except the source code management functions. I have nothing against moving more things to github - what exactly are the benefits?
So for the moment I am indifferent to this, but any effort towards improving the (wiki) pages is more than welcome. :)
r.
If I remember you need to enable the Wikis box under the admins tab and then add a wiki to your repo. Yes, I see I have push rights - thanks.
On Thu, Dec 9, 2010 at 9:10 AM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
On 12/09/10 15:44, Andre Smit wrote:
Sounds good - I've made a start to show the wiki layout on Github. Probably best if you enable wikis on the sfepy page and give me write access and I'll continue to edit from there or we can just transfer at a later stage:
Nice!
I sort of see how to add people to teams within the sfepy organization, but cannot see how to enable wikis. Write access = I put you among developers with push rights, right?
r.
On Thu, Dec 9, 2010 at 4:57 AM, Robert Cimrman<cimr...@ntc.zcu.cz>
wrote:
That sounds good!
Maybe a good start would be to update your cool primer for current sfepy (as some things changed slightly in the input file syntax, term evaluation was simplified etc.) and put it to the github.
The updates to the problem description are as follows:
- from
fields = { 'displacement': ((2,1), 'real', 'Omega', {'Omega' : '2_3_P1'}), }
to
fields = { 'displacement': ('real', 'vector', 'Omega', 1), }
- remove 'integrals' and use the order directly in place of integral name in equations/terms:
equations = { 'balance_of_forces' : """dw_lin_elastic_iso.2.Omega(Asphalt.lam, Asphalt.mu, v, u ) = 0""", }
This is not necessary, but let's make the input as simple as possible.
remove 'fe'
in postprocessing/probe functions, replace
strain = eval_term_op(state, 'de_cauchy_strain.i1.Omega(u)', pb)
with
strain = pb.evaluate('de_cauchy_strain.i1.Omega(u)')
etc.
- Computing nodal stress can be done now IMHO in a simpler way, something like:
i. Create a variable to hold the nodal stresses:
sfield = Field('stress', nm.float64, (sym,), omega, 1) svar = FieldVariable('sigma', 'parameter', sfield, sym, primary_var_name='(set-to-None)')
where omega is some region, sym = (dim + 1) * dim / 2 is the symmetric tensor storage size (3 in 3D, 6 in 3D)
ii. Evaluate the stresses using the custom integral (this remains the same)
stress = pb.evaluate('dq_cauchy_stress.ivn.Omega(Asphalt.D, u)')
iii. Set the variable - this computes the nodal values given the quadrature point values:
svar.data_from_qp(stress, integrals['ivn'])
Then calling svar() will return the vector of nodal values.
Note that the above is just a "pseudo-code"... I can help you with it after other parts are updated.
What do you think about this?
r.
On 12/08/10 14:31, Andre Smit wrote:
Benefits:
It may be easier to address, for example, Issue 109<http://code.google.com/p/sfepy/issues/detail?id=109>.
Figures can be copied and linked to the git repo. It supports rst (although not exactly the same as Sphinx) but it should be easier to convert to/from documentation. Looks like it provides better latex math support.
On Wed, Dec 8, 2010 at 6:13 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/08/10 02:24, freevryheid wrote:
Robert
What do you think about moving the wiki to github?
I have heard a lot of good things about github recently, but have not
tried it much myself except the source code management functions. I have nothing against moving more things to github - what exactly are the benefits?
So for the moment I am indifferent to this, but any effort towards improving the (wiki) pages is more than welcome. :)
r.
-- 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<sfepy-devel%...@googlegroups.com> . For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
-- Andre
So they are enabled. (Were already, in fact.)
r.
On 12/09/10 16:14, Andre Smit wrote:
If I remember you need to enable the Wikis box under the admins tab and then add a wiki to your repo. Yes, I see I have push rights - thanks.
On Thu, Dec 9, 2010 at 9:10 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/09/10 15:44, Andre Smit wrote:
Sounds good - I've made a start to show the wiki layout on Github. Probably best if you enable wikis on the sfepy page and give me write access and I'll continue to edit from there or we can just transfer at a later stage:
Nice!
I sort of see how to add people to teams within the sfepy organization, but cannot see how to enable wikis. Write access = I put you among developers with push rights, right?
r.
On Thu, Dec 9, 2010 at 4:57 AM, Robert Cimrman<cimr...@ntc.zcu.cz>
wrote:
That sounds good!
Maybe a good start would be to update your cool primer for current sfepy (as some things changed slightly in the input file syntax, term evaluation was simplified etc.) and put it to the github.
The updates to the problem description are as follows:
- from
fields = { 'displacement': ((2,1), 'real', 'Omega', {'Omega' : '2_3_P1'}), }
to
fields = { 'displacement': ('real', 'vector', 'Omega', 1), }
- remove 'integrals' and use the order directly in place of integral name in equations/terms:
equations = { 'balance_of_forces' : """dw_lin_elastic_iso.2.Omega(Asphalt.lam, Asphalt.mu, v, u ) = 0""", }
This is not necessary, but let's make the input as simple as possible.
remove 'fe'
in postprocessing/probe functions, replace
strain = eval_term_op(state, 'de_cauchy_strain.i1.Omega(u)', pb)
with
strain = pb.evaluate('de_cauchy_strain.i1.Omega(u)')
etc.
- Computing nodal stress can be done now IMHO in a simpler way, something like:
i. Create a variable to hold the nodal stresses:
sfield = Field('stress', nm.float64, (sym,), omega, 1) svar = FieldVariable('sigma', 'parameter', sfield, sym, primary_var_name='(set-to-None)')
where omega is some region, sym = (dim + 1) * dim / 2 is the symmetric tensor storage size (3 in 3D, 6 in 3D)
ii. Evaluate the stresses using the custom integral (this remains the same)
stress = pb.evaluate('dq_cauchy_stress.ivn.Omega(Asphalt.D, u)')
iii. Set the variable - this computes the nodal values given the quadrature point values:
svar.data_from_qp(stress, integrals['ivn'])
Then calling svar() will return the vector of nodal values.
Note that the above is just a "pseudo-code"... I can help you with it after other parts are updated.
What do you think about this?
r.
On 12/08/10 14:31, Andre Smit wrote:
Benefits:
It may be easier to address, for example, Issue 109<http://code.google.com/p/sfepy/issues/detail?id=109>.
Figures can be copied and linked to the git repo. It supports rst (although not exactly the same as Sphinx) but it should be easier to convert to/from documentation. Looks like it provides better latex math support.
On Wed, Dec 8, 2010 at 6:13 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/08/10 02:24, freevryheid wrote:
Robert
> > What do you think about moving the wiki to github? > > > I have heard a lot of good things about github recently, but have not > tried it much myself except the source code management functions. I have nothing against moving more things to github - what exactly are the benefits?
So for the moment I am indifferent to this, but any effort towards improving the (wiki) pages is more than welcome. :)
r.
I see it now, didn't previously.
On Thu, Dec 9, 2010 at 9:28 AM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
So they are enabled. (Were already, in fact.)
r.
On 12/09/10 16:14, Andre Smit wrote:
If I remember you need to enable the Wikis box under the admins tab and then add a wiki to your repo. Yes, I see I have push rights - thanks.
On Thu, Dec 9, 2010 at 9:10 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/09/10 15:44, Andre Smit wrote:
Sounds good - I've made a start to show the wiki layout on Github.
Probably best if you enable wikis on the sfepy page and give me write access and I'll continue to edit from there or we can just transfer at a later stage:
Nice!
I sort of see how to add people to teams within the sfepy organization, but cannot see how to enable wikis. Write access = I put you among developers with push rights, right?
r.
On Thu, Dec 9, 2010 at 4:57 AM, Robert Cimrman<cimr...@ntc.zcu.cz>
wrote:
That sounds good!
Maybe a good start would be to update your cool primer for current sfepy (as some things changed slightly in the input file syntax, term evaluation was simplified etc.) and put it to the github.
The updates to the problem description are as follows:
- from
fields = { 'displacement': ((2,1), 'real', 'Omega', {'Omega' : '2_3_P1'}), }
to
fields = { 'displacement': ('real', 'vector', 'Omega', 1), }
- remove 'integrals' and use the order directly in place of integral name in equations/terms:
equations = { 'balance_of_forces' : """dw_lin_elastic_iso.2.Omega(Asphalt.lam, Asphalt.mu, v, u ) = 0""", }
This is not necessary, but let's make the input as simple as possible.
remove 'fe'
in postprocessing/probe functions, replace
strain = eval_term_op(state, 'de_cauchy_strain.i1.Omega(u)', pb)
with
strain = pb.evaluate('de_cauchy_strain.i1.Omega(u)')
etc.
- Computing nodal stress can be done now IMHO in a simpler way, something like:
i. Create a variable to hold the nodal stresses:
sfield = Field('stress', nm.float64, (sym,), omega, 1) svar = FieldVariable('sigma', 'parameter', sfield, sym, primary_var_name='(set-to-None)')
where omega is some region, sym = (dim + 1) * dim / 2 is the symmetric tensor storage size (3 in 3D, 6 in 3D)
ii. Evaluate the stresses using the custom integral (this remains the same)
stress = pb.evaluate('dq_cauchy_stress.ivn.Omega(Asphalt.D, u)')
iii. Set the variable - this computes the nodal values given the quadrature point values:
svar.data_from_qp(stress, integrals['ivn'])
Then calling svar() will return the vector of nodal values.
Note that the above is just a "pseudo-code"... I can help you with it after other parts are updated.
What do you think about this?
r.
On 12/08/10 14:31, Andre Smit wrote:
Benefits:
It may be easier to address, for example, Issue 109<http://code.google.com/p/sfepy/issues/detail?id=109>.
Figures can be copied and linked to the git repo. It supports rst (although not exactly the same as Sphinx) but it should be easier to convert to/from documentation. Looks like it provides better latex math support.
On Wed, Dec 8, 2010 at 6:13 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/08/10 02:24, freevryheid wrote:
> Robert > > >> What do you think about moving the wiki to github? >> >> >> I have heard a lot of good things about github recently, but have >> not >> >> tried > it much myself except the source code management functions. I have > nothing > against moving more things to github - what exactly are the benefits? > > So for the moment I am indifferent to this, but any effort towards > improving the (wiki) pages is more than welcome. :) > > r. > >
-- 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<sfepy-devel%...@googlegroups.com> . For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
-- Andre
Maybe I messed something up. I was looking for the admin tab at the organization page... and it is at the source repo page.
It should be ok now, thanks for starting this!
r.
On 12/09/10 16:41, Andre Smit wrote:
I see it now, didn't previously.
On Thu, Dec 9, 2010 at 9:28 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
So they are enabled. (Were already, in fact.)
r.
On 12/09/10 16:14, Andre Smit wrote:
If I remember you need to enable the Wikis box under the admins tab and then add a wiki to your repo. Yes, I see I have push rights - thanks.
On Thu, Dec 9, 2010 at 9:10 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/09/10 15:44, Andre Smit wrote:
Sounds good - I've made a start to show the wiki layout on Github.
Probably best if you enable wikis on the sfepy page and give me write access and I'll continue to edit from there or we can just transfer at a later stage:
Nice!
I sort of see how to add people to teams within the sfepy organization, but cannot see how to enable wikis. Write access = I put you among developers with push rights, right?
r.
On Thu, Dec 9, 2010 at 4:57 AM, Robert Cimrman<cimr...@ntc.zcu.cz>
wrote:
That sounds good!
Maybe a good start would be to update your cool primer for current sfepy (as some things changed slightly in the input file syntax, term evaluation was simplified etc.) and put it to the github.
The updates to the problem description are as follows:
- from
fields = { 'displacement': ((2,1), 'real', 'Omega', {'Omega' : '2_3_P1'}), }
to
fields = { 'displacement': ('real', 'vector', 'Omega', 1), }
- remove 'integrals' and use the order directly in place of integral name in equations/terms:
equations = { 'balance_of_forces' : """dw_lin_elastic_iso.2.Omega(Asphalt.lam, Asphalt.mu, v, u ) = 0""", }
This is not necessary, but let's make the input as simple as possible.
remove 'fe'
in postprocessing/probe functions, replace
strain = eval_term_op(state, 'de_cauchy_strain.i1.Omega(u)', pb)
with
strain = pb.evaluate('de_cauchy_strain.i1.Omega(u)')
etc.
- Computing nodal stress can be done now IMHO in a simpler way, something like:
i. Create a variable to hold the nodal stresses:
sfield = Field('stress', nm.float64, (sym,), omega, 1) svar = FieldVariable('sigma', 'parameter', sfield, sym, primary_var_name='(set-to-None)')
where omega is some region, sym = (dim + 1) * dim / 2 is the symmetric tensor storage size (3 in 3D, 6 in 3D)
ii. Evaluate the stresses using the custom integral (this remains the same)
stress = pb.evaluate('dq_cauchy_stress.ivn.Omega(Asphalt.D, u)')
iii. Set the variable - this computes the nodal values given the quadrature point values:
svar.data_from_qp(stress, integrals['ivn'])
Then calling svar() will return the vector of nodal values.
Note that the above is just a "pseudo-code"... I can help you with it after other parts are updated.
What do you think about this?
r.
On 12/08/10 14:31, Andre Smit wrote:
Benefits:
> > It may be easier to address, for example, Issue > 109<http://code.google.com/p/sfepy/issues/detail?id=109>. > > Figures can be copied and linked to the git repo. > It supports rst (although not exactly the same as Sphinx) but it > should > be > easier to convert to/from documentation. > Looks like it provides better latex math support. > > On Wed, Dec 8, 2010 at 6:13 AM, Robert Cimrman<cimr...@ntc.zcu.cz> > wrote: > > On 12/08/10 02:24, freevryheid wrote: > > >> Robert >> >> >>> What do you think about moving the wiki to github? >>> >>> >>> I have heard a lot of good things about github recently, but have >>> not >>> >>> tried >> it much myself except the source code management functions. I have >> nothing >> against moving more things to github - what exactly are the benefits? >> >> So for the moment I am indifferent to this, but any effort towards >> improving the (wiki) pages is more than welcome. :) >>
np, glad to help, gives me something to do :)
On Thu, Dec 9, 2010 at 9:47 AM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
Maybe I messed something up. I was looking for the admin tab at the organization page... and it is at the source repo page.
It should be ok now, thanks for starting this!
r.
On 12/09/10 16:41, Andre Smit wrote:
I see it now, didn't previously.
On Thu, Dec 9, 2010 at 9:28 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
So they are enabled. (Were already, in fact.)
r.
On 12/09/10 16:14, Andre Smit wrote:
If I remember you need to enable the Wikis box under the admins tab and
then add a wiki to your repo. Yes, I see I have push rights - thanks.
On Thu, Dec 9, 2010 at 9:10 AM, Robert Cimrman<cimr...@ntc.zcu.cz> wrote:
On 12/09/10 15:44, Andre Smit wrote:
Sounds good - I've made a start to show the wiki layout on Github.
Probably best if you enable wikis on the sfepy page and give me write access and I'll continue to edit from there or we can just transfer at a later stage:
https://github.com/freevryheid/tmpWiki/wiki/Primer
Nice!
I sort of see how to add people to teams within the sfepy organization, but cannot see how to enable wikis. Write access = I put you among developers with push rights, right?
r.
On Thu, Dec 9, 2010 at 4:57 AM, Robert Cimrman<cimr...@ntc.zcu.cz>
wrote:
That sounds good!
> Maybe a good start would be to update your cool primer for current > sfepy > (as some things changed slightly in the input file syntax, term > evaluation > was simplified etc.) and put it to the github. > > The updates to the problem description are as follows: > > 1. from > > fields = { > 'displacement': ((2,1), 'real', 'Omega', {'Omega' : '2_3_P1'}), > } > > to > > fields = { > 'displacement': ('real', 'vector', 'Omega', 1), > } > > 2. remove 'integrals' and use the order directly in place of integral > name > in equations/terms: > > equations = { > 'balance_of_forces' : > """dw_lin_elastic_iso.2.Omega(Asphalt.lam, Asphalt.mu, v, u ) = > 0""", > } > > This is not necessary, but let's make the input as simple as > possible. > > 3. remove 'fe' > > 4. in postprocessing/probe functions, replace > > strain = eval_term_op(state, 'de_cauchy_strain.i1.Omega(u)', pb) > > with > > strain = pb.evaluate('de_cauchy_strain.i1.Omega(u)') > > etc. > > 5. Computing nodal stress can be done now IMHO in a simpler way, > something > like: > > i. Create a variable to hold the nodal stresses: > > sfield = Field('stress', nm.float64, (sym,), omega, 1) > svar = FieldVariable('sigma', 'parameter', sfield, sym, > primary_var_name='(set-to-None)') > > where omega is some region, sym = (dim + 1) * dim / 2 is the > symmetric > tensor storage size (3 in 3D, 6 in 3D) > > ii. Evaluate the stresses using the custom integral (this remains the > same) > > stress = pb.evaluate('dq_cauchy_stress.ivn.Omega(Asphalt.D, u)') > > iii. Set the variable - this computes the nodal values given the > quadrature > point values: > > svar.data_from_qp(stress, integrals['ivn']) > > Then calling svar() will return the vector of nodal values. > > Note that the above is just a "pseudo-code"... I can help you with it > after > other parts are updated. > > What do you think about this? > > r. > > > On 12/08/10 14:31, Andre Smit wrote: > > Benefits: > > >> It may be easier to address, for example, Issue >> 109<http://code.google.com/p/sfepy/issues/detail?id=109>. >> >> Figures can be copied and linked to the git repo. >> It supports rst (although not exactly the same as Sphinx) but it >> should >> be >> easier to convert to/from documentation. >> Looks like it provides better latex math support. >> >> On Wed, Dec 8, 2010 at 6:13 AM, Robert Cimrman<cimr...@ntc.zcu.cz> >> wrote: >> >> On 12/08/10 02:24, freevryheid wrote: >> >> >> Robert >>> >>> >>> What do you think about moving the wiki to github? >>>> >>>> >>>> I have heard a lot of good things about github recently, but have >>>> not >>>> >>>> tried >>>> >>> it much myself except the source code management functions. I have >>> nothing >>> against moving more things to github - what exactly are the >>> benefits? >>> >>> So for the moment I am indifferent to this, but any effort towards >>> improving the (wiki) pages is more than welcome. :) >>> >>>
-- 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<sfepy-devel%...@googlegroups.com> . For more options, visit this group at http://groups.google.com/group/sfepy-devel?hl=en.
-- Andre
participants (3)
-
Andre Smit -
freevryheid
-
Robert Cimrman