wiki:Meetings/Meet-2010-08-20
Last modified 20 months ago

Meeting 2010-08-20

  • protocol: haf
  • attendees: rvh, msp, cmot, haf, mmu, pkl, ybe, mhei, chsch, bdu, jjc, ckru

KIML Layout Options

  • msp reimplemented internal handling of layout options in KIML
  • new Features: define default values for options in extension point

SVN EOL Style

  • Problems encountered with different line ending styles (Windows vs. Unix)
  • svn:eol-style=native as property for SVN
  • question: how are binary files handled in SVN if this property is set?
  • decision: everybody should apply those auto-props in their svn
    • #1113 cmot: add entry to rtsys wiki for all relevant SVN clients
  • decision: implement SVN commit hooks in the server that enforce these properties
    •  rtsys trac 27 tig: implement such commit hook, error message should contain link to wiki

Addressing of Model Elements

  • topic of jjc and mmu
  • proposal:
    • standard EMF fragment URI: states.0/regions.1/states.0
    • KIELER URI format: states.ABRO/regions.R0/states.ABO
      • implemented in core.model ModelingUtil? class
      • currently only a "name" attribute is used to reference objects, an Object must be of type "NamedObject?" from the Annotations metamodel
      • msp: better should register the used structural features by an extension point
      • msp: should be able to compact the label:
        • remove feature keywords: ABRO/R0/ABO
        • fallback if some of those values are not set: ABRO/regions.0/ABO
        • remove irrelevant entries, if still is valid (e.g. region IDs may be omitted): ABRO/ABO
  • Should be handled as first class project: #1114

KViD Demo (jjc)

  • jjc shows what currently is possible with KViD
  • an example KAOM model is shown
  • rvh is astonished about strange port arrangements of KLODD layouter
    • msp: standard layout option is "fixed port position"
      • #1115 in demo "free" is visible. Is this a bug?
    • problem: GMF bug prevents immediate update of port positions (reported to bugzilla long time ago)
    • #1116 msp TODO: everybody should vote for that bug
    • #1117 cmot TODO: find ways to determine port positions of Ptolemy actors (ask for rules at Berkeley)
  • "Visualization" View allows configuration for visulaization
    • object specific settings are done via the visualization view
      • rvh: this seems to be unintuitive, would expect to put settings near the object
        • #1118 msp: using a view is typical for Eclipse, however, the possible options should consider only the current model object selection
  • Data tokens are visualized as "flying" boxes at the connections
    • #1119 animation duration cannot be configured yet properly
      • so far is configured by step time (however, superflous brake between two animations)
        • keep data token in the end until a new token arrives
      • auto layout is required for proper animation
      • #1120 when connections overlap (hyperedges), tokens will also overlap. Should not overlap.
      • Supported data types: all that can be represented as string -> might get big
      • small step size and then pause might leave animation in bad state
      • #1121 small step sizes are problematic for animation
        • if animation cannot cope with small step size, reduce sampling, but keep a consistent animation
        • saw null pointer exception during demo with small step size
  • #1122 rvh: does always zoom-to-fit already work? mmu: not yet, but its in the pipeline
  • Scope Boxes can be attached to actors
    • Supported data types: only int and float
    • #1123 by default, only an "output" named port will be considered
      • rvh: associate scope with connection --- msp: very bad for auto layout
      • rvh: then associate scope with port
    • #1124 Scope is the ptplot of Ptolemy: should demo this in Berkeley: cmot
    • #1125 Data source may be taken from other inputs, such as csv files
      • input is currently chosen by Visualization view which has its own step button
        • put it into execution manager as data component
        • actual step number should be taken from execution manager (otherwise some steps may be skipped)
    • #1126 stepping back is currently not yet supported
    • #1127 cleaning the scope is not yet supported
    • #1128 msp: every configuration should be also available programmatically
    • #1129 scopes do not scale with size of outer boxes.
  • #1130 Problem: export to pictures is not yet possible (placed on printable layer, but is not visible in printout)
    • mri: look at this issue?
  • KAOM Editor issues:
    • #1131 bad position of port labels
    • #1082 flexible height of title separator
  • KIEM: #1132 Warns about errors but current model has no errors
  • KIEM: #1133 Cannot jump to specific step in the future
    • msp: could be relevant for a database data component
    • cmot: difficult to interface between KIEM UI and such database component
    • suggestion: abstract data pool and make it replaceable by a database
    • msp: different types of simulations:
      • standard: stepwise sequential execution
      • optional: random access execution
  • KIEM: #1134 "jump to most current step" -> "most recent"

Misc

  • review KEX: thu, 2010-08-26, 10:00h
  • Name for View Management: KiVi?: Kieler View Management