Triming lens population

[rpoleski]

I'm interested in generating binary lens events with both components in mass range 0.08-0.15 M_Sun. In order to make PopSyCLE more efficient in that task, I think I should be able to remove stars from the population of candidate lenses. Can that be easily done? I can imagine there could be option for that while the population is created or one could trim the population (.h5 file).

[nsabrams]

While unfortunately you can't remove them before calc_events as it is now, you can remove them before refine_events and refine_binary_events. We need to keep everything in in the calc_events stage since any object in the .h5 file could be a lens or a source. However once you have the events, you can take the .fits file after calc_events and trim on lenses of interest to you. Let me know if you want a command to make that trim!

[jluastro]

It would be a little tricky because if you remove the stars outside that mass range, you lose them as sources. But, in principle, you could insert a post processing step after perform_pop_syn but before calc_events where you loop through the patches in the hdf5 file and remove everything inside some distance (say 4kpc) that isn’t in your desired mass range. I’m not 100% sure how much more efficient this would actually be since the majority of the stars are in the bulge.On Feb 10, 2026, at 11:23 AM, Radek Poleski ***@***.***> wrote:rpoleski created an issue (MovingUniverseLab/PopSyCLE#76) I'm interested in generating binary lens events with both components in mass range 0.08-0.15 M_Sun. In order to make PopSyCLE more efficient in that task, I think I should be able to remove stars from the population of candidate lenses. Can that be easily done? I can imagine there could be option for that while the population is created or one could trim the population (.h5 file). —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>