<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Jun 12, 2012, at 2:57 PM, Matthew Knepley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Wed, Jun 13, 2012 at 2:57 AM, Jed Brown <span dir="ltr"><<a href="mailto:jedbrown@mcs.anl.gov" target="_blank">jedbrown@mcs.anl.gov</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im"><div class="gmail_quote">On Tue, Jun 12, 2012 at 1:59 PM, Mark F. Adams <span dir="ltr"><<a href="mailto:mark.adams@columbia.edu" target="_blank">mark.adams@columbia.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
How does one do that? Blaise generated this mat/vec. </blockquote></div><br></div><div>Set a prefix in the info file (done automatically when you write it) and set a prefix on the Vec before you read it.</div>
</blockquote></div><br>I think its even simpler in this case. The option is coming too late. Give it explicitly on the command line.</blockquote><div><br></div>Still not sure what you mean. I added -vecload_block_size 3 to the command line and I got the same error.</div><div><br></div><div>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.</div><div><br></div><div>Mark</div><div><br></div><div><blockquote type="cite"><div><br></div><div> Matt<br clear="all"><div><br></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>
-- Norbert Wiener<br>
</div>
</blockquote></div><br></body></html>