extra notes regarding dependencies (need to use/add urllib3==1.26.7)

[BrunoArsioli]

I would like to suggest to add extra notes regarding dependencies in case someone uses the latest Python3.9 version (Python 3.9.17)

Note: need to use urllib3==1.26.7 Currently, this information is missing from documentation)

Draft.V2 Extra notes:

Create a new environment to install gPhoton and its dependencies

conda create -n gphoton_env python=3.9

conda activate gphoton_env 

Inside your gphoton environment, check for the Python version

python --version 

It should be: Python 3.9.17

Now, proceed to install all dependencies before installing gPhoton

pip install numpy requests scipy astropy future pandas urllib3==1.26.7

pip install gPhoton

(maybe, you will need to use this commandf to force installation in your gphoton_env (note: update the local user folder).

pip install --target=/Users/<YOU_LOCAL_USER_FOLDER>/anaconda3/envs/gphoton_env/lib/python3.9/site-packages gPhoton --upgrade

run python import gPhoton

to check the installation was succesfull.

[cmillion]

Great! Thanks for taking the time to do this!

However, you may also be interested to know that we now prefer (and suggest that others use) the new and improved gPhoton2: https://github.com/millionconcepts/gphoton2

[BrunoArsioli]

Dear Chase, Thank you for your reply! I will try gPhoton2 as well. I am still reading the documentation, and I am trying to understand if there is an automated way to estimate the radius parameter. I used 2.5" for point sources (testing with z>2 quasars) and got NUVmag fluxes close to the values reported in GalexDR6+7 .

I would appreciate your thoughts about that, Best regards, Bruno Arsioli

Em ter., 29 de ago. de 2023 às 13:50, Chase Million < @.***> escreveu:

Great! Thanks for taking the time to do this!

However, you may also be interested to know that we now prefer (and suggest that others use) the new and improved gPhoton2: https://github.com/millionconcepts/gphoton2

— Reply to this email directly, view it on GitHub https://github.com/cmillion/gPhoton/pull/290#issuecomment-1697382990, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANUDYJRZR4UWJUDCS6UCVATXXXQPXANCNFSM6AAAAAA4C3ZFKI . You are receiving this because you authored the thread.Message ID: @.***>

[cmillion]

By "estimate the radius parameter," do you mean something like "find the optimum photometric extraction radius"? There is not an automated mechanism, although we're adding improvements to the aperture photometry of extended sources in gPhoton2. For point sources, I suggest r>17" in GALEX data, and basically go as big as you can go without hitting other stars. If you mostly care about absolute magnitudes, you'll want to apply an aperture correction. (IMO, the one implemented in the apcorrect1 function here is the best available.) But if you are interested in temporal variation, I recommend skipping the aperture correction (at least when computing deltas).

[BrunoArsioli]

About the radius parameter, that is what I meant: to "find the optimum photometric extraction radius" to extract absolute magnitudes. I will look into apcorrect1 for the aperture correction, using gPhoton2. Thank you!

[BrunoArsioli]

Dear Chase, I also found about the glcat, at ( https://www.millionconcepts.com/projects.html ). Do you know the status of this UV catalog? If you have information about it (e.g. an estimate for the release date) I would appreciate hearing from you.

I have ongoing works which explore multifrequency data associated with quasars, and glcat is key (carrying information about the accretion disk). Cheers! Bruno Arsioli

Em qua., 30 de ago. de 2023 às 13:39, Chase Million < @.***> escreveu:

By "estimate the radius parameter," do you mean something like "find the optimum photometric extraction radius"? There is not an automated mechanism, although we're adding improvements to the aperture photometry of extended sources in gPhoton2. For point sources, I suggest r>17" in GALEX data, and basically go as big as you can go without hitting other stars. If you mostly care about absolute magnitudes, you'll want to apply an aperture correction. (IMO, the one implemented in the apcorrect1 function here https://github.com/cmillion/gPhoton/blob/master/gPhoton/galextools.py is the best available.) But if you are interested in temporal variation, I recommend skipping the aperture correction (at least when computing deltas).

— Reply to this email directly, view it on GitHub https://github.com/cmillion/gPhoton/pull/290#issuecomment-1699094093, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANUDYJSHVMMODUEYQUWCZ4LXX4YB3ANCNFSM6AAAAAA4C3ZFKI . You are receiving this because you authored the thread.Message ID: @.***>

[cmillion]

Yup. The working repository is here, although it's mostly stubs of code from various experiments that we have run to try to extract the most value out of the GALEX data and won't be useful to you. I'm targeting the first release of this catalog by the end of summer. The major innovation in GLCAT v1 is that it will do a better job identifying and measuring extended sources and flagging data within extended sources, and it will also perform identical aperture photometry across both bands so that "significant nondetections" can be easily distinguished / leveraged vs. non-observations. It will not include data from the scan mode or CAUSE phase observations of e.g. the galactic plane and Magellanic clouds.

Why don't you follow up with me by email and I'll see if I can get you the specific data that you need more quickly.