OSU UIL development plan

Development tasks, in order, and who is doing

for research in December

  1. ______(Judah) few line of code to pop up UI as per new procedure arriving
  2. ______(Judah) live mode testing of classifier persistence facility (add code in trainer class)
  3. ______(Judah) Attachment predictor class needs to read in classifier
  4. \SKIP(Jed, Oliver) no body event - Jed try html vs plain text email adjustment
  5. \SKIP(Chris/Oliver) successfully read Sensitivity from Pojo (awaiting help from Oliver, Chris)
  6. ___(Jed) harvesting issue "to" field not harvested correctly -> check IrisTracer log to see if To is populated in final email harvest
  7. ___API (JI) SATService.parseSparkleString(String s) using SAT (labelling working, feature detection not)
  8. ___API (JI) SATService.inferForgetting(IEmailMessagePojo p, boolean userIntendedTheAction) using SAT
  9. ___demonstrate fully integrated system (minus SAT)
  10. ______(Judah) (not necessary for demo or paper?) logic for switching from training mode to predicting mode
  11. \SKIP______(Judah) awareness of when emailFinal is sent to adjust training samples?
  12. \SKIP______(Judah) if hack still in place, correct the KB with final email, and persist training example
  13. \SKIP___(team) decide whether we will give learning feedback to the user
  14. ___(Chris) incremental reharvesting not working with outlook
  15. ______(Jed) schedule debugging session with Chris for later in week re -incremental harvesting problem
  16. ___IMPLEMENTATION (KJ) extend EmailContextInfo to include other entities and their
  17. \SKIP___(Oliver) no emailFinal event flowing (still looking into it as of 1118 mtg)
  18. ___(Oliver) batch harvesting in outlook
  19. debugging___API (JI) SATService.getLabelForEmail(IEmailMessagePojo p) using SAT

rough edges (12/09/08)

  1. ___(JI) consume live "new procedure event" from ITL. Got the updated api from ITL folks to work (99% sure) but never finished hooking it into AttachmentPredictor.init due to lack of time before viseo production needed to commence.
  2. ___(Jed) grant_all.policy adsded to build.xml so its copied to uil_plugin from uil_plugin_src - only done on venetie - not committed. So , never committed the ITL and OSU full integration to the point we got it to.
  3. ______(Jed) Tom guided me to not do dangerous last minute jar update commit of ITL dependency jars into uil_plugin\lib dir or in other places in iris
  4. ___(Jed) special hack jars for itl ui and ITLClient API (Jed note 12/09/08 - don't remember if this was still an issue - might have been tweaking jars during troubleshooting or this might just be referring to getting the references right for ITL.
  5. ______(Jed remove Jython files from uil_plugin - decided not to do this as need it for tests to translate sparkle into SharedSpark)
  1. DONE IMPLEMENTATION (KJ) implement UIL manager and learner component
  2. DONE___FEATURE (JI) generate SAT problem for forgetting inference
  3. DONE___(JI) fake forget detection for demo until SAT works
  4. DONE___(JI) fake email labeling for demo until SAT works# DONE FEATURE (JI) parse sparkl string into UILActionSequence
  5. DONE EVAL (KJ, JI) get Tom's partially labeled data into Thunderbird
  6. DONE EVAL (KJ) harvest that data in calo
  7. DONE API (JI) SATService.parseSparkleString(String s) faked
  8. DONE API (JI) SATService.getLabelForEmail(IEmailMessagePojo p) faked
  9. DONE API (JI) SATService.inferForgetting(IEmailMessagePojo p, boolean userIntendedTheAction) faked
  10. DONE/UT UTIL(JI) POJO value lookup for Strings
  11. DONE/UT UTIL(JI) POJO value lookup for Attachments
  12. DONE(JI/KJ) Generate email Data
  13. Done(JI) fake feature legailty for demo until SAT works
  14. DONE FEATURE (JI) adjust sparkl parsing to consume final format of sparkl procedure
  15. DONE___FEATURE (JI) SATService session persistence
  16. DONE___TASK (JI) Prep demo machine for calo
  17. DONE___TASK (KJ) pull iris, desktop onto demo machine
  18. DONE___FEATURE (JI) generate SAT problem for labelling
  19. DONE___FEATURE (JI) generate SAT problem for feature legality
  20. DONE___EVAL (KJ) perform experiments on Tom's data for attachment prediction and generate cross-validation results
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.