Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Rightclick on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
From: David Knezevic <dknezevic@se...>  20120228 02:34:17

I've just checked in the discontinuous Lagrange basis (L2_LAGRANGE) we discussed recently. Changing MONOMIAL to L2_LAGRANGE in miscellaneous_ex5 works fine in both 2D and 3D. A few comments: 1. Just like in fe_monomial.C, I set compute_constraints to be a NOOP. I was surprised to see that this method is not a NOOP in L2_HIERARCHIC? 2. Similarly, I was surprised to see that L2_HIERARCHIC returns C_ZERO rather than DISCONTINUOUS in get_continuity()? 3. In fe_monomial.C, it looks like monomial_n_dofs() and monomial_n_dofs_per_elem() are identical? If so, I'd like to delete the latter (we only have one of these two functions in L2_HIERARCHIC and L2_LAGRANGE) 4. For now I've just used the same "max_order" for L2_LAGRANGE and LAGRANGE, since I wanted to do an initial checkin based directly on LAGRANGE. But L2_LAGRANGE's Order is no longer related to "element order" (e.g. a SECOND on a TRI3 is perfectly fine for L2_LAGRANGE), so those extra valid combinations could be added to L2_LAGRANGE... this would also have implications for the serendipity shapes functions: we currently assume that QUAD8 or HEX20 implies serendipity, but this need not be true with L2_LAGRANGE. 5. I followed the L2_HIERARCHIC approach of adding new files fe_l2_lagrange_shape_*D.C which are copies of fe_lagrange_shape_*D.C with LAGRANGE replaced by L2_LAGRANGE. But it would be possible to just call LAGRANGE's shape functions directly, rather than copying and pasting  though this would need some modifications if point 4 above is implemented. Any thoughts on the best thing to do here? Dave 
From: David Knezevic <dknezevic@se...>  20120228 02:34:17

I've just checked in the discontinuous Lagrange basis (L2_LAGRANGE) we discussed recently. Changing MONOMIAL to L2_LAGRANGE in miscellaneous_ex5 works fine in both 2D and 3D. A few comments: 1. Just like in fe_monomial.C, I set compute_constraints to be a NOOP. I was surprised to see that this method is not a NOOP in L2_HIERARCHIC? 2. Similarly, I was surprised to see that L2_HIERARCHIC returns C_ZERO rather than DISCONTINUOUS in get_continuity()? 3. In fe_monomial.C, it looks like monomial_n_dofs() and monomial_n_dofs_per_elem() are identical? If so, I'd like to delete the latter (we only have one of these two functions in L2_HIERARCHIC and L2_LAGRANGE) 4. For now I've just used the same "max_order" for L2_LAGRANGE and LAGRANGE, since I wanted to do an initial checkin based directly on LAGRANGE. But L2_LAGRANGE's Order is no longer related to "element order" (e.g. a SECOND on a TRI3 is perfectly fine for L2_LAGRANGE), so those extra valid combinations could be added to L2_LAGRANGE... this would also have implications for the serendipity shapes functions: we currently assume that QUAD8 or HEX20 implies serendipity, but this need not be true with L2_LAGRANGE. 5. I followed the L2_HIERARCHIC approach of adding new files fe_l2_lagrange_shape_*D.C which are copies of fe_lagrange_shape_*D.C with LAGRANGE replaced by L2_LAGRANGE. But it would be possible to just call LAGRANGE's shape functions directly, rather than copying and pasting  though this would need some modifications if point 4 above is implemented. Any thoughts on the best thing to do here? Dave 
From: Derek Gaston <friedmud@gm...>  20120228 03:06:37
Attachments:
Message as HTML

Very cool David... since you brought these up a little while back we've been thinking of ways we can use them. I think they're going to turn out to be quite useful for a lot of different things (like well behaved, nonconstant, discontinuous material property projections)... Thanks for contributing this! Derek On Mon, Feb 27, 2012 at 7:34 PM, David Knezevic <dknezevic@...>wrote: > I've just checked in the discontinuous Lagrange basis (L2_LAGRANGE) we > discussed recently. Changing MONOMIAL to L2_LAGRANGE in > miscellaneous_ex5 works fine in both 2D and 3D. > > A few comments: > > 1. Just like in fe_monomial.C, I set compute_constraints to be a NOOP. I > was surprised to see that this method is not a NOOP in L2_HIERARCHIC? > > 2. Similarly, I was surprised to see that L2_HIERARCHIC returns C_ZERO > rather than DISCONTINUOUS in get_continuity()? > > 3. In fe_monomial.C, it looks like monomial_n_dofs() and > monomial_n_dofs_per_elem() are identical? If so, I'd like to delete the > latter (we only have one of these two functions in L2_HIERARCHIC and > L2_LAGRANGE) > > 4. For now I've just used the same "max_order" for L2_LAGRANGE and > LAGRANGE, since I wanted to do an initial checkin based directly on > LAGRANGE. But L2_LAGRANGE's Order is no longer related to "element > order" (e.g. a SECOND on a TRI3 is perfectly fine for L2_LAGRANGE), so > those extra valid combinations could be added to L2_LAGRANGE... this > would also have implications for the serendipity shapes functions: we > currently assume that QUAD8 or HEX20 implies serendipity, but this need > not be true with L2_LAGRANGE. > > 5. I followed the L2_HIERARCHIC approach of adding new files > fe_l2_lagrange_shape_*D.C which are copies of fe_lagrange_shape_*D.C > with LAGRANGE replaced by L2_LAGRANGE. But it would be possible to just > call LAGRANGE's shape functions directly, rather than copying and > pasting  though this would need some modifications if point 4 above > is implemented. Any thoughts on the best thing to do here? > > Dave > > > >  > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL  plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnowd2d > _______________________________________________ > Libmeshdevel mailing list > Libmeshdevel@... > https://lists.sourceforge.net/lists/listinfo/libmeshdevel > 
From: Roy Stogner <roystgnr@ic...>  20120228 03:30:19

On Mon, 27 Feb 2012, David Knezevic wrote: > I've just checked in the discontinuous Lagrange basis (L2_LAGRANGE) we > discussed recently. Changing MONOMIAL to L2_LAGRANGE in > miscellaneous_ex5 works fine in both 2D and 3D. Thanks! > 1. Just like in fe_monomial.C, I set compute_constraints to be a NOOP. I > was surprised to see that this method is not a NOOP in L2_HIERARCHIC? compute_proj_constraints would work correctly (it just does an immediate return for DISCONTINUOUS), it's just slightly less efficient to call it needlessly. This looks like a minor oversight. > 2. Similarly, I was surprised to see that L2_HIERARCHIC returns C_ZERO > rather than DISCONTINUOUS in get_continuity()? This looks just wrong. Could cause lots of subtle breakage. Unless there's something I'm missing  Truman? > 3. In fe_monomial.C, it looks like monomial_n_dofs() and > monomial_n_dofs_per_elem() are identical? If so, I'd like to delete the > latter (we only have one of these two functions in L2_HIERARCHIC and > L2_LAGRANGE) Agreed; go right ahead. > 4. For now I've just used the same "max_order" for L2_LAGRANGE and > LAGRANGE, since I wanted to do an initial checkin based directly on > LAGRANGE. But L2_LAGRANGE's Order is no longer related to "element > order" (e.g. a SECOND on a TRI3 is perfectly fine for L2_LAGRANGE), so > those extra valid combinations could be added to L2_LAGRANGE... this > would also have implications for the serendipity shapes functions: we > currently assume that QUAD8 or HEX20 implies serendipity, but this need > not be true with L2_LAGRANGE. Right  max_order==unlimited would be fine once the default n > handcoded case is handled in the shape function calculations. > 5. I followed the L2_HIERARCHIC approach of adding new files > fe_l2_lagrange_shape_*D.C which are copies of fe_lagrange_shape_*D.C > with LAGRANGE replaced by L2_LAGRANGE. But it would be possible to just > call LAGRANGE's shape functions directly, rather than copying and > pasting  though this would need some modifications if point 4 above > is implemented. Any thoughts on the best thing to do here? I'm fine with the copy/paste if others are  especially given that the codes may diverge soon to add those higherorder features.  Roy 
From: David Knezevic <dknezevic@se...>  20120228 16:49:14

