gdat issueshttps://gitlab.epfl.ch/spc/gdat/-/issues2021-10-21T15:54:28Zhttps://gitlab.epfl.ch/spc/gdat/-/issues/43Error in extracting nbi data2021-10-21T15:54:28ZMichele MarinError in extracting nbi dataThe following warnings are issued when using 'tcv2ids2database(64862,0001,'ids_names','nbi')' on spcimas.
```
Warning: problems loading data for tdi('\results::nbh:energy'); for data_request= \results::nbh:energy
Warning: problems loadi...The following warnings are issued when using 'tcv2ids2database(64862,0001,'ids_names','nbi')' on spcimas.
```
Warning: problems loading data for tdi('\results::nbh:energy'); for data_request= \results::nbh:energy
Warning: problems loading data for tdi('\results::nbh:fraction'); for data_request= \results::nbh:fraction
```
Similarly, the following are issued when using 'aa=gdat(64862,'ids','source','nbi')' (full error message)
```
Warning: problems loading data for tdi('\results::nbh:powr_tcv'); for data_request= \results::nbh:powr_tcv
> In gdat_tcv (line 529)
In tcv_get_ids_nbi (line 75)
In gdat_tcv (line 1487)
In gdat (line 190)
Warning: problems loading data for tdi('\results::nbh:energy'); for data_request= \results::nbh:energy
> In gdat_tcv (line 529)
In tcv_get_ids_nbi (line 81)
In gdat_tcv (line 1487)
In gdat (line 190)
Warning: problems loading data for tdi('\results::nbh:fraction'); for data_request= \results::nbh:fraction
> In gdat_tcv (line 529)
In gdat (line 190)
In tcv_get_ids_nbi (line 87)
In gdat_tcv (line 1487)
In gdat (line 190)
```
The code still goes through, but I guess that some of the IDSs are not filled properlyMatteo Vallarmatteo.vallar@epfl.chMatteo Vallarmatteo.vallar@epfl.chhttps://gitlab.epfl.ch/spc/gdat/-/issues/42set up imas tests on spcimas2021-10-07T07:36:21ZFederico Feliciset up imas tests on spcimashttps://gitlab.epfl.ch/spc/gdat/-/issues/41NBI fraction2023-03-09T16:39:48ZOlivier SauterNBI fraction@vallar To check line 93 of TCV_IMAS/tcv_get_ids_nbi.m:
`i_frac = i_frac.*1./repmat(sum(i_frac,2), 1, 3);`
I am astonished there are digits instead of "size(xxx,yy)" for example as before. This comes after your (old) merge request for ...@vallar To check line 93 of TCV_IMAS/tcv_get_ids_nbi.m:
`i_frac = i_frac.*1./repmat(sum(i_frac,2), 1, 3);`
I am astonished there are digits instead of "size(xxx,yy)" for example as before. This comes after your (old) merge request for the nbi fraction: old branch: fix_ids_curr_fracMatteo Vallarmatteo.vallar@epfl.chMatteo Vallarmatteo.vallar@epfl.chhttps://gitlab.epfl.ch/spc/gdat/-/issues/40Read NB22021-10-11T14:48:39ZMatteo Vallarmatteo.vallar@epfl.chRead NB2TCV NB2 is online, we should add it in the gdat call to powers
The signal I use is `\RESULTS::NB2:POWR_TCV`, but all the names are the same as `NBH`
An example shot is 71588TCV NB2 is online, we should add it in the gdat call to powers
The signal I use is `\RESULTS::NB2:POWR_TCV`, but all the names are the same as `NBH`
An example shot is 71588https://gitlab.epfl.ch/spc/gdat/-/issues/39summary field in ids structure2021-03-08T16:45:34ZMatteo Vallarmatteo.vallar@epfl.chsummary field in ids structure@osauter
I loaded a matlab ids structure from lacs, with the following command
`data=tcv2ids(64770, 'trialindx',3);`
Then I moved the structure I got to the iter cluster (you can find it in '/home/ITER/vallarm/public/data_64770_ids_t...@osauter
I loaded a matlab ids structure from lacs, with the following command
`data=tcv2ids(64770, 'trialindx',3);`
Then I moved the structure I got to the iter cluster (you can find it in '/home/ITER/vallarm/public/data_64770_ids_trialindx3.mat')
In that structure, there is the field "summary" and when I do ids2database it is complaining because it cannot write that field. I will remove it from the structure as quick-fix, but is it possible to set it as "not ids name" as is done with the following?
```
these subfields are not ids names, so not used: core_profiles_description ec_launchers_description equilibrium_description magnetics_description nbi_description params_tcv2ids pf_active_description summary_description tf_description thomson_scattering_description wall_description
```https://gitlab.epfl.ch/spc/gdat/-/issues/38Follow-up from "fix TCV ids for version 3.31"2021-02-17T16:51:59ZOlivier SauterFollow-up from "fix TCV ids for version 3.31"The following discussion from !88 should be addressed:
- [ ] @osauter started a [discussion](https://gitlab.epfl.ch/spc/gdat/-/merge_requests/88#note_81899): (+10 comments)
> @vallar Can you test on ITER IO the full data get and w...The following discussion from !88 should be addressed:
- [ ] @osauter started a [discussion](https://gitlab.epfl.ch/spc/gdat/-/merge_requests/88#note_81899): (+10 comments)
> @vallar Can you test on ITER IO the full data get and write, I put the branch "fix TCV ids for version 3.31" for the "official gdat" in my public. I added the CXRS links
>
> Once checked I'll add the ids_empty of the most recent version so it will work from the lacs as well
>
> @amerle @vallar It had "wrong" default structure even when running it at ITER-IO because there was an ```if exist('ids_list') else use IDS_list``` which was not working as expected because matlab was thinking the first ids_list was misprinted and asking if IDS_list should be used... I am now checking ```if exist('IDS_list')``` (this is historical we can soon, may be already now, forget about the former ids_list function)Antoine MerleAntoine Merlehttps://gitlab.epfl.ch/spc/gdat/-/issues/37core_profiles.profiles_1d[0].ion[0].label2021-02-04T11:39:32ZMatteo Vallarmatteo.vallar@epfl.chcore_profiles.profiles_1d[0].ion[0].label@amerle @osauter
Is the field `core_profiles.profiles_1d[0].ion[0].label` filled using `ids2database`?@amerle @osauter
Is the field `core_profiles.profiles_1d[0].ion[0].label` filled using `ids2database`?https://gitlab.epfl.ch/spc/gdat/-/issues/36Changes of core_profiles/profiles_1d/grid/area to core_profiles/profiles_1d/g...2021-02-08T10:27:38ZMatteo Vallarmatteo.vallar@epfl.chChanges of core_profiles/profiles_1d/grid/area to core_profiles/profiles_1d/grid/surface@osauter @amerle
I think the name of a `core_profiles/profiles_1d/grid/area` changed to `core_profiles/profiles_1d/grid/surface` in latest imas version.
If I load `IMAS/3.27.0-4.7.1`, everything works smoothly
```
$ module load MATL...@osauter @amerle
I think the name of a `core_profiles/profiles_1d/grid/area` changed to `core_profiles/profiles_1d/grid/surface` in latest imas version.
If I load `IMAS/3.27.0-4.7.1`, everything works smoothly
```
$ module load MATLAB
$ module load IMAS
$ matlab-nodesktop
>> ids=load('/home/ITER/vallarm/public/68587_eq_coreprof.mat');
>> run ~/../sautero/public/matlab/startup.m
>> [ids_put_status] = ids2database(68587, 001, 001, ids);
core_profiles ec_launchers equilibrium magnetics nbi pf_active summary tf thomson_scattering wall Warning: IDS_list not available, quick fix introducing list of ids available for TCV: b
> In ids2database (line 92)
these subfields are not ids names, so not used: core_profiles_description equilibrium_description params_tcv2ids
problems in putting data in database:
Error using ids_put
Unable to get field surface from input structure
... in field profiles_1d/grid/surface
... in IDS core_profiles
Error in ids2database (line 126)
ids_put(idx,[ids_to_get '/' num2str(occurence)],ids2put.(ids_to_get));
```https://gitlab.epfl.ch/spc/gdat/-/issues/35Error using CXRS_get_profiles from ITER gateway2021-02-08T10:53:55ZMatteo Vallarmatteo.vallar@epfl.chError using CXRS_get_profiles from ITER gatewayI get the following error trying to connect from ITER HPC
```
>>> %here above stuff to connect are set
>>> shot=69087;
>>> [ids_from_tcv,idsok] = tcv2ids(shot,'ids_names',ids2get);
use structure in .mat file: /home/ITER/sautero/public/m...I get the following error trying to connect from ITER HPC
```
>>> %here above stuff to connect are set
>>> shot=69087;
>>> [ids_from_tcv,idsok] = tcv2ids(shot,'ids_names',ids2get);
use structure in .mat file: /home/ITER/sautero/public/matlab/gdat/matlab/TCV/../TCV_IMAS/ids_empty/ids_empty_core_profiles
Warning: problems calling gdat_tcv
> In gdat (line 196)
In tcv_get_ids_core_profiles (line 236)
In gdat_tcv (line 1419)
In gdat (line 190)
In tcv2ids (line 115)
there is a problem with: tcv_get_ids_core_profiles , may be check if it exists in your path or test it by itself
Warning: problems calling gdat_tcv
> In gdat (line 196)
In tcv2ids (line 115)
Undefined function or variable 'CXRS_get_profiles'.
Error in gdat_tcv (line 939)
aa=CXRS_get_profiles; cxrs_params = aa.param;
Error in gdat (line 190)
[gdat_data,gdat_params,error_status,varargout] = feval(['gdat_' lower(machine_eff)],args{:});
Error in tcv_get_ids_core_profiles (line 236)
temp_1d.cxrs_rho = gdat(params_cores_profiles.shot,params_eff_fit1);
Error in gdat_tcv (line 1419)
[ids_top,ids_top_description] = feval(['tcv_get_ids_' ids_top_name],shot,ids_empty,gdat_data.gdat_params);
Error in gdat (line 190)
[gdat_data,gdat_params,error_status,varargout] = feval(['gdat_' lower(machine_eff)],args{:});
Error in tcv2ids (line 115)
tmp = gdat(shot,gdat_params);
```https://gitlab.epfl.ch/spc/gdat/-/issues/34Job Failed #1769412020-11-30T14:30:41ZFederico FeliciJob Failed #176941The nightly tests are failing for `gdat` since the latest change, see e.g.
Job [#176941](https://gitlab.epfl.ch/spc/gdat/-/jobs/176941) failed for 7a655c5fff0b3be51366f9ecd6c6f3877b7482cb:
Try to run the tests locally to see whether th...The nightly tests are failing for `gdat` since the latest change, see e.g.
Job [#176941](https://gitlab.epfl.ch/spc/gdat/-/jobs/176941) failed for 7a655c5fff0b3be51366f9ecd6c6f3877b7482cb:
Try to run the tests locally to see whether they fail locally as well or whether it's an issue with the test setup.
You can see the script the test is trying to run on line 44 of the test log:
https://gitlab.epfl.ch/spc/gdat/-/jobs/176941#L44Olivier SauterOlivier Sauterhttps://gitlab.epfl.ch/spc/gdat/-/issues/33consider exploiting gitlab's `matrix` facility2020-10-12T14:41:34ZFotis Georgatosconsider exploiting gitlab's `matrix` facilityin relation to the multiple tests against matlab ;
this is fyi:
* https://about.gitlab.com/releases/2020/09/22/gitlab-13-4-released/#parallel-matrix-jobs-show-relevant-variables-in-job-namein relation to the multiple tests against matlab ;
this is fyi:
* https://about.gitlab.com/releases/2020/09/22/gitlab-13-4-released/#parallel-matrix-jobs-show-relevant-variables-in-job-namehttps://gitlab.epfl.ch/spc/gdat/-/issues/32Load/Plot ASTRA results without CXRS data2020-09-17T07:57:27ZAlexander KarpushovLoad/Plot ASTRA results without CXRS dataThere is an error in ASTRA_TCV_summary.m for TCV shots without the CXRS data - need to updateThere is an error in ASTRA_TCV_summary.m for TCV shots without the CXRS data - need to updateMatteo Vallarmatteo.vallar@epfl.chMatteo Vallarmatteo.vallar@epfl.chhttps://gitlab.epfl.ch/spc/gdat/-/issues/31No deployment for 8302020-06-16T13:25:31ZFederico FeliciNo deployment for 830@amerle @osauter@amerle @osauterFederico FeliciFederico Felicihttps://gitlab.epfl.ch/spc/gdat/-/issues/30Job Failed #1181142020-06-16T10:41:41ZFederico FeliciJob Failed #118114@osauter this is not related to the deployment problems but the 'all' tests run overnight failed on the new `master`...
Job [#118114](https://gitlab.epfl.ch/spc/gdat/-/jobs/118114) failed for 88253476d1461618ace614a2875e33d0c9b9cf31:@osauter this is not related to the deployment problems but the 'all' tests run overnight failed on the new `master`...
Job [#118114](https://gitlab.epfl.ch/spc/gdat/-/jobs/118114) failed for 88253476d1461618ace614a2875e33d0c9b9cf31:Olivier SauterOlivier Sauterhttps://gitlab.epfl.ch/spc/gdat/-/issues/29deployment fails again https://gitlab.epfl.ch/spc/gdat/pipelines/429902020-05-27T07:42:24ZOlivier Sauterdeployment fails again https://gitlab.epfl.ch/spc/gdat/pipelines/42990How do you create an issue directly from there?
@ffelici I cannot resolve the new problemHow do you create an issue directly from there?
@ffelici I cannot resolve the new problemJoan DeckerJoan Deckerhttps://gitlab.epfl.ch/spc/gdat/-/issues/28Job Failed #1180502020-05-27T07:43:35ZFederico FeliciJob Failed #118050Job [#118050](https://gitlab.epfl.ch/spc/gdat/-/jobs/118050) failed for 88253476d1461618ace614a2875e33d0c9b9cf31:Job [#118050](https://gitlab.epfl.ch/spc/gdat/-/jobs/118050) failed for 88253476d1461618ace614a2875e33d0c9b9cf31:Olivier SauterOlivier Sauterhttps://gitlab.epfl.ch/spc/gdat/-/issues/27deploy failed2020-05-26T18:37:07ZOlivier Sauterdeploy failed@ffelici @decker it seems there is a problem with deployment, some folders being links...?
can you check for gdat?@ffelici @decker it seems there is a problem with deployment, some folders being links...?
can you check for gdat?https://gitlab.epfl.ch/spc/gdat/-/issues/26Proposition to have all systems data as default for all TS related requests2020-05-06T12:37:13ZAntoine MerleProposition to have all systems data as default for all TS related requests@osauter Currently if you ask for `ne`, `te` or `nete_rho` you only get the main system even in the shot range where the edge system was available. I would like that the default be that you get data from all available systems.
The main ...@osauter Currently if you ask for `ne`, `te` or `nete_rho` you only get the main system even in the shot range where the edge system was available. I would like that the default be that you get data from all available systems.
The main question remains how to specify the different options. One possibility is:
| Value of `edge` option | system |
| ------ | ------ |
| 0 | M |
| 1 | E |
| 2 (Default) | M+E |
Or we could introduce a `main` option, and both `main` and `edge` would default to 1.
I can take care of the implementation, once we agree.https://gitlab.epfl.ch/spc/gdat/-/issues/25Update `gdat` deployment following update to deployment tools2020-04-24T09:35:35ZFederico FeliciUpdate `gdat` deployment following update to deployment toolsSince we updated some details of the deployment tools, we need to update some parts of the gdat deployment settings.
@osauter please let me know when you want to do a new deployment and I will set it up.Since we updated some details of the deployment tools, we need to update some parts of the gdat deployment settings.
@osauter please let me know when you want to do a new deployment and I will set it up.Federico FeliciFederico Felicihttps://gitlab.epfl.ch/spc/gdat/-/issues/24multiple data_requests and multiple shot_numbers as input2020-03-12T12:55:04ZNgoc Minh Trang Vumultiple data_requests and multiple shot_numbers as inputIt may be useful if the users can define the data_request as a list of keywords/param_names they want to get and call:
>> out = gdat(shot,{'ip','q0',...})
or even as for several shots for the comparison:
>> out = gdat([shot1, shot2, ... ...It may be useful if the users can define the data_request as a list of keywords/param_names they want to get and call:
>> out = gdat(shot,{'ip','q0',...})
or even as for several shots for the comparison:
>> out = gdat([shot1, shot2, ... ],{'ip', 'q0'},1)
The output out may be in form of a structure, for example out.shot1.ip, out.shot1.q0, etc. And eventually the users can obtain a plot with subplots of all the params they ask for.Olivier SauterOlivier Sauter