NFMAX and lensing with NFW profiles

[Dominik Rhiem]

Dear all,

I have encountered a few issues when trying to run Lenstool. Specifically, my goal is to create maps of background sources to then lens them with an NFW cluster through Lenstool. Currently, I am using a dummy map of evenly spaced background sources of the same magnitude and redshift and trying to lens that map. However, I have three questions/issues so far; first, I seem to be unable to influence the concentration parameter of that cluster, independent of my choice of r_s and r200. Is there any way for me to change it? Second, there is an error with "rtbis2", see also the attached log file. Third (see also the attached log file), there is the following error: "[ERROR] Too many sources in even-grid.cat. NFMAX limit is 908". I have also encountered the same issue of "NFMAX limit is 908" when trying to reproduce maps of another group, so I know the parameter and catalogue files are fine for that case, and I have not found any clues on the wiki with regards to this parameter. Can somebody help and explain?

I am using the compiled version of Lenstool 7.1 for Linux, as found on the Wiki, and I have attached my test parameter file and my "dummy" source catalogue. Please let me know if anything is unclear.

Sincerely,

Dominik Rhiem

[Johan Richard]

Hi Dominik

I will let other users more familiar with them answer about NFW profiles, I do not normally adjust specifically this parameter.

Regarding NFMAX (or other dimension values) they are machine dependent but can be adjusted in the dimension.h in include from the sources.

I would strongly advise using the git version from lenstool to get the most up to date version and developments, that is the first link on the wiki: 

https://git-cral.univ-lyon1.fr/lenstool/lenstool

I am happy to help with the installation if needed.

Best

Johan

--
--
_____________________________________________________________________
LENSTOOL: http://projets.lam.fr/projects/lenstool/wiki
To post to this group, send email to lens...@googlegroups.com
To unsubscribe from this group, send email to lenstool-u...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/lenstool?
---
You received this message because you are subscribed to the Google Groups "lenstool" group.
To unsubscribe from this group and stop receiving emails from it, send an email to lenstool+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lenstool/CAEyWfYnjwqsQTaAaTLPUmthf2aKu7-J3HZy%3DhOG4Sm4zkrmJLg%40mail.gmail.com.

[Jean-Paul Kneib]

Hi Dominik:

Regarding the NFW parameters, it seems that in your log output the M200 is unphysical, likely due to the rtbis2 error … looks like some parameter input issues.

Can you share also your para.out file?

Thanks

Jp

To view this discussion on the web visit https://groups.google.com/d/msgid/lenstool/CAMwZtF%2BBPxY6%3Dijhu_L%2Bp_-o8oDLSqgoEN7S%3DYEFhsx_fqdhhg%40mail.gmail.com.

[Dominik Rhiem]

Hi Joseph, hi Jean-Paul,

First of all, the issue is that, when I was testing, I was changing Rs and R200 and also their ratios, but the resulting concentration parameter was still the same. Either way, I prefer to write it using M200 and concentration, too, so could somebody show me the specific way to provide these parameters in my file? I have not found them in the documentation.

I am also currently corresponding with Johan, there are some issues with installing Lenstool on my system, but I do want to use the latest version. I have also attached the para.out file.

Sincerely,

Dominik

Am Sa., 27. Juni 2020 um 14:30 Uhr schrieb Joseph E. Coleman <jec0...@utdallas.edu>:

Hi Dominik,

The NFW profile has only two free parameters.  If you specify the scale radius and R200, then everything is derived from those values.   If you want to influence the concentration, then you'll need to not specify either Rs or R200.  Personally, I prefer working with M200 and concentration when describing NFW halos, then I just derive the other values, R200 and Rs.

I seem to recall some issues with a hard coded limit within lenstool.   I think I ended up just setting it to a large number.   You can always change the constant and recompile.  I would also recommend sticking with a release version and not necessarily use the nightly or latest commit.  The reason being is for reproducibility and for comparing your work to others and theirs to yours.  If that's not an issue, then it doesn't really matter except maybe for stability and bugs.

Regards,
Joe

[Dominik Rhiem]

Dear all,

I am still having a bit of an issue with Lenstool. I have managed to install the latest version of Lenstool (thanks again for the help there, Johan!) and I am now trying to lense a regular grid of point-sources which sit at the same redshift and all have the same magnitude. I want to lense it with an NFW cluster that is simply placed in the middle of this grid, no ellipticity or anything else involved. However, the resulting grid of images is not sensible; the magnitude has not changed at all and the locations have been spread out evenly, which does not make sense since the sources closer to the centre of the cluster should get lensed more strongly. Does anyone know what is happening? I have attached the parameter file (test.par), the input grid (even-grid-small.cat), the read-out parameters (para.out) and the lensed sources (source.dat).

Sincerely,

Dominik Rhiem

