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
Hello,
I am observing that when I create a deepxde.data.pde_operator.PDEOperator with num_function=1 and I had previously specified a PDE with, as an example, num_domain=100, num_boundary=20, num_initial=50, if I look into the pde_operator.train_bc[0] the size is correctly [50+20,N_sensors] but, instead, pde_operator.train_x[0] will have size [240,N_sensors], being 240=100+2*(20+50), i.e. twice the number of bc and ic points. Moreover, all of these are passed in the forward pass and PDE evaluation. What am I missing? Why are there twice the initial and boundary points?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I am observing that when I create a deepxde.data.pde_operator.PDEOperator with num_function=1 and I had previously specified a PDE with, as an example, num_domain=100, num_boundary=20, num_initial=50, if I look into the pde_operator.train_bc[0] the size is correctly [50+20,N_sensors] but, instead, pde_operator.train_x[0] will have size [240,N_sensors], being 240=100+2*(20+50), i.e. twice the number of bc and ic points. Moreover, all of these are passed in the forward pass and PDE evaluation. What am I missing? Why are there twice the initial and boundary points?
Beta Was this translation helpful? Give feedback.
All reactions