<div dir="ltr">On Sun, Feb 10, 2013 at 1:05 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_extra"><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="im"><br><div class="gmail_quote">On Sat, Feb 9, 2013 at 8:04 PM, Matthew Knepley <span dir="ltr"><<a href="mailto:knepley@gmail.com" target="_blank">knepley@gmail.com</a>></span> wrote: <blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="gmail_extra"><div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div dir="ltr"><div class="gmail_extra"><div class="gmail_extra"></div><div class="gmail_extra">
What's your plan for implementing this?</div></div></div>
</blockquote></div></div><br>My plan was to try the easiest thing I could think of first:</div><div class="gmail_extra"><br></div><div class="gmail_extra"> a) Make a replacement monitor for SNES and KSP</div><div class="gmail_extra">
<br></div><div class="gmail_extra"> It would have a big honking sentinel before each solve and iterations in Python array format</div><div class="gmail_extra"><br></div><div class="gmail_extra"> b) Run a braindead Python parser over this which snips out the monitors</div>
<div class="gmail_extra"><br></div><div class="gmail_extra"> c) Diff the monitor sections with a numerical tolerance</div><div class="gmail_extra"><br></div><div class="gmail_extra"> d) Diff the whole thing, and throw out differences in the monitor sections, since we know the line numbers.</div>
<div class="gmail_extra"> Maybe it would be easier to just remove those lines, but we need to experiment a little.</div></blockquote></div><br></div>Okay, so this would all be implemented in C?</div></div></blockquote>
<div><br></div><div style>Does the Bear(y) shit in the woods?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra">
If you want Python array format, you may as well use JSON since it's more of an exchange standard and it's the most convenient format for monitoring in a web-based GUI. There are a bunch of good JSON libraries, ranging from the ultra-compact <a href="http://zserge.bitbucket.org/jsmn.html" target="_blank">http://zserge.bitbucket.org/jsmn.html</a> and <a href="http://ccodearchive.net/info/json.html" target="_blank">http://ccodearchive.net/info/json.html</a>, to the object-oriented <a href="http://www.digip.org/jansson/doc/dev/tutorial.html" target="_blank">http://www.digip.org/jansson/doc/dev/tutorial.html</a>.</div>
</div>
</blockquote></div><br>The phrase "may as well" is very slippery. Python arrays are just [x, y, z], whereas JSON needs a library.</div><div class="gmail_extra">However, the format is is now way crucial to the scheme. I want to get the workflow up an running with</div>
<div class="gmail_extra">the simplest format. We will inevitably tweak it was we add tons of crap on top if it works.</div><div class="gmail_extra"><br></div><div class="gmail_extra"> 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
</div></div>