Ivan Ruiz Manuel
Ivan Ruiz Manuel
Hello @euronion ! Sure, here is the cutout command (had to reconstruct it because of snakemake, but it's roughly like this): ```python cutout = atlite.Cutout( path="output/test.nc", module=["era5"], x=slice(-9.497466600999928, -6.205947224999932), y=slice(36.96588776200008,...
@fneum ok, so basically: only use `per_unit` to avoid trouble :+1: I've been following this and my workflows work well (as far as I've checked)
If you are looking at python solutions, consider [dedupe](https://github.com/dedupeio/dedupe). I've yet to use it myself, but it looks quite mature.
Here are some other issues that might be related to this one: - https://github.com/snakemake/snakemake/issues/2962 - https://github.com/snakemake/snakemake/issues/3024 - https://github.com/snakemake/snakemake/issues/3254 Seems like `ancient` is too temperamental...
@Hocnonsense thanks for looking into it! I see something similar when running `snakemake -np`. The problem is that this behaviour is not respected during our CI test. I'll explain in...
@Hocnonsense I managed to replicate this issue locally! Here are the steps (assuming you already have `snakemake` installed): ```shell git clone [email protected]:calliope-project/module_hydropower.git # clone our repo git checkout add-euro-calliope-methods #...
I repeated the steps above, but using `snakemake -np`. The command shows that `ancient` is not respected: ``` host: fedora Building DAG of jobs... Job stats: job count -------------------------------------------------- -------...
I assume you are looking into the `tests/integration/resources` folder, correct? Perhaps a bit more context might help: - The main workflow (`module_hydropower/workflow`) was built with modularisation in mind. It is...
Ahhhh, got it. I added the second file (`"results/by_shape_id/hydro_run_of_river_cf.parquet"`) to the `all` rule recently. However, both `results/by_shape_id/hydro_dam_cf.parquet` and `results/by_shape_id/hydro_run_of_river_cf.parquet` are produced by the same rule, and have the same inputs....
This smells like some condition messing with the DAG in a super specific case. The names of the called rules are all different, and all the files in the 'wrong'...