Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Not all nodes are in a town. There are 947 nodes but only 938 are in a town. Investigate why. |Priority=4|
  • There is no distinction between Packet 100, Packet 1000. See http://localhost:8080/pinger/sparql?explore=MetricFROM-BR.ORG.SPRACE.N3-TO-GT.USAC.EDU.N1
  • For the same instance of StatisticalMeasurement, add a hasMeasurementData for each statistical metric. Do not instanciate a new StatisticalMeasurement for each statistical metric.
  • There are some odd duplicates in values. Example: http://localhost:8080/pinger/sparql?explore=Time2010 |Priority=3|
  • There are some nodes in %NODE_DETAILS% that do not have longitude or latitude parameters. |Priority=2|
    • www.ucu.edu.ar, sunysb.edu, buitms.seecs.edu.pk, www.nren.nasa.gov, rzserv2.gsi.de, gluino.phys.unm.edu, and ouhep1.nhn.ou.edu
    Find a way to set up prefixes programmatically. |Priority=1|
  • Remove Nodes Programatically according to some "Context".
  • Verify security of Sesame Server. Do I need to set up User/Password? |Priority=2|
  • Read this http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.161.8030&rep=rep1&type=pdf |Priority=2|
  • Make a better plan to populate the repository. |Priority=4|
    • A file keeping the last action taken to insert a triple could be used to resume the execution of the program if an error (bug, timeout, or connection problem) occurs. Make a more segmented task flow to increase the chance of populating everything. |Priority=3|
    • Verify if it makes sense to use only monitoring nodes in the "FROM" parameter. |Priority=5|
      • If it does, using Perl, generate a JSON file for monitoring nodes only and use it in the MeasurementInstantiator.
    • Use the context in every insertion. Read about context indexes. |Priority=3|
  • Study and test visualization tools. |Priority=5|

...