Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

t.pytorch.predict: various issues with reference data and model config #59

Open
2 of 3 tasks
ninsbl opened this issue Aug 30, 2024 · 2 comments
Open
2 of 3 tasks
Assignees
Labels
enhancement New feature or request

Comments

@ninsbl
Copy link
Collaborator

ninsbl commented Aug 30, 2024

Investigate:

  • why does positive offset result in maps not found (likely due to extraction of start and end times (start time is for some reason end time of the first input)
  • make sure that the order of reference data is applied as expected (negative offset means reference maps represent earlier points in time)
  • how to handle binary clasification (rounding (0.5 threshold) may be too restrictive, implement support for other threshold? Use scaling?) esp. with inverted classes (0: presence 1: absence)
@ninsbl ninsbl added the enhancement New feature or request label Aug 30, 2024
@ninsbl ninsbl self-assigned this Aug 30, 2024
@ninsbl
Copy link
Collaborator Author

ninsbl commented Sep 3, 2024

See: #61 adds argmax transformation for binary clasification results (used by NORCE algorithm).

@ninsbl
Copy link
Collaborator Author

ninsbl commented Sep 3, 2024

BTW. When a negative reference is used it makes sense that the start_time of the resulting map is the end_time of the previous (e.g. offset=-1) granule as that is the time window covered...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant