Intrasense and the Myrian® Studio team will be happy to welcome you in Chicago, from Nov. 26 to Dec. 1. Let’s meet in our booth #6544 !
Year: 2017
 |
Dowload Myrian® Studio Go to the Download page and click the link. |
|
 |
Execute the installer There is only one installer but it bundles two different packages: Myrian® Community and Myrian® SDK |
|
 |
Install Myrian® Community This will install all the Myrian Community runtime in both debug and release and all the standard protocols. |
|
 |
Select a destination folder Default destination is the standard Programs folder, but you can choose any other folder. A link to Myrian® executable will be created on the desktop. |
|
 |
Install Myrian® C++ SDK and Clinical App Toolkit This will install the all the documentation and all the C++ samples. |
|
 |
Select a destination folder Default destination is the Public Documents folder, but you can choose any other folder. A link to that folder will be created on the desktop. |
|
 |
Installation Complete You have now installed Myrian® Community, the C++ SDK and the Clinical App Toolkit. |
|
 |
Launch Myrian® You should find the following icons on your desktop: |
|
 |
Import DICOM files Click the Import button at the top of the screen or drop some DICOM files from the Windows Explorer into the local study list. |
|
 |
Select a folder containing DICOM files Browse for DICOM files. Detected series will show in the list. Select the ones you want to import and click the Import button. |
|
 |
Open series Select a study or a series and click the Open Series button to select a protocol. You can also use the Quick Protocols buttons at the bottom. |
|
 |
Select a protocol If you clicked the Open Series button, you should now select a protocol. For example, select the Samples family and click the Hello World button to open the selected DICOM series with this sample protocol. |
|
 |
Try out sample viewports Once your DICOM series is loaded Inside the workspace, click on any viewport orientation menu (top left of the viewport) and select one of the sample viewports. All those viewports are implemented in the C++ samples installed with the SDK. |
The screen organizer takes care of the position, size and visibility of all frames on the screen (frames can be Myrian® build-in windows as well as user-defined windows). This new mecanism offers many possibilities, from minor reorganization of the default layouts to complete relooking of the user interface.
Avec la 2.3 il est désormais possible de paramétrer les protocoles à partir des préférences, en utilisant des formules XML.
Pour ce faire, on doit utiliser des “alias”. Je rappelle le principe: on définit une table de variables appelée “aliasmap” au début d’un Clinical Element, puis, dans les attributs XML, on référence ces variables par leur nom, en préfixant avec le signe $.
<aliasmap uid="sampvolumestatus" viewlimit="4"/> ... <view appindex="0" limit="$viewlimit"/>
Dorénavant, on peut aussi indiquer que l’alias déterminera sa valeur en évaluant une formule XML. Evidemment, comme les alias sont évalués au chargement de l’objet qui contient l’aliasmap, tous les évaluateurs ne sont pas utilisables (parce que certains objets sont chargés au lancement de l’application par exemple et non à l’ouverture du workspace).
Dans l’exemple suivant, on utilise la fonction “app” pour lire une hypothétique préférence standard de Myrian qui s’appellerait “viewlimit”.
<?xml version="1.0" encoding="utf-16"?>
<protocol uid="sampvolumestatus" thumbnail="volumestatus.png" version="1500" >
<aliasmap uid="sampvolumestatus" viewlimit="#eval:app(prefs,viewlimit)"/>
<appset>
<app refuid="appvolumestatus" />
</appset>
<mmconfig>
<monitor>
<pagelayout type="autogrid" />
<view appindex="0" limit="$viewlimit"/>
</monitor>
</mmconfig>
</protocol>
On pourrait aussi aller lire une préférence quelconque dans _intrasense.txt:
<aliasmap uid="sampvolumestatus" viewlimit="#eval:app(prefs,sys:mysection:myentry:4)"/>
On peut dorénavant avoir des variables XML locales à un button group ou à un scénario. Il suffit de préfixer le nom de la variable partout où on l’utilise avec “local:”. Exemple:
<control type="text" title="Run Commands (2 series)" width="100%">
<cmd id="WksVariableCmd" cmd="set" name="local:lossyarrived" content="0"/>
</control>
Myrian s’occupe en interne de remplace “local:” par le pointeur de l’objet parent (button group ou scénario).
L’event “varchanged” contiendra le nom d’origine (“local:xxxx”) et non le nom interne. A priori, seul l’objet parent est intéressé par un tel event, donc ça devrait suffire.
This article describes how to retrieve context information once Myrian has stopped working, using dump files.
Creating a dump file
When Myrian crashes, the following window may appear (or another of its variants).
Do not close the window. Instead, open the Task Manager, right click on Myrian and Create a dump file.
Once the dump is done, you can close Myrian.
Opening a dump file
Open Visual Studio. Myrian and Visual should use the same code version in order to make full use of the dump file.
Open the dump file, menu “File/Open/File”.
A file summary appears. Click on “Debug with Native Only”.
If you used a single version of Myrian, everything will be as if Myrian was launched in Release linked with Visual Studio. It means you will have the call stack, the line causing the crash and you will be able to go through the different running threads through the parallel stack.
Intrasense and all the Myrian Studio team wish you the best for this new year, may 2017 bring you hapiness and good health.
We look forward to increase further interest for Myrian Studio and to work together on successful and challenging medical applications with all of you !
