Output Variables from EBTEL2 (IDL version)

[chhabrasherry]

This may be a known problem, but I noticed that the listed outputs from EBTEL2.pro need to be written in order. If one tries to only get selected outputs (by name), the routine returns wrong outputs.

For example:
The initial calling sequence is written as (original ebtel2.pro):

ebtel2, ttime, heat, length, t, n, p, v, ta, na, pa, c11, dem_tr, dem_cor, $
logtdem, f_ratio, rad_ratio, cond, rad_cor,$
classical=classical, dynamic=dynamic, dem_old=dem_old, $
flux_nt=flux_nt, energy_nt=energy_nt, rtv=rtv, $
a_c=a_c, a_0=a_0, a_tr=a_tr, l_fact=l_fact

• Note the order of output variables*

Now, If I need dem_tr, dem_cor and logtdem as outputs, and I use the following command (shown as an example in the routine):
ebtel2, ttime, heat, t, n, p, v, dem_tr, dem_cor, logtdem

It will return ta, na, pa for dem_tr, dem_cor, and logtdem. i.e. one cannot skip specific output variables.

This is not clarified anywhere in the document, so it causes a lot of confusion. Also, I was wondering if there is a way to fix it.

[wtbarnes]

Hi Sherry. I've moved this issue to the EBTEL repository. ebtelplusplus is the C++ code. Hope that is ok!

Thanks for bringing this up. I have to admit I was not aware of this at all as I've not really used the IDL code much, particularly with the DEM outputs.

So just to clarify, in the documentation, you're saying that the calling sequence for computing the DEM variables should instead be

ebtel2, ttime, heat, length, t, n, p, v, ta, na, pa, c11, dem_tr, dem_cor, logtdem

It looks like this affects both the first and fourth code examples in the documentation.

[chhabrasherry]

Hi Will, Thanks so much. Sorry I did not realize that I added it to the C++ repository. Yes, you are right, to get DEM variables, all the others that are declared in the routine before DEM also need to be in the command. So, the order of output variables need to be exactly as it is in the routine. Similarly, if I want the rad_cor output, the command will be: ebtel2, ttime, heat, length, t, n, p, v, ta, na, pa, c11, dem_tr, dem_cor, logtdem, f_ratio, rad_ratio, cond, rad_cor

…

On Thu, Sep 15, 2022 at 10:00 AM Will Barnes ***@***.***> wrote: Hi Sherry. I've moved this issue to the EBTEL repository. ebtelplusplus is the C++. Hope that is ok! Thanks for bringing this up. I have to admit I was not aware of this at all as I've not really used the IDL code much, particularly with the DEM outputs. So just to clarify, in the documentation, you're saying that the calling sequence for computing the DEM variables should instead be ebtel2, ttime, heat, length, t, n, p, v, ta, na, pa, c11, dem_tr, dem_cor, logtdem — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASFMA6GBG32GHWRCZUPCAATV6MTYTANCNFSM6AAAAAAQNNPLJY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- -- Sherry Chhabra (she/her), Postdoctoral Research Fellow, Naval Research Laboratory/GMU Editor, SolarNews Mobile: +1-201-719-3935 e-mail: ***@***.*** ***@***.*** ***@***.***

[wtbarnes]

Ok, I can easily amend the README to reflect that.

Do you know if there is an easier way to provide access to those optional variables, e.g. if I want dem_cor and logtdem, can I get those without having to list out all of those variables before them? Maybe through the use of keywords?

I'm not sure of the best way to do that or if it is possible. I'm really showing my IDL ignorance here...

[chhabrasherry]

Thanks, Could you please also add that instruction to the routine as well for now, so whoever downloads it moving forward, knows? Honestly, I do not know how to solve it either, but I am certainly looking into it. I'll let you know as soon as I find anything.

…

On Thu, Sep 15, 2022 at 1:08 PM Will Barnes ***@***.***> wrote: Ok, I can easily amend the README to reflect that. Do you know if there is an easier way to provide access to those optional variables, e.g. if I want dem_cor and logtdem, can I get those without having to list out all of those variables before them? Maybe through the use of keywords? I'm not sure of the best way to do that or if it is possible. I'm really showing my IDL ignorance here... — Reply to this email directly, view it on GitHub <#6 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASFMA6HI64UPKDRLAXX4MKLV6NJZZANCNFSM6AAAAAAQNNPLJY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- -- Sherry Chhabra (she/her), Postdoctoral Research Fellow, Naval Research Laboratory/GMU Editor, SolarNews Mobile: +1-201-719-3935 e-mail: ***@***.*** ***@***.*** ***@***.***