From: Derek G. <fri...@gm...> - 2013-04-27 03:17:17
|
Guys, What's involved in enabling the ability to add a System to an ES after init() has been called? I can't see why it wouldn't be ok... each System is fairly independent? We have a use case where this is necessary... we don't know beforehand about some small side calculations that will need to be done using the same Mesh (and we don't want to copy the Mesh and create a new ES for this). Any ideas? Thanks! Derek |
From: Roy S. <roy...@ic...> - 2013-04-27 04:08:47
|
On Fri, 26 Apr 2013, Derek Gaston wrote: > What's involved in enabling the ability to add a System to an ES > after init() has been called? I can't see why it wouldn't be ok... > each System is fairly independent? It's sort of like the "adding a vector after init() has been called" case - we didn't originally support it because we didn't have use cases and it was extra work, but the post-init vector case wasn't too much extra work and I don't think the post-init system case would be either. Probably roughly the same process to fix it, too: when something new is added, test to see if init has been called. If it has, then we do the initialization for that new addition right away instead of waiting. --- Roy |
From: Derek G. <fri...@gm...> - 2013-04-27 04:26:08
|
Sounds doable. We'll look into it. I just wanted to a gauge on whether this was even remotely possible before attempting ;-) Derek On Fri, Apr 26, 2013 at 10:08 PM, Roy Stogner <roy...@ic...>wrote: > > On Fri, 26 Apr 2013, Derek Gaston wrote: > > What's involved in enabling the ability to add a System to an ES >> after init() has been called? I can't see why it wouldn't be ok... >> each System is fairly independent? >> > > It's sort of like the "adding a vector after init() has been called" > case - we didn't originally support it because we didn't have use > cases and it was extra work, but the post-init vector case wasn't too > much extra work and I don't think the post-init system case would be > either. > > Probably roughly the same process to fix it, too: when something new > is added, test to see if init has been called. If it has, then we do > the initialization for that new addition right away instead of > waiting. > --- > Roy |
From: Kirk, B. (JSC-EG311) <ben...@na...> - 2013-04-27 12:37:45
|
Have a look at the DofObject - I think it'll need a provision to dynamically change the number of systems, but not much else should really need to change outside of the EquationSystems and System itself. -Ben On Apr 26, 2013, at 11:26 PM, "Derek Gaston" <fri...@gm...<mailto:fri...@gm...>> wrote: Sounds doable. We'll look into it. I just wanted to a gauge on whether this was even remotely possible before attempting ;-) Derek On Fri, Apr 26, 2013 at 10:08 PM, Roy Stogner <roy...@ic...<mailto:roy...@ic...>> wrote: On Fri, 26 Apr 2013, Derek Gaston wrote: What's involved in enabling the ability to add a System to an ES after init() has been called? I can't see why it wouldn't be ok... each System is fairly independent? It's sort of like the "adding a vector after init() has been called" case - we didn't originally support it because we didn't have use cases and it was extra work, but the post-init vector case wasn't too much extra work and I don't think the post-init system case would be either. Probably roughly the same process to fix it, too: when something new is added, test to see if init has been called. If it has, then we do the initialization for that new addition right away instead of waiting. --- Roy ------------------------------------------------------------------------------ Try New Relic Now & We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, & servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr _______________________________________________ Libmesh-devel mailing list Lib...@li...<mailto:Lib...@li...> https://lists.sourceforge.net/lists/listinfo/libmesh-devel |