From: Cline, Danelle Sent: Tuesday, August 30, 2005 6:12 PM To: Cline, Danelle Subject: FW: AVED classifier requirements doc update and project share -----Original Message----- From: Cline, Danelle To: Chase, Andrew Cc: Schlining, Brian Sent: 8/30/05 6:11 PM Subject: RE: AVED classifier requirements doc update and project share Good questions. I'll try to answer as best I can. >> On page 3, I don't see much change from the 2005 diagram to the 2006. >> Does the UI still remain coupled to nanomia as depicted? In 2005 we'd like something to just work on nanomia. A user would login to nanomia and run this tool. In 2006 we will explore running this on machines outside of nanomia. We should talk with Duane about this. The idea here is incremental development. There is no compelling need to run this outside nanomia at the moment, but I wanted to place it out there for consideration. >> page 4, Definitions >> "A class shall be defined as a collection of related images that >> represent a particular animal, collection of animals, or objects." >> does "collection of animals" == "collection of animals of the same >> species"? yes. >>page 4, Class preview >> "The interface shall include an alphabetical tree that displays all >>available training classes" >> is this going to be a tree or a list? it sounds more like a list... Let's talk about this. It depends on how the list/tree is used. >> Are new classes restricted to what's in the VARS KB? Or will the >> looser definition stay in place, that classes may >> come from the VARS KB (which i read as "may not" as well). Yes, classes will typically come from the VARS KB, but we also may test things outside our KB for collaborations. I'll update the reqt doc to reflect this as it's not clear. >>one thing I didn't see addressed is user logins. are we going to have >>them? No login is required as the user will already have logged into nanomia so we have some restriction there already. >>when addressing the issue of saving training/testing results, what >>drives the requirement for saving to a temp file if no file is selected? >>Why not just prompt the user to select a file? I don't remember. I think this was an idea Dorothy had based on how we do it now. Prompting to select a file is fine. >> we may want to think about minimum system requirements for running the >> app. i can do a lot fancy stuff for displaying the class images in a >> nice way, but it's going to be somewhat processor intensive. The KISS principle works here. We just need something simple this year. There will be a lot of details to work out between the DB, UI, matlab library, and RAID interfaces. We'll likely spend a good amount of time on getting the framework in place for everything. Fancy stuff for displaying class images falls last on the list in my opinion. Make sense ? -Danelle -----Original Message----- From: Chase, Andrew To: Cline, Danelle Cc: Schlining, Brian; Chase, Andrew Sent: 8/30/05 5:25 PM Subject: RE: AVED classifier requirements doc update and project share hey Danelle, Thanks for sending this, i'm not sure whether I received it before or not. i've got a couple of comments: On page 3, I don't see much change from the 2005 diagram to the 2006. Does the UI still remain coupled to nanomia as depicted? page 4, Definitions "A class shall be defined as a collection of related images that represent a particular animal, collection of animals, or objects." does "collection of animals" == "collection of animals of the same species"? page 4, Class preview "The interface shall include an alphabetical tree that displays all available training classes" is this going to be a tree or a list? it sounds more like a list... In the "Class Preview" section, it says the class listing tree will contain " classes that may correspond to concepts in the VARS Knowledge Base". however, in "creating a class" we have "The interface shall allow the user to create a class that corresponds to a concept name in the VARS Knowledge Base.". Are new classes restricted to what's in the VARS KB? Or will the looser definition stay in place, that classes may come from the VARS KB (which i read as "may not" as well). one thing I didn't see addressed is user logins. are we going to have them? when addressing the issue of saving training/testing results, what drives the requirement for saving to a temp file if no file is selected? Why not just prompt the user to select a file? we may want to think about minimum system requirements for running the app. i can do a lot fancy stuff for displaying the class images in a nice way, but it's going to be somewhat processor intensive. for my own reference... Creating a class: user: select a name from VARS KB user: provide description and representative image user: provide directory of images backend: create class using provided info, suck up images to be stored on raid. Deleting classes and images: user: can delete an entire class backend: call to database to delete class. user: delete images within a class backend: delete references to image in class model. Collection: user: can kick off collection process backend: lock class, run collection process, inform user of completion. Validation: user: kick off process backend: check for min num images. perform operation. return results Training: UI: give a list of available classes to the user to select from. user: select classes to use, kick of process backend: perform training, inform user of results Framework: Keep track of status of RAID, nanomia, solstice. Store user profile settings (machine specific? user specific (login required)?) Provide a settings editor for chaning user specific settings. Save results of training/testing. Why the temp file requirement? -----Original Message----- From: Cline, Danelle To: Chase, Andrew; Schlining, Brian Sent: 8/30/05 3:59 PM Subject: AVED classifier requirements doc update and project share Brian and Andrew, I can't remember if I sent you an updated doc, so here it is with changes from our meeting. Sorry if this is a repeat. Also, I've created a directory in the AVED project folder \\Tornado\ProjectLibrary\900260.AVED\Project.Design\Classifier. Feel free to put any design doc here you want to share, e.g. like your schema's or Java design doc. Thanks, Danelle <>