Barry Smith <[email protected]> writes: > Ok now let’s consider the given case for viewing the matrix. In the > code one could do KPSGetPC(), PCFactorGetMatrix(), MatView() so > anally the option could be -ksp_pc_factor_mat_view and when would > the view get triggered? Well it makes sense right after the > factorization. And if we shorten the option name out completely we > get -mat_view (but we already have a mat_view for the originally > matrix so to prevent problems we could have -factor_mat_view or > -pc_factor_mat_view.
What about -mg_levels_2_mat_view or -fieldsplit_pressure_mat_view? If the number of levels or the fieldsplit names are obtained automatically From the matrix, then the object cannot reasonably exist at PCSetFromOptions. Or is there a way? > Final note: since someone may want to have -mat_view draw -mat_view > ascii in the same run we actually need to maintain a collection of > viewers for each trigger point The options database doesn't currently work this way. What interface would be use to get those options passed multiple times?
pgpsfg6eriWr1.pgp
Description: PGP signature
