hi, @deena-b i get the same issue, have you solved it ?
looks like tranformerXL is cpu bound - my cpu utilization is higher than the gpu utilization. Is that also your experience @sgugger
Some handy pytest extensions I have just discovered (click on the links for the full description, installation info).
-
Automatically rerun failed tests on source modification
pytest -f -
pytest --picked -
improved look-n-feel: add progress-bar and show failing tests immediately
I’ve been using this last plugin today a lot in various projects and I love it!
2 Likes
Breaking change
Did you all notice how we had ImageItemList but TextList and TabularList? Well not anymore. In master and v1.0.46 ImageItemList becomes ImageList.
2 Likes
I could use some CS algorithm help here.
Needing help with a search algorithm to find the shortest sequence of items that lead to a certain outcome (failed test in this case). Please see this post.
Thank you.
@sgugger has just released fastai-1.0.46, list of changes.
Also there was a bit of a mess up with 1.0.44 vs 1.0.45, which are really the same release. So I removed 1.0.45 from pypi/conda and there is 1.0.44 instead for those who want it. But, of course, 1.0.46 is out.
ImageItemList was renamed to ImageList for consistency and at the same time MixedItemList was introduced?
Looking forward to try the new TextClassificationInterpretation function!
That is correct. MixedItemList is a mix of ItemLists (and experimental for now), so there is no inconsistency here.
Hey, Jeremy –
Looks like the keyboard shortcut to bring up the list of Discourse shortcuts has been changed to shift-/ instead of just /, at least on Chrome on Linux. If this is universal, could you please edit your initial post to reflect this? Thanks!
Breaking change
The API of the Callback has been slightly changed to be more flexible and (hopefully) less opaque. You now can return a dictionary that will update the state of the CallbackHandler so
- instead of returning
last_lossinon_backward_begin, you can return{"last_loss": my_value}in any event of any callback - you can change inner stats (for instance the number of the epoch displayed when resuming training)
- in a custom metric written as a callback, instead of having to give
last_metric=my_valueinon_epoch_end, the new way of doing it is:
def on_epoch_end(self, last_metrics, **kwargs):
return {'last_metrics': last_metrics + [my_value]}
The CallbackHandler will throw an error in case of typo (so you can’t add attributes).
The old return True in some events to stop training or skip the step are now replaced by the following flags in the state:
-
skip_step: to skip the next optimizer step -
skip_zero: to skip the next grad zeroing -
stop_epoch: to stop the current epoch -
stop_training: to stop the training at the end of the current epoch
For instance, in the old LR Finder Callback the part to stop after going too high in loss was:
def on_batch_end(self, iteration:int, smooth_loss:TensorOrNumber, **kwargs:Any)->None:
"Determine if loss has runaway and we should stop."
if iteration==0 or smooth_loss < self.best_loss: self.best_loss = smooth_loss
self.opt.lr = self.sched.step()
if self.sched.is_done or (self.stop_div and (smooth_loss > 4*self.best_loss or torch.isnan(smooth_loss))):
#We use the smoothed loss to decide on the stopping since it's less shaky.
self.stop=True
return True
def on_epoch_end(self, **kwargs:Any)->None:
"Tell Learner if we need to stop."
return self.stop
and the new one is
def on_batch_end(self, iteration:int, smooth_loss:TensorOrNumber, **kwargs:Any)->None:
"Determine if loss has runaway and we should stop."
if iteration==0 or smooth_loss < self.best_loss: self.best_loss = smooth_loss
self.opt.lr = self.sched.step()
if self.sched.is_done or (self.stop_div and (smooth_loss > 4*self.best_loss or torch.isnan(smooth_loss))):
#We use the smoothed loss to decide on the stopping since it's less shaky.
return {'stop_epoch': True, 'stop_training': True}
3 Likes
So now we need to either return nothing or a dict of valid key:value pairs that can be handled. Thanks for the update
1 Like
Under development but should work as long as you are on master for fastai and fastprogress, resume training from where it was automatically.
If AWS shuts down your spot instance, the marvelous fastec2 will wait for them to be available again and it would be nice to restart training from when you last where (at least the last completed epoch). This is now possible with two callbacks! Just pass:
callback_fns = [TrackEpochCallback, partial(SaveModelCallback, every='epoch')]
in you call to fit, fit_one_cycle or with a custom scheduler and it should work. Interrupted trainings will start back from the last completed epoch!
Note that to force the training to go back from start, you need to remove the epoch file that will pops out in your model_dir because that’s where we keep track of the progress made.
4 Likes
Breaking change (this is all @radek fault, so don’t be mad at me ^^)
create_cnn won’t exist anymore in v1.0.47 and later on, it will be replaced by cnn_learner for consistency with all the other convenience functions that return a Learner. Updating the docs, will do the course and the deployment kits once the release is out.
3 Likes
And since it’s I’m going to break things day:
- random_split_by_pct becomes split_by_rand_pct
- no_split becomes split_none
so that all split methods begin with split_
Again, blame @radek 
1 Like
A product of hard work of @ashaw, @Benudek and yours humbly is now ready for your enjoyment (project thread).
-
Each API that’s tested in the fastai test suite now has a test entry in the documentation (about 200+ of those):
e.g. go here https://docs.fast.ai/basic_train.html#Learner.save and click on
[test], and you will get:
So in addition to tutorials and code snippets in the docs, you can now also look at how the API is tested, including expected results and expected failures.
-
Each API that isn’t yet tested invites you to do so:
e.g. go here https://docs.fast.ai/basic_train.html#Recorder.plot_metrics and click on
[test], and you will get:
- And similar to
show_docyou can also doshow_testfrom your notebook once you install the new fastai 1.0.47 when it’s released, or using git master now:
Same as show_doc arguments, except it’s show_test.
What makes it all possible is a special this_tests call in every test. https://docs.fast.ai/dev/test.html#test-registry
Bottom line, if you click on [test] or you run show_test and you get ‘No tests found’ - please contribute some!
10 Likes
I hope this is the right place to post. I have a suggestion for improving the ClassificationInterpretation class. Right now there is a very useful feature, most_confused, that shows you the classes that your model is predicting incorrectly. There is also plot_top_losses, also very useful, to visualize the cases the model had the highest loss on. However, if you discover the model is mixing up two classes that it shouldn’t be, I don’t believe there is any way to visualize the data for just those classes.
For example if we have a fruit classifier, maybe most_confused shows something like this…
interp.most_confused(min_val=2)
[('pear', 'apple', 4),
('papaya', 'mango', 3),
('watermelon', 'apple', 3),
('apple', 'pear', 2)]
These are all reasonable except for watermelon/apple which should be very easy to distinguish so I’d think of this as a good place to take a closer look, but I don’t think there’s a way to do it easily.
Would this be useful enough to consider as a feature, or would it add bloat? Would it be best to add it’s own function? Or would it be better to add two additional parameters to plot_top_losses (pred_class=None, actual_class=None) to act as a filter. I’d be happy to do it and submit a PR if people would find it useful, but I’ve never submitted a PR so would probably need guidance on the implementation.
Thanks!
-Rob
1 Like