On Wed, Jun 13, 2012 at 3:25 AM, Mark F. Adams <mark.adams at columbia.edu>wrote:
> > On Jun 12, 2012, at 2:57 PM, Matthew Knepley wrote: > > On Wed, Jun 13, 2012 at 2:57 AM, Jed Brown <jedbrown at mcs.anl.gov> wrote: > >> On Tue, Jun 12, 2012 at 1:59 PM, Mark F. Adams <mark.adams at >> columbia.edu>wrote: >> >>> How does one do that? Blaise generated this mat/vec. >> >> >> Set a prefix in the info file (done automatically when you write it) and >> set a prefix on the Vec before you read it. >> > > I think its even simpler in this case. The option is coming too late. Give > it explicitly on the command line. > > > Still not sure what you mean. I added -vecload_block_size 3 to the > command line and I got the same error. > I thought there would be a -vec_block_size option, but alas its missing. Can you check in the debugger when the block size is getting set? I cannot find it in VecSetFromOptions(). Matt > Also, shouldn't this just work? Blaise wrote a binary fine and I'm using > ex10 to read it. We are both using petsc-dev presumably. > > Mark > > > Matt > > -- > 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 > > > -- 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120613/0c31ab22/attachment.html>
