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

testing job checks #198

Open
wants to merge 19 commits into
base: main
Choose a base branch
from
Open

testing job checks #198

wants to merge 19 commits into from

Conversation

SallyElHajjar
Copy link
Collaborator

testing job checks

Copy link
Collaborator

@Katsutoshii Katsutoshii left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

At a high level, a lot of this seems like experimental code that shouldn't be checked in. Can we start by checking in the dataset changes only?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's remove the _copy notebooks unless they are generally useful for future work. If we do keep them, give them a more meaningful name.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okkay

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Instead of commenting out the entire file, can you put an early return on each of the failing tests?

# Geospatial constants
MAP_HEIGHT = 200
MAP_WIDTH = 200
# Geospatial constants should be 200
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we check this in? I thought this was for experimental purposes only.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

was thinking about that, but thought if I keep 200 with the new model architecture i will get the memory error again because the model will not be built. I can try do that

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should add this to the gitignore.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ohh i forgot to delete it. will remove it because we are no longer using it

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

Successfully merging this pull request may close these issues.

2 participants