I hereby claim:
- I am noorvir on github.
- I am noorvir (https://keybase.io/noorvir) on keybase.
- I have a public key ASBq_QwtJuQyvEFwjizF-Ty9lAm-6bycSjNG7ARRoxXGqAo
To claim this, I am signing this object:
| <div style={{ display: 'flex', height: '100vh', flexGrow: 1, flexDirection: 'column' }}> | |
| <div | |
| style={{ | |
| display: 'flex', | |
| height: '100%', | |
| flexDirection: 'column', | |
| backgroundColor: 'red', | |
| }} | |
| > | |
| <div style={{ backgroundColor: 'yellow' }}>Element above</div> |
I hereby claim:
To claim this, I am signing this object:
| """ | |
| You sometimes need to load weights from a checkpoint file to a new/different TensorFlow architecture where the | |
| variable names for the layers are different (see example below). For instance, you might need to load the first | |
| few layers of AlexNet pre-trained on ImageNet to your custom model which for some reason has a different naming | |
| convention. | |
| I couldn't find any convinient piece of code to do this; this gist is aimed at addressing this. | |
| Example mapping: |
| """ | |
| Inspired by: | |
| https://blog.metaflow.fr/tensorflow-a-proposal-of-good-practices-for-files-folders-and-models-architecture-f23171501ae3 | |
| Recommended guidelines for child classes: | |
| 1) Abstract away common/repeated functionality that remains the same for multiple models whose use is obvious to the | |
| reader. | |
| 2) Do not abstract essential parts of the model (such as loss terms, optimisers, layer names). Name these variables |