[Question] question title

[jvoids]

❓ Question

Hi guys.
In case of custom FeatureExtractor is it possible to teach some parts of it controlled but in terms of general Algorithm flow. I.e there's exact specific behavior is expected for the feature extractor to perform. So that it should not be trained as a black box along the input - extractor - actor flow but as a white box.

E.g. having environment that returns extra data within info result from a step() call (as it is not the observation it self)

obs, reward, terminated, info, done = env.step(action)

So that is it possible to organize feature_extractor some how to use specific data from the info as a target at back propagation phase.

Or should such logic be trained just separately and used exclusively at inference mode within feature_extractor

Thank you!

Checklist

• I have checked that there is no similar issue in the repo
• I have read the documentation
• If code there is, it is minimal and working
• If code there is, it is formatted using the markdown code blocks for both code and stack traces.

[araffin]

Hello,
it is currently not possible, you will need to have a custom version of SB3.

[jvoids]

Hello @araffin. thanks for the answer.
Could you guide please

• What would be the best place(s) to handle this
• Is it really codebase fork needed or would it be enough just to extend/override/rework some classes using standard module release?