OK, that all sounds good. Based on Truman's reply, in L2_HIERARCHIC I'll remove compute_proj_constraints and change to DISCONTINOUS. Also, I'll make the change to MONOMIAL that I mentioned. I'll leave the copy/pasted version of L2_LAGRANGE. Dave On 02/27/2012 10:30 PM, Roy Stogner wrote: > > On Mon, 27 Feb 2012, David Knezevic wrote: > >> I've just checked in the discontinuous Lagrange basis (L2_LAGRANGE) we >> discussed recently. Changing MONOMIAL to L2_LAGRANGE in >> miscellaneous_ex5 works fine in both 2D and 3D. > > Thanks! > >> 1. Just like in fe_monomial.C, I set compute_constraints to be a NOOP. I >> was surprised to see that this method is not a NOOP in L2_HIERARCHIC? > > compute_proj_constraints would work correctly (it just does an > immediate return for DISCONTINUOUS), it's just slightly less efficient > to call it needlessly. This looks like a minor oversight. > >> 2. Similarly, I was surprised to see that L2_HIERARCHIC returns C_ZERO >> rather than DISCONTINUOUS in get_continuity()? > > This looks just wrong. Could cause lots of subtle breakage. Unless > there's something I'm missing  Truman? > >> 3. In fe_monomial.C, it looks like monomial_n_dofs() and >> monomial_n_dofs_per_elem() are identical? If so, I'd like to delete the >> latter (we only have one of these two functions in L2_HIERARCHIC and >> L2_LAGRANGE) > > Agreed; go right ahead. > >> 4. For now I've just used the same "max_order" for L2_LAGRANGE and >> LAGRANGE, since I wanted to do an initial checkin based directly on >> LAGRANGE. But L2_LAGRANGE's Order is no longer related to "element >> order" (e.g. a SECOND on a TRI3 is perfectly fine for L2_LAGRANGE), so >> those extra valid combinations could be added to L2_LAGRANGE... this >> would also have implications for the serendipity shapes functions: we >> currently assume that QUAD8 or HEX20 implies serendipity, but this need >> not be true with L2_LAGRANGE. > > Right  max_order==unlimited would be fine once the default n > > handcoded case is handled in the shape function calculations. > >> 5. I followed the L2_HIERARCHIC approach of adding new files >> fe_l2_lagrange_shape_*D.C which are copies of fe_lagrange_shape_*D.C >> with LAGRANGE replaced by L2_LAGRANGE. But it would be possible to just >> call LAGRANGE's shape functions directly, rather than copying and >> pasting  though this would need some modifications if point 4 above >> is implemented. Any thoughts on the best thing to do here? > > I'm fine with the copy/paste if others are  especially given that the > codes may diverge soon to add those higherorder features. >  > Roy 
From: David Knezevic <dknezevic@se...>  20120228 12:55:49
Attachments:
Message as HTML

Sounds good Derek. John also mentioned to me that you guys are interested in L2_LAGRANGE that interpolates at gauss points. I think we could just add that to the current L2_LAGRANGE (rather than making a new type L2_GAUSS_LAGRANGE), and have a switch between NODAL and GAUSS shape functions? Dave On 02/27/2012 10:06 PM, Derek Gaston wrote: > Very cool David... since you brought these up a little while back > we've been thinking of ways we can use them. I think they're going to > turn out to be quite useful for a lot of different things (like well > behaved, nonconstant, discontinuous material property projections)... > > Thanks for contributing this! > > Derek > > On Mon, Feb 27, 2012 at 7:34 PM, David Knezevic > <dknezevic@... <mailto:dknezevic@...>> wrote: > > I've just checked in the discontinuous Lagrange basis (L2_LAGRANGE) we > discussed recently. Changing MONOMIAL to L2_LAGRANGE in > miscellaneous_ex5 works fine in both 2D and 3D. > > A few comments: > > 1. Just like in fe_monomial.C, I set compute_constraints to be a > NOOP. I > was surprised to see that this method is not a NOOP in L2_HIERARCHIC? > > 2. Similarly, I was surprised to see that L2_HIERARCHIC returns C_ZERO > rather than DISCONTINUOUS in get_continuity()? > > 3. In fe_monomial.C, it looks like monomial_n_dofs() and > monomial_n_dofs_per_elem() are identical? If so, I'd like to > delete the > latter (we only have one of these two functions in L2_HIERARCHIC and > L2_LAGRANGE) > > 4. For now I've just used the same "max_order" for L2_LAGRANGE and > LAGRANGE, since I wanted to do an initial checkin based directly on > LAGRANGE. But L2_LAGRANGE's Order is no longer related to "element > order" (e.g. a SECOND on a TRI3 is perfectly fine for L2_LAGRANGE), so > those extra valid combinations could be added to L2_LAGRANGE... this > would also have implications for the serendipity shapes functions: we > currently assume that QUAD8 or HEX20 implies serendipity, but this > need > not be true with L2_LAGRANGE. > > 5. I followed the L2_HIERARCHIC approach of adding new files > fe_l2_lagrange_shape_*D.C which are copies of fe_lagrange_shape_*D.C > with LAGRANGE replaced by L2_LAGRANGE. But it would be possible to > just > call LAGRANGE's shape functions directly, rather than copying and > pasting  though this would need some modifications if point 4 above > is implemented. Any thoughts on the best thing to do here? > > Dave > > >  > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft > developers > is just $99.99! Visual Studio, SharePoint, SQL  plus HTML5, CSS3, > MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnowd2d > _______________________________________________ > Libmeshdevel mailing list > Libmeshdevel@... > <mailto:Libmeshdevel@...> > https://lists.sourceforge.net/lists/listinfo/libmeshdevel > > 
From: David Knezevic <dknezevic@se...>  20120228 12:58:43
Attachments:
Message as HTML

