oskopek / transporteditor Goto Github PK

• Set up build, test and release pipeline
  • Add a script to auto-upload to GitHub releases
• Set up weekly diaries in docs
  • Set up report
  • Include a did report of everything T - 1week ... did this week --bp --github
  • Include diary
• Prune branches

• Ensure LFS is working
• Add dennik.pdf to docs
• un-do v nejake rozumne podobe pro editace. Jde o to, ze program se bude hodne pouzivat ve stylu what-if, takze uzivatel by se nemel bat, ze se nebude moci vratit.
• Re-release

• Watch out for conflicts in domain creation
  • Don't allow user to create a conflict (pre-validation)
  • Select STRIPS/numeric as base and remove/add valid stuff
• Problem creation (validate against a domain) .. just a button that draws a new empty graph with a node

Before continuing

After #11

• Saving/loading:
  • Problem (PDDL + coords)
  • Domain (PDDL)
• Autodetect?
• I/O Tests
  • Original data
  • Custom formats
    • Create custom data sets for testing

• thesis profile: call build.sh
• releaseEditor profile: just the editor release + its internal docs
  • integration tests + normal tests + checkstyle
  • Make travis only run on editor with ITs
• release profile: thesis + releaseEditor

• Create a view for that
• Let user choose between strips, numeric, custom (ask user where to input the domain model)
• Run the planner, wait and load output as a plan
  • Verify (call VAL? No, platform dependent)

• Create editor submodule, move the code
• Create CI and CD webhooks and scripts
• Create release & reports scripts ... did this week --bp --github
• Populate weekly milestones

Take into account:

• Simplicity, speed
• Basic PDDL formulation
  • STRIPS
  • Numeric
  • Custom (add/remove things)
    • Conflicts?

Needs:

• Focus on viewing, not planning
• Do NOT overengineer

• Manage state changes
• Display/depict movement
• Highlight current action
• Changes
  • Drag'n'drop order prevalidation
  • If timeline: change start, prevalidation
• Action List filtering (grey out others)

Basically:

• Sequential
  • Minimize: total-cost
• Temporal
  • Minimize: time
  • Adds a few technicalities (ready-loading vehicle temporal locking)
  • Adds duration to preconditions/effects

Bonus packages:

• All distances equal
  • Not needed, can be simulated by changing the graph
    • Do we want it anyway, though?
• Remove capacities
  • Removes upper limits on vehicle capacities
• Add Fuel
  • Adds a few functions, predicates, preconditions, ...
  • Refuelling action
  • new thing to minimize: total-fuel

Probably do at the same time as #5 .

• Port the POM accordingly
• Do not delete code, let that for another time
• Add tests, if possible

• Right panel (planning + action list)
• Center (graph, toolbox)
• Menu

• Drawing graphs? (just load the coords from file if available.. else drawing alg?)
  • Use JUNG visualization + SpringNode
• Drag'n'drop GUI editor
  • Supported by JUNG automatically?
  • Create custom JUNG visualizer?
• Detail edit dialogs
• Toolbox
  • Lock
  • Add/edit/remove edge/vertex/package/vehicle

http://www.javaslang.io/ ?

With preventive disabling of buttons

• Fix any misconceptions

• Check that all functionality can be done with model
  • Subclassing of conditions in domain
  • Reasonable drawing speed
  • Domain conflict validation
  • Problem validation againts domain
• Aim for simplicity! Do not overengineer

• Tooltip popup
• Reflection display + edit?
  • Or just add the methods

• Rewrite UML diagram into java
• Make any necessary adjustments

• Copy over code from StudyGuide
• Adapt UI to match spec image
• Do not implement graph drawing, only research UI elements and possibilities

• Gantt chart
• Partially ordered action graph
• Time-ordered multi-list
  • Concurrent actions side-by-side