Re: [MTT devel] MTT Visualization
Woo hoo! The reporter has been much much more useful since the DB optimizations, though I wonder if in the next batch of changes we could also have #296 (a few more columns are needed)? (Not really related to visibility, but I thought I'd speak my mind while there seems to be another round of database stuff going on :-)) Stats visualization would be interesting on virtually any column. Particularly combinations of these: * runtime_parameters * configure_options (broken down by individual options) * bitness * threadedness * np * platform * hardware How much focus will be on the interface for generating whatever visualization versus creating more static pictures? It would be nice to have a flexible dashboard of some kind that would allow us to generate ad hoc visualizations on any combination of database columns. -Ethan On Thu, Jan/10/2008 10:29:32AM, Josh Hursey wrote: > I met with Joseph Cottam (Grad student in my lab at IU) > yesterday about MTT visualization. He is working on some > new visualization techniques and wants to apply them to > the MTT dataset. > > Since we are ramping up to a v1.3 release we want to > visualization to support this effort. So we want to make > sure that the visualization will meet the development > community's needs. We should probably ask the devel-core > list, but I thought I would start some of the discussion > here to make sure I am asking the right questions of the > group. > > To start I have some basic questions: > - How does Open MPI determine that it is stable enough to release? > - What dimensions of testing are most/least important (i.e., > platforms, compilers, feature sets, scale, ...)? > - What other questions would be useful to answer with regard to > testing (thinking completely outside of the box)? > * Example: Are we testing a specific platform/configuration set > too much/too little? > - Other questions you think we should pose to the group? > > We are currently feeling out the domain of possibilities, > but hope to start doing some sketching some ideas in > another week or so. This work should proceed fairly > quickly since we are targeting a paper about this for the > ACM Symposium on Software Visualization > (http://www.softvis.org/ ) which is due in early April. > How is that for expecting success :) > > Cheers, > Josh > ___ > mtt-devel mailing list > mtt-de...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel
[MTT devel] server side Mellanox patch
Pasha sent a 2nd file with their server-side changes. It looks like
there is only one substantive change in report.inc:
-do_pg_query("set sort_mem = '256MB';");
+do_pg_query("set sort_mem = 256;");
Pasha -- what was this change for? Does a knob for this change need
to be added to config.inc?
--
Jeff Squyres
Cisco Systems
Re: [MTT devel] Oleg's mtt client changes.
Pasha sent me this list of changes that Mellanox made to the client
side of MTT. Some of them have already been accepted back into the
trunk, so I snipped those from this mail. There's two main fixes
left: copytree and new functionality in the Mail reporter.
More comments below.
On Jan 10, 2008, at 10:21 AM, Pavel Shamis wrote:
Jeff, please see the attached file.
Most of the fixes already fixed by mtt.
Please see below my comments (grep )
Index: lib/MTT/MPI/Install/Copytree.pm
===
--- lib/MTT/MPI/Install/Copytree.pm (revision 1123)
+++ lib/MTT/MPI/Install/Copytree.pm (working copy)
@@ -48,7 +48,7 @@ sub Install {
$ret->{exit_status} = 1;
$ret->{result_message} = "MPI INSTALL COPYTREE PLUGIN IS OUT OF
DATE. CONTACT AUTHORS";
Verbose("*** $ret->{result_message}\n");
-return $ret;
+#return $ret;
Hah -- I guess the above message says it all, eh? :-)
Debug(">> copytree copying to $config->{installdir}\n");
@@ -69,9 +69,18 @@ sub Install {
}
# Copy the tree
-MTT::DoCommand::Pushdir($config->{installdir});
+#MTT::DoCommand::Pushdir($config->{installdir});
+#$x = MTT::Files::copy_tree("$config->{abs_srcdir}", 1);
+#MTT::DoCommand::Popdir();
+#return undef
+#if (!$x);
+
+#OLEG#
+# Copy the tree
+my $start_dir = cwd();
+MTT::DoCommand::Chdir($config->{installdir});
$x = MTT::Files::copy_tree("$config->{abs_srcdir}", 1);
-MTT::DoCommand::Popdir();
+MTT::DoCommand::Chdir($start_dir);
return undef
if (!$x);
i guess it is copytree fixes
Looks mostly good; I'll commit (and remove the other "this is broken!"
stuff).
Index: lib/MTT/Mail.pm
===
--- lib/MTT/Mail.pm (revision 1123)
+++ lib/MTT/Mail.pm (working copy)
@@ -54,7 +54,9 @@ sub Init {
#--
sub Send {
-my ($subject, $to, $body) = @_;
+#my ($subject, $to, $body) = @_;
+#OLEG#
+my ($subject, $to, $from, $body) = @_;
Init()
if (! $initialized);
@@ -66,11 +68,12 @@ sub Send {
# Invoke the mail agent to send the mail
-open MAIL, "|$mail_agent -s \"$subject\" \"$to\"" ||
+#open MAIL, "|$mail_agent -s \"$subject\" \"$to\"" ||
+#OLEG#
+open MAIL, "|$mail_agent -r \"$from\" -s \"$subject\" \"$to\"" ||
die "Could not open pipe to output e-mail\n";
print MAIL "Subject: $subject\n";
print MAIL "$body\n";
-close MAIL;
# Restore the old environment
Here he is changing default user from to some other value.
This looks reasonable, but I think we only want to add the -r if $from
is defined.
# If we have a hostlist, return its max procs count
Index: lib/MTT/Reporter/Email.pm
===
--- lib/MTT/Reporter/Email.pm (revision 1123)
+++ lib/MTT/Reporter/Email.pm (working copy)
@@ -81,6 +81,8 @@ sub Submit {
# Evaluate the email subject header
my $subject = Value($ini, $section, "email_subject");
+#OLEG#
+my $from = Value($ini, $section, "email_from");
my $s;
my $body;
@@ -116,7 +118,9 @@ sub Submit {
}
# Now send it
-MTT::Mail::Send($s, $to, $body);
+#MTT::Mail::Send($s, $to, $body);
+#OLEG#
+MTT::Mail::Send($s, $to, $from, $body);
Verbose(">> Reported to e-mail: $to\n");
}
again mail fixes
--
Jeff Squyres
Cisco Systems
Re: [MTT devel] mtt reporter popups broken
Perfect -- I can confirm that it all works again. Thanks! On Jan 10, 2008, at 12:53 PM, Josh Hursey wrote: Fixed. This was a latent bug that my commit highlighted, but I didn't check for (Sorry). If mtt_body_html_suffix was non-null then the popups would not work. I just fixed this in r1133. -- Josh On Jan 10, 2008, at 12:26 PM, Jeff Squyres wrote: I notice that I can no longer get the MTT preferences/advanced popups anymore in Safari. They were working earlier this morning -- did Josh's commit break something, perchance? -- Jeff Squyres Cisco Systems ___ mtt-devel mailing list mtt-de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel ___ mtt-devel mailing list mtt-de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel -- Jeff Squyres Cisco Systems
Re: [MTT devel] mtt reporter popups broken
Fixed. This was a latent bug that my commit highlighted, but I didn't check for (Sorry). If mtt_body_html_suffix was non-null then the popups would not work. I just fixed this in r1133. -- Josh On Jan 10, 2008, at 12:26 PM, Jeff Squyres wrote: I notice that I can no longer get the MTT preferences/advanced popups anymore in Safari. They were working earlier this morning -- did Josh's commit break something, perchance? -- Jeff Squyres Cisco Systems ___ mtt-devel mailing list mtt-de...@open-mpi.org http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel
[MTT devel] mtt reporter popups broken
I notice that I can no longer get the MTT preferences/advanced popups anymore in Safari. They were working earlier this morning -- did Josh's commit break something, perchance? -- Jeff Squyres Cisco Systems
Re: [MTT devel] [OMPI devel] Cisco MTT runs
Awesome -- thanks Josh!
On Jan 10, 2008, at 11:32 AM, Josh Hursey wrote:
So we already have this implemented in the configuration file. Props
to Jeff for the addition in r949. The $mtt_body_html_{prefix|suffix}
variable seems to do the trick.
I added a link to contribution graph to the bottom of the reporter. I
moved where this graph lives from my osl.iu.edu space to the
www.open-mpi.org/mtt/stats
directory. The graph should be updated every night. I created a file
that we can edit (body_suffix.html) so if we want to change this we
don't have to keep changing the config.ini file.
Cheers,
Josh
On Jan 8, 2008, at 10:58 AM, Jeff Squyres wrote:
On Jan 8, 2008, at 10:45 AM, Josh Hursey wrote:
(Switching to MTT devel, forgot that we were mailing to OMPI devel
before :/)
Ah. Yeah that makes sense we can allow folks to add some custom,
static text to the reporter page.
Are we talking just a header and a footer for now?
I think that would be sufficient. I could have sworn that we had an
open MTT ticket on this, but now I can't find it...
-- Josh
On Jan 8, 2008, at 8:15 AM, Jeff Squyres wrote:
On Jan 7, 2008, at 2:03 PM, Josh Hursey wrote:
It should be easy enough to add some prefix/suffix/hook-like HTML
somewhere in the standard MTT config that can customize the
output
HTML (i.e., put some additional information on the page, such
as a
link to this graph)...
I'm not sure I understand what you are trying to say here.
Sorry, *I* knew what I meant... :-)
What I meant was that we could add a hook to the MTT server side
config such that a site can add their own HTML to the reporter
output
without needing to modify the MTT code.
--
Jeff Squyres
Cisco Systems
___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel
--
Jeff Squyres
Cisco Systems
___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel
___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel
--
Jeff Squyres
Cisco Systems
Re: [MTT devel] [OMPI devel] Cisco MTT runs
So we already have this implemented in the configuration file. Props
to Jeff for the addition in r949. The $mtt_body_html_{prefix|suffix}
variable seems to do the trick.
I added a link to contribution graph to the bottom of the reporter. I
moved where this graph lives from my osl.iu.edu space to the www.open-mpi.org/mtt/stats
directory. The graph should be updated every night. I created a file
that we can edit (body_suffix.html) so if we want to change this we
don't have to keep changing the config.ini file.
Cheers,
Josh
On Jan 8, 2008, at 10:58 AM, Jeff Squyres wrote:
On Jan 8, 2008, at 10:45 AM, Josh Hursey wrote:
(Switching to MTT devel, forgot that we were mailing to OMPI devel
before :/)
Ah. Yeah that makes sense we can allow folks to add some custom,
static text to the reporter page.
Are we talking just a header and a footer for now?
I think that would be sufficient. I could have sworn that we had an
open MTT ticket on this, but now I can't find it...
-- Josh
On Jan 8, 2008, at 8:15 AM, Jeff Squyres wrote:
On Jan 7, 2008, at 2:03 PM, Josh Hursey wrote:
It should be easy enough to add some prefix/suffix/hook-like HTML
somewhere in the standard MTT config that can customize the output
HTML (i.e., put some additional information on the page, such as a
link to this graph)...
I'm not sure I understand what you are trying to say here.
Sorry, *I* knew what I meant... :-)
What I meant was that we could add a hook to the MTT server side
config such that a site can add their own HTML to the reporter
output
without needing to modify the MTT code.
--
Jeff Squyres
Cisco Systems
___
devel mailing list
de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/devel
___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel
--
Jeff Squyres
Cisco Systems
___
mtt-devel mailing list
mtt-de...@open-mpi.org
http://www.open-mpi.org/mailman/listinfo.cgi/mtt-devel
[MTT devel] MTT Visualization
I met with Joseph Cottam (Grad student in my lab at IU) yesterday about MTT visualization. He is working on some new visualization techniques and wants to apply them to the MTT dataset. Since we are ramping up to a v1.3 release we want to visualization to support this effort. So we want to make sure that the visualization will meet the development community's needs. We should probably ask the devel-core list, but I thought I would start some of the discussion here to make sure I am asking the right questions of the group. To start I have some basic questions: - How does Open MPI determine that it is stable enough to release? - What dimensions of testing are most/least important (i.e., platforms, compilers, feature sets, scale, ...)? - What other questions would be useful to answer with regard to testing (thinking completely outside of the box)? * Example: Are we testing a specific platform/configuration set too much/too little? - Other questions you think we should pose to the group? We are currently feeling out the domain of possibilities, but hope to start doing some sketching some ideas in another week or so. This work should proceed fairly quickly since we are targeting a paper about this for the ACM Symposium on Software Visualization (http://www.softvis.org/ ) which is due in early April. How is that for expecting success :) Cheers, Josh
