On Tue, 27 Oct 2015, Miguel Angel Salazar de Troya wrote: > To me the problem of the current approach is that I prefer having > the QoIs separated so I can call them whenever I need them.
I agree. Thats why you'd want to write separate QoIs, then a composite QoI class to combine them. > I'm not sure if there's a way to achieve this modularity with having > just one DifferentiableQoI. There's not. But there is a way to achieve it with N+1 DifferentiableQoIs: the first N each implement their own QoI, and the N+1st contains them and dispatches to them. You then attach the N+1st to your system. That N+1st class isn't something I don't think should exist, it's something I haven't had time to write in sufficient generality to include in libMesh. If you do then I'd love a patch. -- Roy ------------------------------------------------------------------------------ _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
