You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check out this page containing API doc for the gpflow.conditionals.conditionals._conditional function (screenshot of key section below). As I understand it, this doc is supposed to say (something like):
"If you call the gpflow.conditionals.conditional function and pass in object,InducingVariables,Kernel,object then we'll forward these things to _conditional. Below is the doc for this version of _conditional ..."
"If on the other hand you call the gpflow.conditionals.conditional function and pass in object,object,Kernel,object then we'll forward these things to _conditional. Below is the doc for this version of _conditional ..."
But the docs for both versions of _conditional are the same (it's the second, object,object,Kernel,object, version). Sphinx has found two methods with the same name and pasted the documentation it's found last for both of them.
Check out this page containing API doc for the
gpflow.conditionals.conditionals._conditional
function (screenshot of key section below). As I understand it, this doc is supposed to say (something like):gpflow.conditionals.conditional
function and pass inobject,InducingVariables,Kernel,object
then we'll forward these things to_conditional
. Below is the doc for this version of_conditional
..."gpflow.conditionals.conditional
function and pass inobject,object,Kernel,object
then we'll forward these things to_conditional
. Below is the doc for this version of_conditional
..."But the docs for both versions of
_conditional
are the same (it's the second,object,object,Kernel,object
, version). Sphinx has found two methods with the same name and pasted the documentation it's found last for both of them.The doc for the 'InducingVariables' version is never shown (starts "Single-output GP conditional...")
PS. The
_sample_conditional
function is implemented differently, and on the surface at least, seems to generate documentation that makes more sense...The text was updated successfully, but these errors were encountered: