This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
hekate:hekate_process [2009/10/24 18:17] gjn |
hekate:hekate_process [2019/06/27 15:49] (current) |
||
|---|---|---|---|
| Line 164: | Line 164: | ||
| * types' names should be meaningful! | * types' names should be meaningful! | ||
| - | FIXME provide xslt for wiki export (WTF!) | + | BETA version of XSLT translator from HML 2 wiki table is provided in CVS - [[hekate:cases:howto#attribute_specification|HOWTO description]] |
| ===== Prototyping ===== | ===== Prototyping ===== | ||
| Line 198: | Line 197: | ||
| * Files: | * Files: | ||
| * //hekate_case_NAME:hekate_case_NAME-xtt.hml// | * //hekate_case_NAME:hekate_case_NAME-xtt.hml// | ||
| - | * //hekate_case_NAME:hekate_case_NAME-rt.pl// (with callbacks!) | + | * //hekate_case_NAME:hekate_case_NAME-clb.pl// HMR file generated by HQEd that includes callbacks (HQEd does not support callbacks deffinitons, so they have to be defined 'manually'). For GUI callbacks see this {{:hekate:callbackslibrary.zip|NetBeans project}}, take a look at {{:hekate:hekatecases:hekate_case_thermostat:hekate_case_thermostat-clb.pl|ThermostatCalbacks}} to see how to use them. Also you will have to install JPL extension to launch Java code from within HMR. See [[https://ai.ia.agh.edu.pl/wiki/student:msc2009_xtteng:jpl?s[]=jpl&s[]=quest|this]] for Howto. |
| - | * //hekate_case_NAME:hekate_case_NAME-cb.pl// (callbacks FIXME please verify if callbacks can be kept in the same file as the rt) | + | * //hekate_case_NAME:hekate_case_NAME-xtt.png// (screenshot, xtt struct only (no editor window!), B/W View+ File->Export_scene_view->PNG, hqed export sets no compression!, try to compress the fily siply by ''convert hqedscene.png newfile.png'') |
| - | * //hekate_case_NAME:hekate_case_NAME-xtt.png// (color screenshot, xtt struct only (no editor window!)) | + | * //hekate_case_NAME:hekate_case_NAME-hqd.png// (hqed color screenshot, with the xtt struct (with editor window!), try //printscreen// in GNOME) |
| - | * //hekate_case_NAME:hekate_case_NAME-hqd.png// (hqed color screenshot, with the xtt struct only (with editor window!)) | + | |
| * Output: | * Output: | ||
| * The //output// of this stages is the full XTT structure [[:hekate:hekate_process#encoding|encoded]] with the use of the [[HML]]. | * The //output// of this stages is the full XTT structure [[:hekate:hekate_process#encoding|encoded]] with the use of the [[HML]]. | ||
| Line 207: | Line 205: | ||
| * while making screenshots try to minimize their size (in terms of unused screen space), maximize readability | * while making screenshots try to minimize their size (in terms of unused screen space), maximize readability | ||
| * where callbacks are written? | * where callbacks are written? | ||
| + | |||
| + | REMARK: if you design several versions, variants of the XTT structure, store them with the above names with numbers or _comment before the file extension. \\ | ||
| + | 8-) HQEd allow for image compression: Tools->Settings->XTT Options->Scene. The default compresion level is 0%:!: | ||
| ===== Formal Analysis ===== | ===== Formal Analysis ===== | ||
| Line 222: | Line 223: | ||
| * Output: reports? | * Output: reports? | ||
| * Remarks: | * Remarks: | ||
| - | |||
| ===== Physical Design ===== | ===== Physical Design ===== | ||
| The executable design generation. | The executable design generation. | ||
| Line 233: | Line 233: | ||
| * Files: | * Files: | ||
| * FIXME, at least basic input callbacks | * FIXME, at least basic input callbacks | ||
| - | * Output: reports? trajectories | + | * To launch: <code>gox(<state>, [<tables>], <inference process>).</code> e.g. <code>gox(init, ['Table2', 'Table3'], ddi).</code> |
| + | * Output: Trajectories projections. Trajectory is the system inference path. After every inference process invocation new trajectory is generated. The trajectory can be identified by ID, to obtain ID of recently generated trajectory use //traj_id(ID)// predicate. The ID variable will be unified with an ID of the last trajectory. To save trajectory projection to a file use //io_export_trajectory(Filename, TrajID)// predicate. If you want to save most recent trajectory type this in Prolog console: <code> traj_id(ID),io_export_trajectory('file.txt', ID).</code> | ||
| * Remarks: FIXME | * Remarks: FIXME | ||
| * different inference modes? | * different inference modes? | ||
| + | |||
| + | |||
| + | ===== Integration ===== | ||
| + | This stage involves integrating the XTT logic with the environment with: | ||
| + | * callbacks | ||
| + | * knowledge encodings, translations | ||
| + | * UML representation | ||
| + | * Java serialization | ||
| + | * other? | ||
| + | |||
| + | FIXME | ||
| + | |||
| + | ==== Callbacks ==== | ||
| + | A minimal step here is to write callback for HeaRT in Prolog, XPCE, Java, Python. | ||
| Line 253: | Line 268: | ||
| * LLK: Drools | * LLK: Drools | ||
| - | ====== Integration ====== | + | ==== Encoding ==== |
| - | The stages are integrated with: | + | |
| - | * knowledge encodings | + | |
| - | * transformations | + | |
| - | * other? | + | |
| - | + | ||
| - | FIXME | + | |
| - | This needs filling! | + | |
| - | + | ||
| - | ===== Encoding ===== | + | |
| Currently XML encodings to be used: | Currently XML encodings to be used: | ||
| * ATTML | * ATTML | ||
| Line 269: | Line 275: | ||
| The are now integrated into //HML// the [[Hekate Markup Language]]. | The are now integrated into //HML// the [[Hekate Markup Language]]. | ||
| - | ===== Knowledge Markups ===== | + | ==== Knowledge Markups ==== |
| Aspects: | Aspects: | ||
| * ATTML <-> RDF | * ATTML <-> RDF | ||
| Line 278: | Line 284: | ||
| * ontologies <-> ARDML | * ontologies <-> ARDML | ||
| - | ===== Transformations ===== | ||
| FIXME | FIXME | ||
| HatHoR | HatHoR | ||
| + | |||
| + | ===== Summary ===== | ||
| + | In this stage designer experiences and observations should be captured. | ||
| + | |||
| + | Some of the questions to be answered might be: | ||
| + | * was the case easy to model, if not, why | ||
| + | * was the HeKatE methodology helpfull, how, if not, why | ||
| + | * is it possible to suggest some improvements to the methodology | ||
| + | * was the HeKatE designed simplified compared to the original one | ||
| + | * what are the benefits of the HeKatE approach in this case | ||
| ====== Tools ====== | ====== Tools ====== | ||
| Line 288: | Line 303: | ||
| ====== Case Template ====== | ====== Case Template ====== | ||
| See [[:hekates:cases:hekate_case_skel:start|skeleton case]] | See [[:hekates:cases:hekate_case_skel:start|skeleton case]] | ||
| - | |||
