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

Inconsistent attribute and method names #91

Open
lil1n opened this issue Jan 16, 2024 · 1 comment
Open

Inconsistent attribute and method names #91

lil1n opened this issue Jan 16, 2024 · 1 comment
Labels
Type: Bug Something isn't working

Comments

@lil1n
Copy link

lil1n commented Jan 16, 2024

Several issues were faced while trying out counterfit.

Upon starting counterfit and providing the command new -n test, an error 'AttributeError' was encountered.

  • new.py referenced an attribute named targets_path in config.py but config.py does not seem to have an attribute named targets_path declared or defined
  • This was resolved by adding a line to declare an attribute named targets_path with the path directed to the "targets" directory in config.py

The above issue appears to be the same issue as the first bullet point in issue #82

After resolving this issue, several other issues of similar nature were encountered:

  • new.py referenced add_targets() in state.py but state.py do not any method named add_targets() declared or defined
  • new.py referenced load_targets() in state.py but state.py do not any method named load_targets() declared or defined

After resolving the above issues, another exception named 'TypeError' was encountered with the message: 'NoneType' object is not callable. This issue was traced back to be from line 77 of new.py.

Other than the new command, the command predict -i range(10) (as mentioned in DEMO1-satellite.md) also does not produce the same output as documented. This appears to be the same issue as the second bullet point in issue #82

@lil1n lil1n added the Type: Bug Something isn't working label Jan 16, 2024
@robsanity
Copy link

Hey sorry to bother you, did you fix in anyway the TypeError issue? i'm at exactly your same point :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants