Open budschi opened 10 months ago
fot @ThomasTSC :
lab_id
present in the schema: growthrunstep, growthrun(recipe), substrate, final sampleI created an issue for the LayTecd EpiTT schema --> #65
@budschi
Done:
TODOs:
Planned for later on:
- [x] for @ThomasTSC: prepare an excel file from 2013-2019 with growth, substrate, and characterization (due for the demo on 19th of February Colloquium IKZ)
@aalbino2 I uploaded already two sets of files from year 2019, 2018, 2017 and 2016.
[x] which parameter is static in the experiment, which one may be varied?
[ ] check whether process parameters change in different rows for same experiment (@aalbino2).
[x] we will need to create two samples for each process, a Gallium and a reference (sapphire). @ThomasTSC could you please put at least one dataset with sapphire data? (due for the demo on 19th of February Colloquium IKZ)
@aalbino2 please check 20-158-G+A
push_gas_valve
uniform_valve
can be in the environment
sub_sectionTODOs (@aalbino2 )
implement a check in the create_archive function that checks if the file exist already and - if the file exists and the content is identical - do not complain and go on with overwriting. @hampusnasstrom I'll mention this to you next data modeling meeting. Ideally, we can set up a create_archive function and share it in 100% of the cases
implement a check in the create_archive function that checks if the file exist already and - if the file exists and the content is identical - do not complain and go on with overwriting. @hampusnasstrom I'll mention this to you next data modeling meeting. Ideally, we can set up a create_archive function and share it in 100% of the cases
Okay, that sounds like what my create_archive function does already except that it doesn't overwrite.
implement a check in the create_archive function that checks if the file exist already and - if the file exists and the content is identical - do not complain and go on with overwriting. @hampusnasstrom I'll mention this to you next data modeling meeting. Ideally, we can set up a create_archive function and share it in 100% of the cases
Okay, that sounds like what my create_archive function does already except that it doesn't overwrite.
The one I use also check if it exists, but is not checking if the archive that exist is the very same, and it always raises a warning. So basically @ThomasTSC cannot reprocess his stuff without removing before all the generated ThinFilm and ThinFilmStack archives. This is annoying I believe.
Lemme check yours, where is it leaving?
implement a check in the create_archive function that checks if the file exist already and - if the file exists and the content is identical - do not complain and go on with overwriting. @hampusnasstrom I'll mention this to you next data modeling meeting. Ideally, we can set up a create_archive function and share it in 100% of the cases
Okay, that sounds like what my create_archive function does already except that it doesn't overwrite.
The one I use also check if it exists, but is not checking if the archive that exist is the very same, and it always raises a warning. So basically @ThomasTSC cannot reprocess his stuff without removing before all the generated ThinFilm and ThinFilmStack archives. This is annoying I believe.
Lemme check yours, where is it leaving?
for @aalbino2
Important: @budschi I'm at the point of touching the APP
We need to put the entry_type quantity in the "APP" of IKZ
We need to update the APP of the IKZ!!
Why "user defined quantities" filter does not appear in the "ALL -> Entries" ??
Why growth_rate is not found in the "user defined quantities"?
@budschi @hampusnasstrom let's discuss the APP in IKZ Oasis together!
@ka-sarthak @ThomasTSC
During your next meeting, please add here any task that you figure out should be accomplished, following the email exchange we had, where I was asking some doubts to @ThomasTSC
Thank you
I reviewed the current status of the MOVPE IKZ Ga2O3 Experiment schema, also with a focus on connecting the MOVPE growth process GrowthRun and the epiTT in-situ measurement schema plugin.
I came up with the follwing things regarding
GrowthRun
andGrowthRunStep
:GrowthRun
--> process activity:steps
)lab_id
ofGrowthRun
should beRecipe Name
fromGrowthRunStep
!? --> take from xlsxSamples
: should be populated with the sample ID from Name inGrowthRunStep
--> "sample Name" in xlsxinstrument
: create a NOMAD Entry based on theinstrument
base section and reference all processe with it, later the instrument could be extended to any detailGrowthRunStep
Name
is thelab_id
of the sample and should go into thesamples
subsectionSubstrate_name
better go one level up from the specific step into the global or base section oth theGrowthRun
schema -->samples!
?recipe_name
islab_id
ofGrowthRun
--> should go into base section or act as a global quantity of the processlaytec Temperature
should be fetched from [epiTT ]((https://github.com/FAIRmat-NFDI/AreaA-data_modeling_and_schemas/tree/main/LayTec_EpiTT) nomad entry --> harmonization of the schemas, Could be taken when timestamps of process and epiTT measurement are alignedcarier gas
,rotation
,push gas
etcbubbler
section should go into NOMAD Material process plugin and get normalizer to calculatepartial pressure
etc. and also thegas sources
and other sourcesgeneral task:
lab_ids
of all activities and entities of MOVPE IKZ Ga2O3 Experiment for consitency and in the different data files/sources --> facilitate automated referencing of the different entries in NOMAD@aalbino2: please let me know your opinion and discuss the points with Ta-Shun