ESM has published a new model ESM-1b. We can't just replace the old model with the new model and change the protocol output, however we need some way to allow the user to "upgrade" to newer models/weights for such cases. Two apparent solutions are a new protocol esm_1b which has a shared implementation with esm or a field model: esm-1b which allows to select model weights. Drawback for the first is that we might get an unwieldy number of embed protocols and classes, while the second might break if the model e.g. changes the embedding dimensionality.
ESM has published a new model ESM-1b. We can't just replace the old model with the new model and change the protocol output, however we need some way to allow the user to "upgrade" to newer models/weights for such cases. Two apparent solutions are a new protocol
esm_1b
which has a shared implementation withesm
or a fieldmodel: esm-1b
which allows to select model weights. Drawback for the first is that we might get an unwieldy number of embed protocols and classes, while the second might break if the model e.g. changes the embedding dimensionality.