matteolucchini1 / matteolucchini1/BHJet

Default input parameters appear incorrect for a default test run

Open
#61 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
18
Forks
9
PR merge metrics
No merged PRs in 30d

Description

When I the current master branch, adjust the compilation commands in `MakeBHJet`, build and then run `bhwrap.x`, I get the following output:

```
Unphysical pair content: -88.1873 pairs per proton. Check the value of plasma beta!
Temperature too high, assuming it's 2500 kev for IC calculation!
Don't trust the output spectrum slope and change parameters!
Temperature too high, assuming it's 2500 kev for IC calculation!
Don't trust the output spectrum slope and change parameters!
Total running time: 1.02961 seconds
```

I'm not sure if I did anything wrong, but I don't notice any changes I made other than those mentioned above: just pointing the compiler to my GSL library.

I checked my input file (also detailed below), and it's indeed the same as this repository's `BHJet/Input/ip.dat`.

```
1e9 //black hole mass
2.5 //viewing angle
543e3 //distance (kpc)
0 //redshift
.9e-2 //jet power (Eddington units)
18 //r0 (rg)
600 //shock distance (rg)
600 //magnetic acceleration distance (rg)
6.6e5 //maximum distance (rg) - z_max
3000 //electron temperature (electron peak gamma) - eltemp
.1 // % non thermal at dissipation region
0 // change plfrac over distance
1.95 //non-thermal slope - pspec
12 //shock heating
10. //dynamic time scale parameter
3e-6 //particle acceleratino time scale - fsc
1 //plasma beta
0.025 //acceleration sigma
0.01 //disk temperature/accretion rate
50 //disk inner radius (rg)
1e3 //disk outer radius (rg)
3300 //compar1
3e-10 //compar2
3.e10 //compar3
0 //compsw
15 //velsw
0 //infosw
1 //EBLsw
```

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the compilation commands in `MakeBHJet`, then reproduce the default run of `bhwrap.x` using `BHJet/Input/ip.dat` and the reported GSL setup. Trace where the pair-content and temperature warnings are produced and compare the run with the expected default behavior; done means the cause and required correction are documented or fixed.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
hpc
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.