[Insight-developers] ITKModular dash board

[Bill Lorensen]

Ahh... If there were a phantom module, called ITK-ALL, I could click
on that and see what I consider the old format. Is that true? Or maybe
this is already possible?

On Tue, Apr 19, 2011 at 12:39 PM, Bradley Lowekamp
<blowekamp at mail.nih.gov> wrote:
> Bill,
> I have mixed feeling about the new layout.
> The old one was too big, and people didn't look at all of it. With the
> modular size, I think more people will look at the whole summary.
> However, it does involve  more clicks. So when cdash is slow its going to
> hurts extra, I am optimistic that the new server will may the interface
> snappy, so that clicking through is not  as painful as it currently is. So
> that there will be more of an interactive experience.
> I also can't find things. For example I don't know where KWSyle is suppose
> to show up. Hopefully, I'll be able to pick these things up quickly, but
> there is just ALOT going on right now to keep track of it all and learn new
> tools too.
> Brad
> On Apr 19, 2011, at 12:22 PM, Bill Lorensen wrote:
>
> Seems I can only use the old one if people submit to the old one.
>
> Maybe it is too early to switch over to this new format. I'll be
> interested to see how others feel about this format. After a trial
> period, if the consensus is that the modular format is better, then we
> should move all of the builds to modular. If the consensus is that the
> modular needs more work, then we should move all of the builds back.
>
> I'm concerned that the ITK community (outside of Kitware) had no input
> into this new presentation.
>
> Bill
>
> On Tue, Apr 19, 2011 at 12:15 PM, David Cole <david.cole at kitware.com> wrote:
>
> It is one extra click from the "page that is most equivalent to the old way"
>
> to get to test results.
>
> The easiest way to provide a page like the old one is ... to use the old
>
> one.
>
> The next easiest way is to make new pages that present information from "all
>
> related builds" rather than just one build. This will take some time and
>
> effort on the part of folks working on CDash, though, and is not something
>
> that will appear in the short term.
>
> I think once you get used to clicking down into the subprojects page, you'll
>
> see that it's really easy to tell where errors and test failures are without
>
> even clicking through to them anymore. The modular organization, and sorting
>
> problem areas to the top (which will happen by default in "nightly" sections
>
> after we update the CDash server) will really make it quite easy to pinpoint
>
> the problems. The hard part, as always, is getting all of us to fix
>
> everything that's going wrong.
>
> What would be a super nice feature is this: sorting through all the stuff
>
> automatically, and presenting a summary of "types of things that went wrong"
>
> and their frequency. The dashboard summary as an "auto-prioritized to do"
>
> list has been talked about before, but we haven't yet come up with an easy
>
> way to implement it, given the diverse set of platforms and build
>
> environments we support.
>
>
> Dave
>
>
> On Tue, Apr 19, 2011 at 11:59 AM, Bill Lorensen <bill.lorensen at gmail.com>
>
> wrote:
>
> Dave,
>
> To be honest, as someone who has been looking at dashboards every day
>
> since the first dashboard, I do not care for this layout. Is it really
>
> meant for a system like ITK, where the modules are "internal" or is it
>
> meant for a system make up of sub systems, like Slicer?
>
> I'll have a better assessment as I try to use it in the next weeks.
>
> This is just my gut reaction.
>
> Bill
>
>
> On Tue, Apr 19, 2011 at 11:49 AM, Bill Lorensen <bill.lorensen at gmail.com>
>
> wrote:
>
> Seems like a lot more clicking.
>
> I'll have to explore more.
>
> Is there any way to provide a page like the old one?
>
> On Tue, Apr 19, 2011 at 11:46 AM, David Cole <david.cole at kitware.com>
>
> wrote:
>
> Because they represent a summary of many builds, (each subproject has
>
> its
>
> own build and test results) and we do not have very many multiple-build
>
> view
>
> pages in CDash.
>
> The queryTests example I sent is one of the few examples of a page that
>
> does
>
> show results from more than one build.
>
> We will definitely need more of these types of pages in CDash moving
>
> forward, but that would be new functionality that is not there yet...
>
> ======================
>
> On Apr 19, 2011, at 12:22 PM, Bill Lorensen wrote:
>
> ================
>
> Bradley Lowekamp
>
> Lockheed Martin Contractor for
>
> Office of High Performance Computing and Communications
>
> National Library of Medicine
>
> blowekamp at mail.nih.gov
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Kitware offers ITK Training Courses, for more information visit:
> http://kitware.com/products/protraining.html
>
> Please keep messages on-topic and check the ITK FAQ at:
> http://www.itk.org/Wiki/ITK_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.itk.org/mailman/listinfo/insight-developers
>
>