-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add CNP #30
base: main
Are you sure you want to change the base?
Add CNP #30
Conversation
A standard CNP model contains 3 parts:
For now I have considered the aggregator part to be included in the encoder. This is because the aggregator can be very different for different tasks. That said, I can include some common aggregators (regression, classification etc) and give an option to pass in a parameter to use one of the common aggregators. If this is being done, the exact function definition has to be discussed. Any thoughts on this? @veds12 |
Codecov ReportBase: 0.00% // Head: 0.00% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## main #30 +/- ##
======================================
Coverage 0.00% 0.00%
======================================
Files 5 11 +6
Lines 95 295 +200
======================================
- Misses 95 295 +200
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@AnirudhM1 a few comments:
|
@AnirudhM1 any updates on this? |
@veds12 Sorry for the delay
I have added a utility class which has functions for some common aggregation algorithms.
I have added docstrings to the main code (cnp.py). The above code in the description of this PR is just an example of how to use the interface.
Can you please elaborate a bit further on this? |
I mean having a separate file from which different architectures (MLP, RNNs, CNNs) can be loaded. |
closes #25
Example:
cc: @veds12