[Tomás]

Hi Dominik,

I think, you only need to change the integer in the "reference" keyword

You are using 3, RA, DEC...

Change to 2, and run it again....

Using your .par file, with 

runmode

reference     2 0.0 0.0

image     0 wfc3.mul

source    1 even-grid-small.cat 

inverse   0 0.100000 448

ampli   0 1800 1.5  mu.fits

end

....

I got...

COMP: images of the sources

COMP: grid at z=2.000 (0.362)

COMP: 0: multiplicity: 1 at (-50.000,-50.000): found 1 image(s)

COMP: 1: multiplicity: 1 at (-50.000,-40.000): found 1 image(s)

COMP: 2: multiplicity: 1 at (-50.000,-30.000): found 1 image(s)

COMP: 3: multiplicity: 1 at (-50.000,-20.000): found 1 image(s)

COMP: 4: multiplicity: 1 at (-50.000,-10.000): found 1 image(s)

COMP: 5: multiplicity: 1 at (-50.000,0.000): found 1 image(s)

COMP: 6: multiplicity: 1 at (-50.000,10.000): found 1 image(s)

COMP: 7: multiplicity: 1 at (-50.000,20.000): found 1 image(s)

COMP: 8: multiplicity: 1 at (-50.000,30.000): found 1 image(s)

COMP: 9: multiplicity: 1 at (-50.000,40.000): found 1 image(s)

COMP: 10: multiplicity: 1 at (-50.000,50.000): found 1 image(s)

COMP: 11: multiplicity: 1 at (-40.000,-50.000): found 1 image(s)

COMP: 12: multiplicity: 1 at (-40.000,-40.000): found 1 image(s)

COMP: 13: multiplicity: 1 at (-40.000,-30.000): found 1 image(s)

COMP: 14: multiplicity: 1 at (-40.000,-20.000): found 1 image(s)

COMP: 15: multiplicity: 1 at (-40.000,-10.000): found 1 image(s)

COMP: 16: multiplicity: 1 at (-40.000,0.000): found 1 image(s)

COMP: 17: multiplicity: 1 at (-40.000,10.000): found 1 image(s)

COMP: 18: multiplicity: 1 at (-40.000,20.000): found 1 image(s)

COMP: 19: multiplicity: 1 at (-40.000,30.000): found 1 image(s)

COMP: 20: multiplicity: 1 at (-40.000,40.000): found 1 image(s)

COMP: 21: multiplicity: 1 at (-40.000,50.000): found 1 image(s)

COMP: 22: multiplicity: 1 at (-30.000,-50.000): found 1 image(s)

COMP: 23: multiplicity: 1 at (-30.000,-40.000): found 1 image(s)

COMP: 24: multiplicity: 1 at (-30.000,-30.000): found 1 image(s)

COMP: 25: multiplicity: 1 at (-30.000,-20.000): found 1 image(s)

COMP: 26: multiplicity: 1 at (-30.000,-10.000): found 1 image(s)

COMP: 27: multiplicity: 1 at (-30.000,0.000): found 1 image(s)

COMP: 28: multiplicity: 1 at (-30.000,10.000): found 1 image(s)

COMP: 29: multiplicity: 1 at (-30.000,20.000): found 1 image(s)

COMP: 30: multiplicity: 1 at (-30.000,30.000): found 1 image(s)

COMP: 31: multiplicity: 1 at (-30.000,40.000): found 1 image(s)

COMP: 32: multiplicity: 1 at (-30.000,50.000): found 1 image(s)

COMP: 33: multiplicity: 1 at (-20.000,-50.000): found 1 image(s)

COMP: 34: multiplicity: 1 at (-20.000,-40.000): found 1 image(s)

COMP: 35: multiplicity: 1 at (-20.000,-30.000): found 1 image(s)

COMP: 36: multiplicity: 1 at (-20.000,-20.000): found 1 image(s)

COMP: 37: multiplicity: 1 at (-20.000,-10.000): found 1 image(s)

COMP: 38: multiplicity: 1 at (-20.000,0.000): found 1 image(s)

COMP: 39: multiplicity: 1 at (-20.000,10.000): found 1 image(s)

COMP: 40: multiplicity: 1 at (-20.000,20.000): found 1 image(s)

COMP: 41: multiplicity: 1 at (-20.000,30.000): found 1 image(s)

COMP: 42: multiplicity: 1 at (-20.000,40.000): found 1 image(s)

COMP: 43: multiplicity: 1 at (-20.000,50.000): found 1 image(s)

COMP: 44: multiplicity: 1 at (-10.000,-50.000): found 1 image(s)

COMP: 45: multiplicity: 1 at (-10.000,-40.000): found 1 image(s)

COMP: 46: multiplicity: 1 at (-10.000,-30.000): found 1 image(s)

COMP: 47: multiplicity: 1 at (-10.000,-20.000): found 1 image(s)

COMP: 48: multiplicity: 1 at (-10.000,-10.000): found 1 image(s)

COMP: 49: multiplicity: 1 at (-10.000,0.000): found 1 image(s)

COMP: 50: multiplicity: 1 at (-10.000,10.000): found 1 image(s)

COMP: 51: multiplicity: 1 at (-10.000,20.000): found 1 image(s)

COMP: 52: multiplicity: 1 at (-10.000,30.000): found 1 image(s)

COMP: 53: multiplicity: 1 at (-10.000,40.000): found 1 image(s)

COMP: 54: multiplicity: 1 at (-10.000,50.000): found 1 image(s)

COMP: 55: multiplicity: 1 at (0.000,-50.000): found 1 image(s)

COMP: 56: multiplicity: 1 at (0.000,-40.000): found 1 image(s)

COMP: 57: multiplicity: 1 at (0.000,-30.000): found 1 image(s)

COMP: 58: multiplicity: 1 at (0.000,-20.000): found 1 image(s)

COMP: 59: multiplicity: 1 at (0.000,-10.000): found 1 image(s)

COMP: 60: multiplicity: 9 at (0.000,0.000): found 9 image(s)

COMP: large distorsion 60 (0.000,0.000) (0.500,0.500,0.000)

COMP: 61: multiplicity: 1 at (0.000,10.000): found 1 image(s)

COMP: 62: multiplicity: 1 at (0.000,20.000): found 1 image(s)

COMP: 63: multiplicity: 1 at (0.000,30.000): found 1 image(s)

COMP: 64: multiplicity: 1 at (0.000,40.000): found 1 image(s)

COMP: 65: multiplicity: 1 at (0.000,50.000): found 1 image(s)

COMP: 66: multiplicity: 1 at (10.000,-50.000): found 1 image(s)

COMP: 67: multiplicity: 1 at (10.000,-40.000): found 1 image(s)

COMP: 68: multiplicity: 1 at (10.000,-30.000): found 1 image(s)

COMP: 69: multiplicity: 1 at (10.000,-20.000): found 1 image(s)

COMP: 70: multiplicity: 1 at (10.000,-10.000): found 1 image(s)

COMP: 71: multiplicity: 1 at (10.000,0.000): found 1 image(s)

COMP: 72: multiplicity: 1 at (10.000,10.000): found 1 image(s)

COMP: 73: multiplicity: 1 at (10.000,20.000): found 1 image(s)

COMP: 74: multiplicity: 1 at (10.000,30.000): found 1 image(s)

COMP: 75: multiplicity: 1 at (10.000,40.000): found 1 image(s)

COMP: 76: multiplicity: 1 at (10.000,50.000): found 1 image(s)

COMP: 77: multiplicity: 1 at (20.000,-50.000): found 1 image(s)

COMP: 78: multiplicity: 1 at (20.000,-40.000): found 1 image(s)

COMP: 79: multiplicity: 1 at (20.000,-30.000): found 1 image(s)

COMP: 80: multiplicity: 1 at (20.000,-20.000): found 1 image(s)

COMP: 81: multiplicity: 1 at (20.000,-10.000): found 1 image(s)

COMP: 82: multiplicity: 1 at (20.000,0.000): found 1 image(s)

COMP: 83: multiplicity: 1 at (20.000,10.000): found 1 image(s)

COMP: 84: multiplicity: 1 at (20.000,20.000): found 1 image(s)

COMP: 85: multiplicity: 1 at (20.000,30.000): found 1 image(s)

COMP: 86: multiplicity: 1 at (20.000,40.000): found 1 image(s)

COMP: 87: multiplicity: 1 at (20.000,50.000): found 1 image(s)

COMP: 88: multiplicity: 1 at (30.000,-50.000): found 1 image(s)

COMP: 89: multiplicity: 1 at (30.000,-40.000): found 1 image(s)

COMP: 90: multiplicity: 1 at (30.000,-30.000): found 1 image(s)

COMP: 91: multiplicity: 1 at (30.000,-20.000): found 1 image(s)

COMP: 92: multiplicity: 1 at (30.000,-10.000): found 1 image(s)

COMP: 93: multiplicity: 1 at (30.000,0.000): found 1 image(s)

COMP: 94: multiplicity: 1 at (30.000,10.000): found 1 image(s)

COMP: 95: multiplicity: 1 at (30.000,20.000): found 1 image(s)

COMP: 96: multiplicity: 1 at (30.000,30.000): found 1 image(s)

COMP: 97: multiplicity: 1 at (30.000,40.000): found 1 image(s)

COMP: 98: multiplicity: 1 at (30.000,50.000): found 1 image(s)

COMP: 99: multiplicity: 1 at (40.000,-50.000): found 1 image(s)

