---
# System prepended metadata

title: Demo and Meeting with Costas 01/07/21

---

# Demo and Meeting with Costas 01/07/21

## Costas new IME
- What the model user interface looks like 
- it's looking dated already
- several components that could be re-usable
- What should
- Penny has a draft presentation for the Engineering studio

## Asa agenda
- Based off the update last week
- working hard to make the demo 
- 70% done
- Need to clean up
- Modal is ready 
- extension that penny worked on.
- sidebar still need to be done
- new property editor done
- 26,000 entries makes questions arise about optimisation.
- install a newer version of gnlmpc with a xml file that has some edited data.
- Costas: do not mention anything about the number of entries or the data. 
- Asa: loading all this data.
- For every modal that has been used I gave you a PMI 
- Every GPROMS modal 
- Costas still wants to see the in progress

## Demo
- Costas wants to know how to start the application.
- start the application needs to be explained.
- Setting up the default save directory, Costas questions its use. 
- We need to be clear what each stage of the modal is doing 
- The letters are far too small! 
- Gproms workspace instead of where to save 
- Process instead of model 
- save variable set, must come from master process set above. 
- create digital application project, new 
- cancel instead of close 
- in terms of demo this is the model, the people listening don't understand everything. Explaination for all of this. 
- The lorum impsem text is going to be the path of the node 
- The title of the sidebar may not be necassary 
- Selecting variables from unit FBR or whatever it is that relays what the user thinks about. 
- Timestamp for checking 
- call it something ppe controller or the name of the Nuclear plant.
- Model will no longer be there 
- There was a table viewer on the left 
- Focusing on the development. 
- Remove the welcome to engineering studio and replace with engineering studio version 2
- The little details are truely important within the app.
- Loaded the GVA project to show the new property editor.
- where does this window appear?
- at the moment we are using workspaces for debugging and swicth 
- in the demo where will the window appear?
- side by side with the flowsheet
- The name and the categories.
- click on K toggles
- early next week we will have the proper layouts. 


## Lenam prototypes
- ignore the status 
- variable name should be variable
- The property editor has been updated 
- the property sub editor 
- a list of all the varibles and the properties and sub properties
- on the left list of variables
- how do you select measured variables?
- everything that is MEA 
- Measure variable, what is the category called? 
- measured variable
- shows all the variables that have the sub property measured variable.
- accept if available  and accept is invalid?
- everthing is standardised as much as possible
- can we put it in the meta file
- it might be better to say that this property is done like this.
- the things I am telling you to change are fundemental concepts in GDAP.
- action if invalid 
- The property is based off the source 
- I wouldn't want asa to work on it now becasue it has not been approved
- the symbal to the left of the dropdown?
- They have been changed since when? (The symbols)
- whatever the default was then the idicator will come up 
- this hasn't been implemented 
- only show some of them as changed.
- Mariana is all yellow and that some of it hasn't been changed
-  We have to make a decision on upper case and lower case.
-  normally lower case
-  no camal casing 
-  we can read the bounds externally 
-  production is the variabble
- the external refers to?
- the measured value
- The source may have standard deviation
- There may need to be a reminder 
- The heading measure value is highlighted
- All filter based 
- The spacing between the two filter variables 
- Those boxes 
- show me only the things that have changed
- modified subproperties
- show changes only and only a check box 
- delete the heading and modify the sub property and show changes only 
- We need a toggle for showing changes and show defaults
- Kind of structure that we can use with the filters 
- All the fixed source organise all the unneccary columns 
- How did we select those rows?
- when we click the row it highlights the selected rows 
- Putting property in the column on the left



## Tuesday and Wednesday updates for next week
- 4 O'clock meetings
- what ever is ready
- when is project file is updated.
- in the normal situation there is a save function
- The linked variable is implemented then 
- Open is only available when saved. 
- The main milestone is opening, saving, doing the demo exiting and then re-opening with the same data.
- This is what we are aiming for!


## Penny Slideshow
- a quick recap of the current app
- why we need the migration and how
- The development process
- Architecture and the demo 
- should we have the demo before the theory 
- Demo prototype is ts own section
- 