search

andreatramacere / jetset-installer

1 stars 1 forks source link

SED modeling using two-zone leptonic scenarios #2

Open Ayon2001 opened 4 weeks ago

Ayon2001 commented 4 weeks ago

Hi @andreatramacere ,

I am working on broad-band Blazar SED modeling using JetSeT, here we are using the one-zone leptonic model.

But, in some cases, I have to use a two-zone leptonic scenario. How can I model two-zone scenario with JetSeT.

andreatramacere commented 4 weeks ago

Hi @Ayon2001, you can find all the info here: https://jetset.readthedocs.io/en/latest/user_guide/documentation_notebooks/composite_model/Composite_model.html

Ayon2001 commented 3 weeks ago

Dear @andreatramacere

The issue is modeling the SEDs considering two-zone scenarios, assuming that one emission region is within the BLR and the other is outside, or something like that, which says that there will be two peaks in the synchrotron hump and the two peaks of synchrotron hump are coming from two different emission regions. The composite model [https://jetset.readthedocs.io/en/latest/user_guide/documentation_notebooks/composite_model/Composite_model.html] does not say about the two-zone leptonic model. Is this kind of two-zone modeling possible using JetSeT??

andreatramacere commented 3 weeks ago

Dear @Ayon2001, please, read the documentation carefully, down to the section: "Sum of two jets (steady and flaring) and application of the EBL absorption to both (Multiplicative and additive)"

The composite model allows you to combine (add in your case) two or more models, they can be leptonic jets or other entities. It is up to you to define the details, the code has to offer only the means. If you want to have two one inside and one outside of the BLR, you have:

1) to create two jet models, link the disk, and BLR (and DT if present) parameters, for example, if jet1 is the one within the BLR, in jet2 you link all the EC/Disk pars to jet1 (the documentation explains how)

2) put constraints on R_H in jet2 to be outside of the BLR

3) when implementing the EC please, read the corresponding section in the documentation, and add the functional dependencies for the BRL/DT parameters

As a final comment, issues are meant for bug fixing, or to express desired features for future releases, in issues I can't explain what is already provided in the documentation or go into more details, unless you do not provide a code, that I can run, where you highlight exactly what you would achieve and which is the limit.

Cheers Andrea