P.S. I like the idea of a GAUSSinterpolary basis since it'll give a diagonal mass matrix. On 02/28/2012 07:55 AM, David Knezevic wrote: > Sounds good Derek. John also mentioned to me that you guys are > interested in L2_LAGRANGE that interpolates at gauss points. I think > we could just add that to the current L2_LAGRANGE (rather than making > a new type L2_GAUSS_LAGRANGE), and have a switch between NODAL and > GAUSS shape functions? > > Dave > > > > On 02/27/2012 10:06 PM, Derek Gaston wrote: >> Very cool David... since you brought these up a little while back >> we've been thinking of ways we can use them. I think they're going >> to turn out to be quite useful for a lot of different things (like >> well behaved, nonconstant, discontinuous material property >> projections)... >> >> Thanks for contributing this! >> >> Derek >> >> On Mon, Feb 27, 2012 at 7:34 PM, David Knezevic >> <dknezevic@... <mailto:dknezevic@...>> wrote: >> >> I've just checked in the discontinuous Lagrange basis >> (L2_LAGRANGE) we >> discussed recently. Changing MONOMIAL to L2_LAGRANGE in >> miscellaneous_ex5 works fine in both 2D and 3D. >> >> A few comments: >> >> 1. Just like in fe_monomial.C, I set compute_constraints to be a >> NOOP. I >> was surprised to see that this method is not a NOOP in L2_HIERARCHIC? >> >> 2. Similarly, I was surprised to see that L2_HIERARCHIC returns >> C_ZERO >> rather than DISCONTINUOUS in get_continuity()? >> >> 3. In fe_monomial.C, it looks like monomial_n_dofs() and >> monomial_n_dofs_per_elem() are identical? If so, I'd like to >> delete the >> latter (we only have one of these two functions in L2_HIERARCHIC and >> L2_LAGRANGE) >> >> 4. For now I've just used the same "max_order" for L2_LAGRANGE and >> LAGRANGE, since I wanted to do an initial checkin based directly on >> LAGRANGE. But L2_LAGRANGE's Order is no longer related to "element >> order" (e.g. a SECOND on a TRI3 is perfectly fine for >> L2_LAGRANGE), so >> those extra valid combinations could be added to L2_LAGRANGE... this >> would also have implications for the serendipity shapes functions: we >> currently assume that QUAD8 or HEX20 implies serendipity, but >> this need >> not be true with L2_LAGRANGE. >> >> 5. I followed the L2_HIERARCHIC approach of adding new files >> fe_l2_lagrange_shape_*D.C which are copies of fe_lagrange_shape_*D.C >> with LAGRANGE replaced by L2_LAGRANGE. But it would be possible >> to just >> call LAGRANGE's shape functions directly, rather than copying and >> pasting  though this would need some modifications if point 4 >> above >> is implemented. Any thoughts on the best thing to do here? >> >> Dave >> >> >>  >> Keep Your Developer Skills Current with LearnDevNow! >> The most comprehensive online learning library for Microsoft >> developers >> is just $99.99! Visual Studio, SharePoint, SQL  plus HTML5, >> CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnowd2d >> _______________________________________________ >> Libmeshdevel mailing list >> Libmeshdevel@... >> <mailto:Libmeshdevel@...> >> https://lists.sourceforge.net/lists/listinfo/libmeshdevel >> >> 
Sign up for the SourceForge newsletter:
No, thanks