Hi Matt, Yes I just submitted an issue.
Thanks very much. Randy M. > On Mar 30, 2020, at 9:15 AM, Matthew Knepley <knep...@gmail.com> wrote: > > On Mon, Mar 30, 2020 at 11:46 AM Randall Mackie <rlmackie...@gmail.com > <mailto:rlmackie...@gmail.com>> wrote: > When PETSc reads in a list of options (like PetscOptionsGetReal, etc), we > have noticed that if there are duplicate entries, that PETSc takes the last > one entered as the option to use. This can happen if the user didn’t notice > there were two lines with the same options name (but different values set). > > Is there someway to have PETSc check for duplicate entries so that we can > stop program execution and warn the user? > > We could add an option. We make heavy use of this behavior in order to > override options previously specified (which act as defaults). > Could you create an issue for it? > > Thanks, > > Matt > > Thanks, > > Randy M > > > -- > What most experimenters take for granted before they begin their experiments > is infinitely more interesting than any results to which their experiments > lead. > -- Norbert Wiener > > https://www.cse.buffalo.edu/~knepley/ <http://www.cse.buffalo.edu/~knepley/>