COMP: 100: multiplicity: 1 at (40.000,-40.000): found 1 image(s)

COMP: 101: multiplicity: 1 at (40.000,-30.000): found 1 image(s)

COMP: 102: multiplicity: 1 at (40.000,-20.000): found 1 image(s)

COMP: 103: multiplicity: 1 at (40.000,-10.000): found 1 image(s)

COMP: 104: multiplicity: 1 at (40.000,0.000): found 1 image(s)

COMP: 105: multiplicity: 1 at (40.000,10.000): found 1 image(s)

COMP: 106: multiplicity: 1 at (40.000,20.000): found 1 image(s)

COMP: 107: multiplicity: 1 at (40.000,30.000): found 1 image(s)

COMP: 108: multiplicity: 1 at (40.000,40.000): found 1 image(s)

COMP: 109: multiplicity: 1 at (40.000,50.000): found 1 image(s)

COMP: 110: multiplicity: 1 at (50.000,-50.000): found 1 image(s)

COMP: 111: multiplicity: 1 at (50.000,-40.000): found 1 image(s)

COMP: 112: multiplicity: 1 at (50.000,-30.000): found 1 image(s)

COMP: 113: multiplicity: 1 at (50.000,-20.000): found 1 image(s)

COMP: 114: multiplicity: 1 at (50.000,-10.000): found 1 image(s)

COMP: 115: multiplicity: 1 at (50.000,0.000): found 1 image(s)

COMP: 116: multiplicity: 1 at (50.000,10.000): found 1 image(s)

COMP: 117: multiplicity: 1 at (50.000,20.000): found 1 image(s)

COMP: 118: multiplicity: 1 at (50.000,30.000): found 1 image(s)

COMP: 119: multiplicity: 1 at (50.000,40.000): found 1 image(s)

COMP: 120: multiplicity: 1 at (50.000,50.000): found 1 image(s)

COMP: dist.dat file 

Bye,

Tomás

On Monday, July 13, 2020 at 4:24:54 AM UTC-7, hg.dude.hg wrote:

Dear all,

I am still having a bit of an issue with Lenstool. I have managed to install the latest version of Lenstool (thanks again for the help there, Johan!) and I am now trying to lense a regular grid of point-sources which sit at the same redshift and all have the same magnitude. I want to lense it with an NFW cluster that is simply placed in the middle of this grid, no ellipticity or anything else involved. However, the resulting grid of images is not sensible; the magnitude has not changed at all and the locations have been spread out evenly, which does not make sense since the sources closer to the centre of the cluster should get lensed more strongly. Does anyone know what is happening? I have attached the parameter file (test.par), the input grid (even-grid-small.cat), the read-out parameters (para.out) and the lensed sources (source.dat).

Sincerely,

Dominik Rhiem

To unsubscribe from this group and stop receiving emails from it, send an email to lens...@googlegroups.com.

[Dominik Rhiem]

Hi Tomas, dear all,

that does not quite solve the issue. I have attached the source file that results from following your procedure. The sources are still evenly spaced, which does not make sense since the sources closer to the cluster centre should be deflected more strongly. Also, there is no magnification again. Lastly, albeit that is a more general question: How would I get knowledge about the shear, i.e., if I supply Lenstool with a map of point-sources, the sources should be distorted in their shape - if that is not possible, then how about slightly extended sources, let's say by smoothing the point-sources with a Gaussian kernel. What would this look like in the output?

To state explicitly what I want to do: I want to supply generated maps of point-sources (which might be smoothed with a Gaussian kernel) to Lenstool and calculate how an NFW cluster placed in the middle of the map (with specified mass and concentration) would affect the position, magnitude and shape of the sources; if possible, having the output as a FITS file would be great. How do I do that?

SIncerely,

Dominik

To unsubscribe from this group and stop receiving emails from it, send an email to lenstool+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/lenstool/93fb2df1-d877-4ccd-bb35-30d64d3f2f74o%40googlegroups.com.

[Joseph E. Coleman]

Dominik,

Have you considered simply calculating these things directly from the lens equation?

-Joe

To view this discussion on the web visit https://groups.google.com/d/msgid/lenstool/CAEyWfYnMhD_VSr1GDAu3xvQGjVuWZvJ1-syARPacbw%2BSCk7Xeg%40mail.gmail.com.

[Dominik Rhiem]

Hi Joseph,

Yes, I did, but the shear is somewhat difficult to implement, plus using Lenstool would both improve flexibility in case I want to use different profiles, for example, and also add reproducibility to my results. That is why, if at all possible, I would like to use Lenstool.

Sincerely,

Dominik

To view this discussion on the web visit https://groups.google.com/d/msgid/lenstool/30e05d66-d73e-097f-0984-81349343b317%40utdallas.edu.