Burn area product is out of date

[ChangpeiHe]

MCD64A1 burned area product is decommissioned at the end of 2022. I want to use this tool to extract global fire events in 2023 and 2024.
Looking forward to your reply!
@Ckster @maxwellCcook

[admahood]

Hey there,
I believe the current firedpy algorithm uses the more current MCD64 product that is still being produced. Are using docker and pulling from the old dockerhub repo (earthlab/firedpy)? if so, you'll want to switch to the earthlabcu/firedpy dockerhub account.

[admahood]

Oooh I see what's happening. the updated version of the algorithm is not on the main branch. It's on the v2.0 branch. @Ckster is that branch ready to be the main branch yet?

[ChangpeiHe]

Thanks! So, can I use the code on the v2.0 branch? git checkout v2.0

[admahood]

We just merged 2.0 into main, so you should be all set using main now. Let me know if there are any problems

…

On Fri, Oct 11, 2024, 8:29 PM ChangpeiHe ***@***.***> wrote: Thanks! So, can I use the code on the v2.0 branch? git checkout v2.0 — Reply to this email directly, view it on GitHub <#91 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABXI3P2VT6JMPVO5RRUGCLDZ3CCQXAVCNFSM6AAAAABPYYG5E2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBYGMYTCNZUGA> . You are receiving this because you commented.Message ID: ***@***.***>

[ChangpeiHe]

It seems lacking "setup.py".

[ChangpeiHe]

Hi, @admahood. Are the parameters ecoregion_type, ecoregion_level, and landcover_type required?

[ChangpeiHe]

Without "setup.py", I cannot install firedpy successfully. @admahood

[Ckster]

We are moving away from using setup.py. I would suggest using the environment.yml file create the conda environment necessary for running firedpy and then simply call python bin/firedpy.py. Alternatively, you can run the new Docker container. I will update the README shortly to show how to do this

[Ckster]

The README is updated. If you cannot run from Docker then simply create the environment from the environment.yml file, activate the firedpy env, and run 'python bin/firedpy.py'

[ChangpeiHe]

Thanks, @Ckster. I try to run "python ./bin/firedpy.py -spatial 5 -temporal 11 -aoi h10v04 -out_dir /public/home/hechangpei/firedpy/proj/ -eco_region_type world -file fired -start_year 2023 -end_year 2024
". However, an error occurred as "Traceback (most recent call last):
File "/public/home/hechangpei/firedpy/./bin/firedpy.py", line 10, in
from src.data_classes import EcoRegion, BurnData, LandCover
ModuleNotFoundError: No module named 'src'".

[Ckster]

Sorry, forgot to add you will have to add the project directory to your PYTHONPATH. From the project directory run export PYTHONPATH=$(pwd):$PYTHONPATH

[Ckster]

@ChangpeiHe the PYTHONPATH should be automatically set now, just pull the most recent changes from main. Let me know how it works, thanks.

[ChangpeiHe]

@Ckster It works, thanks! I'm sorry for not replying to you promptly. I‘m trying to run firedpy on the global scale.