Issues: IN-CORE/pyincore
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Remove Less than two hours of work, requiring only email communication
InsecureIncoreClient
and related tests and global variables
1storypoint
#581
opened May 23, 2024 by
Rashmil-1999
Add Google Analytics to pyincore documentation
3storypoints
Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem
#547
opened Apr 23, 2024 by
ywkim312
Refactoring the population dislocation post-processing joining with building inventory
1storypoint
Less than two hours of work, requiring only email communication
#534
opened Apr 4, 2024 by
longshuicy
Surge-wave fragilities not sensitive to elevation
2storypoints
Between 2-6 hours of work, requiring email and/or a brief meeting
#533
opened Apr 4, 2024 by
longshuicy
Investigate population dislocation shows more dislocated households than people
#532
opened Apr 4, 2024 by
longshuicy
Some service class method documentation is not showing in the manual pages
2storypoints
Between 2-6 hours of work, requiring email and/or a brief meeting
#518
opened Mar 8, 2024 by
navarroc
Raster io doesn't work with multiprocessor
3storypoints
Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem
bug
Something isn't working
#512
opened Mar 6, 2024 by
longshuicy
Retrofit cost analysis
3storypoints
Between 7-15 hours of work, requiring back and forth communications to clarify a complex problem
science
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.