On Mon, Feb 1, 2016 at 9:54 AM, David Knezevic <david.kneze...@akselos.com>
wrote:
> I'd like to couple some extra equations to a system using SCALAR variables
> (the extra equations are not based on the mesh). It would be convenient if
> I could do this by adding a SCALAR variable of arbitrary "order" to the
> system. At the moment order is capped at 43, according to the Order enum,
> but I think in the case of SCALARs it makes sense to allow the order to be
> higher than that...
>
> Do others agree that allowing arbitrary order SCALARs would be desirable?
> Of course, it would be possible to add many "low order" scalars to achieve
> the same thing, but it'd be convenient to be able to group the extra
> equations based on higher-order SCALARs.
>
It's not something I've ever needed, but now that Roy has implemented
sparse scalars, it seems reasonable memory-wise.
Any ideas on the implementation? Will it remain backwards-compatible with
code that is using enum-based SCALARS? Off the top of my head, you might
have a new FEType constructor that takes an unsigned int parameter while
setting the existing enum order==INVALID_ORDER. Or you could have a new
System::add_variable() overload that takes an unsigned int.
--
John
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
