Correct initialization for a CL Generic Scenaio + Baselines (Avalanche) #906
Unanswered
valevalerio
asked this question in
Q&A
Replies: 1 comment
-
Hi @valevalerio! Thanks for your question. Here's some feedback.
Hope this helps! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Dear all,
I hope to find you well.
I am approaching the CL framework implemented in Avalanche.
However I am not totally sure about many aspect and details of my sperimentation settings.
I have a dataset for a regression problem: 1 input and 5 outputs let’s say. Those patterns have clearly a change in the distributions (both in the input and output) and i want to shape the problem as a multitask problem differenciating the tasks/kinds of experiences that I have identified in the dataset.
Scenario Initialization
Let’s say I have 100 and 200 entries for 2 different experiences (they all have 1in 5out) and want to use 50% as validation test.
1. Is this following code for the generic CL Scenario semantically correct?
(Dummy initialization of the tensors)
The initialization of the scenario is
2. Are this the right setting implementation of my problem?
(with this setting and the naive vanilla strategy, I am obtaining an evaluation for each experience in each task, that sounds good. How ever I am not totally sure about if I want different Tasks, or different experiences)
Baseline Initialization
I would like to use Avalanche and try the baselines to start with.
I’m going for the Naive/Finetuning by continuing back-prop.
Assuming this is the right setting for the finetuning baseline (so without any smart CL strategy applied, like batch learning: No plugins)
3. What is the best way to try the JointTraining/Offline baseline (train the model with all the data) and evaluating it in the same test settings?
Could it be achieved simply by changing the scenario (so stacking the different experiences together) while keeping the same (reset) model, right?
4. There is an easy way to specify explicitly (automatically by Avalanche) the task label as input for the model?
Thanks in advance
Beta Was this translation helpful? Give feedback.
All reactions