Hi, Everybody! I'm having a little trouble with getting pressure when using HydroMethod=6. For instance,
ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", line 233, in __getitem__ f = self._determine_fields([key])[0] File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000. while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined? Thanks! d. -- -- Sent from a computer. _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py --
probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins
Hi, Everybody!
I'm having a little trouble with getting pressure when using HydroMethod=6. For instance,
ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", line 233, in __getitem__ f = self._determine_fields([key])[0] File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000.
while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined?
Thanks! d.
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the
thermal_energy is computed based on HydroMethod=4,6, but there's no
pressure field. Which in principle is fine, since the computation in
yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that
instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins
wrote: Hi, Everybody!
I'm having a little trouble with getting pressure when using HydroMethod=6. For instance,
ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 233, in __getitem__ f = self._determine_fields([key])[0] File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000.
while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined?
Thanks! d.
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer. _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Hi Dave,
The pressure field is probably coming from the definition in
yt/fields/fluid_fields.py. If it doesn't show up for your dataset, it's
likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data that
uses HydroMethod 4 or 6. Do you happen to have a small one I could play
with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins
wrote: Hi, Everybody!
I'm having a little trouble with getting pressure when using HydroMethod=6. For instance,
ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 233, in __getitem__ f = self._determine_fields([key])[0] File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000.
while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined?
Thanks! d.
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Hi, Nathan--
I do, what's the easiest way to share a dataset?
d.
On Tue, May 5, 2015 at 1:49 PM, Nathan Goldbaum
Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset, it's likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data that uses HydroMethod 4 or 6. Do you happen to have a small one I could play with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
wrote: Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins
wrote: Hi, Everybody!
I'm having a little trouble with getting pressure when using HydroMethod=6. For instance,
> ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 233, in __getitem__ f = self._determine_fields([key])[0] File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000.
while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined?
Thanks! d.
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer. _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
On Tue, May 5, 2015 at 10:53 AM, David Collins
Hi, Nathan--
I do, what's the easiest way to share a dataset? d.
Let's use the curldrop the matt and kacper have set up at NCSA. Use the following command: curl -T file https://labs.nationaldataservice.org/upload/ where file is the path to a tarball containing your test dataset. It should spit out a download link once it's done uploading, which you can reply with here.
On Tue, May 5, 2015 at 1:49 PM, Nathan Goldbaum
wrote: Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset, it's likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data that uses HydroMethod 4 or 6. Do you happen to have a small one I could play with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
wrote: Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins
wrote: Hi, Everybody!
I'm having a little trouble with getting pressure when using HydroMethod=6. For instance,
>> ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 233, in __getitem__ f = self._determine_fields([key])[0] File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000.
while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined?
Thanks! d.
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
On Tue, May 5, 2015 at 11:10 AM, Nathan Goldbaum
On Tue, May 5, 2015 at 10:53 AM, David Collins
wrote: Hi, Nathan--
I do, what's the easiest way to share a dataset? d.
Let's use the curldrop the matt and kacper have set up at NCSA.
Use the following command:
curl -T file https://labs.nationaldataservice.org/upload/
Kacper informed me off-list at this should be http, not https. Sorry for the confusion!
where file is the path to a tarball containing your test dataset. It should spit out a download link once it's done uploading, which you can reply with here.
On Tue, May 5, 2015 at 1:49 PM, Nathan Goldbaum
wrote: Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset, it's likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data that uses HydroMethod 4 or 6. Do you happen to have a small one I could play with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
wrote: Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins
wrote: Hi, Everybody!
I'm having a little trouble with getting pressure when using HydroMethod=6. For instance, >>> ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 233, in __getitem__ f = self._determine_fields([key])[0] File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000.
while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined?
Thanks! d.
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
You can append ("gas", "pressure") to _show_field_errors on
FieldInfoContainer to raise whatever fails.
On Tue, May 5, 2015, 12:49 PM Nathan Goldbaum
Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset, it's likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data that uses HydroMethod 4 or 6. Do you happen to have a small one I could play with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
wrote: Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins
wrote: Hi, Everybody!
I'm having a little trouble with getting pressure when using HydroMethod=6. For instance,
> ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 233, in __getitem__ f = self._determine_fields([key])[0] File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000.
while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined?
Thanks! d.
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
What instance of FieldInfoContainer should I attach that to?
On Tue, May 5, 2015 at 1:54 PM, Matthew Turk
You can append ("gas", "pressure") to _show_field_errors on FieldInfoContainer to raise whatever fails.
On Tue, May 5, 2015, 12:49 PM Nathan Goldbaum
wrote: Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset, it's likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data that uses HydroMethod 4 or 6. Do you happen to have a small one I could play with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
wrote: Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins
wrote: Hi, Everybody!
I'm having a little trouble with getting pressure when using HydroMethod=6. For instance,
>> ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 233, in __getitem__ f = self._determine_fields([key])[0] File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000.
while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined?
Thanks! d.
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer. _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Hi Dave,
Sorry for the abruptness! If you're already editing the source code,
just toss it on to the field_info_container.py definition. Stick it
in the __init__ method like so:
self._show_field_errors = [("gas","pressure")]
On Tue, May 5, 2015 at 12:58 PM, David Collins
What instance of FieldInfoContainer should I attach that to?
On Tue, May 5, 2015 at 1:54 PM, Matthew Turk
wrote: You can append ("gas", "pressure") to _show_field_errors on FieldInfoContainer to raise whatever fails.
On Tue, May 5, 2015, 12:49 PM Nathan Goldbaum
wrote: Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset, it's likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data that uses HydroMethod 4 or 6. Do you happen to have a small one I could play with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
wrote: Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins
wrote: Hi, Everybody!
I'm having a little trouble with getting pressure when using HydroMethod=6. For instance, >>> ds0.all_data()['pressure']
Traceback (most recent call last): File "<stdin>", line 1, in <module> File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", line 233, in __getitem__ f = self._determine_fields([key])[0] File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('all', 'pressure')' in data0000.
while this works for a run with HydroMethod = 0. Could someone give me the nickel tour of hydro method impacts setting of variables, and where I should look to make sure pressure is defined?
Thanks! d.
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
I often debug these issues by inserting a breakpoint at line 315 in
yt/fields/field_info_container.py:
https://bitbucket.org/yt_analysis/yt/src/d683286da1623d41e858dc37409910b704f...
This is where we handle any exceptions that a derived field raises during
field detection. If a field raises an error here, the field fails field
detection and is removed from consideration. If other fields depend on
this one, then they won't show up either.
On Tue, May 5, 2015 at 11:03 AM, Matthew Turk
Hi Dave,
Sorry for the abruptness! If you're already editing the source code, just toss it on to the field_info_container.py definition. Stick it in the __init__ method like so:
self._show_field_errors = [("gas","pressure")]
What instance of FieldInfoContainer should I attach that to?
On Tue, May 5, 2015 at 1:54 PM, Matthew Turk
wrote: You can append ("gas", "pressure") to _show_field_errors on FieldInfoContainer to raise whatever fails.
On Tue, May 5, 2015, 12:49 PM Nathan Goldbaum
wrote: Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset,
it's
likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data
uses HydroMethod 4 or 6. Do you happen to have a small one I could
with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
wrote:
Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no
On Tue, May 5, 2015 at 12:58 PM, David Collins
wrote: that play pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins <
dcollins4096@gmail.com>
wrote: > Hi, Everybody! > > I'm having a little trouble with getting pressure when using > HydroMethod=6. > For instance, >>>> ds0.all_data()['pressure'] > > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", > line 233, in __getitem__ > f = self._determine_fields([key])[0] > File > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", > line 489, in _determine_fields > finfo = self.ds._get_field_info("unknown", fname) > File > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", > line 482, in _get_field_info > raise YTFieldNotFound((ftype, fname), self) > yt.utilities.exceptions.YTFieldNotFound: Could not find field > '('all', > 'pressure')' in data0000. > > > > while this works for a run with HydroMethod = 0. > Could someone give me the nickel tour of hydro method impacts setting > of > variables, and where I should look to make sure pressure is defined? > > Thanks! > d. > > -- > -- Sent from a computer. > > _______________________________________________ > yt-users mailing list > yt-users@lists.spacepope.org > http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org > _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Ok. Here's the set:
http://labs.nationaldataservice.org/upload/5b8d380a
d.
On Tue, May 5, 2015 at 2:13 PM, Nathan Goldbaum
I often debug these issues by inserting a breakpoint at line 315 in yt/fields/field_info_container.py:
https://bitbucket.org/yt_analysis/yt/src/d683286da1623d41e858dc37409910b704f...
This is where we handle any exceptions that a derived field raises during field detection. If a field raises an error here, the field fails field detection and is removed from consideration. If other fields depend on this one, then they won't show up either.
On Tue, May 5, 2015 at 11:03 AM, Matthew Turk
wrote: Hi Dave,
Sorry for the abruptness! If you're already editing the source code, just toss it on to the field_info_container.py definition. Stick it in the __init__ method like so:
self._show_field_errors = [("gas","pressure")]
What instance of FieldInfoContainer should I attach that to?
On Tue, May 5, 2015 at 1:54 PM, Matthew Turk
wrote: You can append ("gas", "pressure") to _show_field_errors on FieldInfoContainer to raise whatever fails.
On Tue, May 5, 2015, 12:49 PM Nathan Goldbaum
wrote: Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset,
it's
likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data
uses HydroMethod 4 or 6. Do you happen to have a small one I could
with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins < dcollins4096@gmail.com> wrote:
Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no
On Tue, May 5, 2015 at 12:58 PM, David Collins
wrote: that play pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: > > Hi Dave, > > You can see all the logic inside yt/frontends/enzo/fields.py -- > probably not too hard to add a new one, and then PR it! > > -Matt > > On Tue, May 5, 2015 at 11:02 AM, David Collins < dcollins4096@gmail.com> > wrote: > > Hi, Everybody! > > > > I'm having a little trouble with getting pressure when using > > HydroMethod=6. > > For instance, > >>>> ds0.all_data()['pressure'] > > > > Traceback (most recent call last): > > File "<stdin>", line 1, in <module> > > File > > > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", > > line 233, in __getitem__ > > f = self._determine_fields([key])[0] > > File > > > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", > > line 489, in _determine_fields > > finfo = self.ds._get_field_info("unknown", fname) > > File > > > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", > > line 482, in _get_field_info > > raise YTFieldNotFound((ftype, fname), self) > > yt.utilities.exceptions.YTFieldNotFound: Could not find field > > '('all', > > 'pressure')' in data0000. > > > > > > > > while this works for a run with HydroMethod = 0. > > Could someone give me the nickel tour of hydro method impacts setting > > of > > variables, and where I should look to make sure pressure is defined? > > > > Thanks! > > d. > > > > -- > > -- Sent from a computer. > > > > _______________________________________________ > > yt-users mailing list > > yt-users@lists.spacepope.org > > http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org > > > _______________________________________________ > yt-users mailing list > yt-users@lists.spacepope.org > http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer. _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Hi, Matt--
No worries. That's where it looked like it should go, but there wasn't any
prior so I figured it best to ask.
So that's useful, now it tells me the problem is with thermal_energy.
Which I find awful strange, since I see (and have printf indicating) that
the self.add_field('thermal_energy') bit does get called for my sim.
Here's the trace.
Ahh, I see. That's a super useful feature, thermal_energy is complaining
about MagneticEnergy now. Why is MagneticEnergy is not defined anywhere.
Why is that?
Hm. Why is Bx not properly aliased to magnetic_field_x?
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 233, in __getitem__
f = self._determine_fields([key])[0]
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py",
line 489, in _determine_fields
finfo = self.ds._get_field_info("unknown", fname)
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 444, in _get_field_info
self.index
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 279, in index
self.create_field_info()
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 334, in create_field_info
self.field_info.load_all_plugins()
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_info_container.py",
line 228, in load_all_plugins
self.find_dependencies(loaded)
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_info_container.py",
line 241, in find_dependencies
deps, unavailable = self.check_derived_fields(loaded)
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_info_container.py",
line 310, in check_derived_fields
fd = fi.get_dependencies(ds = self.ds)
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/derived_field.py",
line 158, in get_dependencies
e[self.name]
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_detector.py",
line 113, in __missing__
vv = finfo(self)
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/derived_field.py",
line 184, in __call__
dd = self._function(self, data)
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/fluid_fields.py",
line 129, in _pressure
* (data[ftype, "density"] * data[ftype, "thermal_energy"])
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_detector.py",
line 97, in __missing__
finfo = self.ds._get_field_info(*field)
File
"/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py",
line 482, in _get_field_info
raise YTFieldNotFound((ftype, fname), self)
yt.utilities.exceptions.YTFieldNotFound: Could not find field '('gas',
'thermal_energy')' in data0000.
On Tue, May 5, 2015 at 2:03 PM, Matthew Turk
Hi Dave,
Sorry for the abruptness! If you're already editing the source code, just toss it on to the field_info_container.py definition. Stick it in the __init__ method like so:
self._show_field_errors = [("gas","pressure")]
What instance of FieldInfoContainer should I attach that to?
On Tue, May 5, 2015 at 1:54 PM, Matthew Turk
wrote: You can append ("gas", "pressure") to _show_field_errors on FieldInfoContainer to raise whatever fails.
On Tue, May 5, 2015, 12:49 PM Nathan Goldbaum
wrote: Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset,
it's
likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data
uses HydroMethod 4 or 6. Do you happen to have a small one I could
with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
wrote:
Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no
On Tue, May 5, 2015 at 12:58 PM, David Collins
wrote: that play pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: Hi Dave,
You can see all the logic inside yt/frontends/enzo/fields.py -- probably not too hard to add a new one, and then PR it!
-Matt
On Tue, May 5, 2015 at 11:02 AM, David Collins <
dcollins4096@gmail.com>
wrote: > Hi, Everybody! > > I'm having a little trouble with getting pressure when using > HydroMethod=6. > For instance, >>>> ds0.all_data()['pressure'] > > Traceback (most recent call last): > File "<stdin>", line 1, in <module> > File > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", > line 233, in __getitem__ > f = self._determine_fields([key])[0] > File > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", > line 489, in _determine_fields > finfo = self.ds._get_field_info("unknown", fname) > File > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", > line 482, in _get_field_info > raise YTFieldNotFound((ftype, fname), self) > yt.utilities.exceptions.YTFieldNotFound: Could not find field > '('all', > 'pressure')' in data0000. > > > > while this works for a run with HydroMethod = 0. > Could someone give me the nickel tour of hydro method impacts setting > of > variables, and where I should look to make sure pressure is defined? > > Thanks! > d. > > -- > -- Sent from a computer. > > _______________________________________________ > yt-users mailing list > yt-users@lists.spacepope.org > http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org > _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer. _______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
Hi Dave,
This looks like the problem! How about we chat off-list to figure
this out? And, we should keep track of the debugging necessary so
that we can make that easier, too. The Bx aliasing seems most likely
culprit to me.
On Tue, May 5, 2015 at 1:19 PM, David Collins
Hi, Matt--
No worries. That's where it looked like it should go, but there wasn't any prior so I figured it best to ask.
So that's useful, now it tells me the problem is with thermal_energy. Which I find awful strange, since I see (and have printf indicating) that the self.add_field('thermal_energy') bit does get called for my sim. Here's the trace.
Ahh, I see. That's a super useful feature, thermal_energy is complaining about MagneticEnergy now. Why is MagneticEnergy is not defined anywhere. Why is that?
Hm. Why is Bx not properly aliased to magnetic_field_x?
Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", line 233, in __getitem__ f = self._determine_fields([key])[0] File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", line 489, in _determine_fields finfo = self.ds._get_field_info("unknown", fname) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", line 444, in _get_field_info self.index File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", line 279, in index self.create_field_info() File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", line 334, in create_field_info self.field_info.load_all_plugins() File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_info_container.py", line 228, in load_all_plugins self.find_dependencies(loaded) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_info_container.py", line 241, in find_dependencies deps, unavailable = self.check_derived_fields(loaded) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_info_container.py", line 310, in check_derived_fields fd = fi.get_dependencies(ds = self.ds) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/derived_field.py", line 158, in get_dependencies e[self.name] File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_detector.py", line 113, in __missing__ vv = finfo(self) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/derived_field.py", line 184, in __call__ dd = self._function(self, data) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/fluid_fields.py", line 129, in _pressure * (data[ftype, "density"] * data[ftype, "thermal_energy"]) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/fields/field_detector.py", line 97, in __missing__ finfo = self.ds._get_field_info(*field) File "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", line 482, in _get_field_info raise YTFieldNotFound((ftype, fname), self) yt.utilities.exceptions.YTFieldNotFound: Could not find field '('gas', 'thermal_energy')' in data0000.
On Tue, May 5, 2015 at 2:03 PM, Matthew Turk
wrote: Hi Dave,
Sorry for the abruptness! If you're already editing the source code, just toss it on to the field_info_container.py definition. Stick it in the __init__ method like so:
self._show_field_errors = [("gas","pressure")]
On Tue, May 5, 2015 at 12:58 PM, David Collins
wrote: What instance of FieldInfoContainer should I attach that to?
On Tue, May 5, 2015 at 1:54 PM, Matthew Turk
wrote: You can append ("gas", "pressure") to _show_field_errors on FieldInfoContainer to raise whatever fails.
On Tue, May 5, 2015, 12:49 PM Nathan Goldbaum
wrote: Hi Dave,
The pressure field is probably coming from the definition in yt/fields/fluid_fields.py. If it doesn't show up for your dataset, it's likely failing field detection.
I'm not sure whether we have a test dataset on yt-project.org/data that uses HydroMethod 4 or 6. Do you happen to have a small one I could play with?
-Nathan
On Tue, May 5, 2015 at 10:40 AM, David Collins
wrote: Hi, Matt--
Thanks for your input. In frontends/enzo/feilds.py, I see where the thermal_energy is computed based on HydroMethod=4,6, but there's no pressure field. Which in principle is fine, since the computation in yt/fields/fluid_fields.py (in setup_fluid_fields) is fine. Does that instance not get called?
On Tue, May 5, 2015 at 12:26 PM, Matthew Turk
wrote: > > Hi Dave, > > You can see all the logic inside yt/frontends/enzo/fields.py -- > probably not too hard to add a new one, and then PR it! > > -Matt > > On Tue, May 5, 2015 at 11:02 AM, David Collins > > wrote: > > Hi, Everybody! > > > > I'm having a little trouble with getting pressure when using > > HydroMethod=6. > > For instance, > >>>> ds0.all_data()['pressure'] > > > > Traceback (most recent call last): > > File "<stdin>", line 1, in <module> > > File > > > > > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", > > line 233, in __getitem__ > > f = self._determine_fields([key])[0] > > File > > > > > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/data_containers.py", > > line 489, in _determine_fields > > finfo = self.ds._get_field_info("unknown", fname) > > File > > > > > > "/Users/dcollins/local-2014-09-24-yt3/src/yt-hg/yt/data_objects/static_output.py", > > line 482, in _get_field_info > > raise YTFieldNotFound((ftype, fname), self) > > yt.utilities.exceptions.YTFieldNotFound: Could not find field > > '('all', > > 'pressure')' in data0000. > > > > > > > > while this works for a run with HydroMethod = 0. > > Could someone give me the nickel tour of hydro method impacts > > setting > > of > > variables, and where I should look to make sure pressure is > > defined? > > > > Thanks! > > d. > > > > -- > > -- Sent from a computer. > > > > _______________________________________________ > > yt-users mailing list > > yt-users@lists.spacepope.org > > http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org > > > _______________________________________________ > yt-users mailing list > yt-users@lists.spacepope.org > http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org -- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
-- -- Sent from a computer.
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
_______________________________________________ yt-users mailing list yt-users@lists.spacepope.org http://lists.spacepope.org/listinfo.cgi/yt-users-spacepope.org
participants (3)
-
David Collins
-
Matthew Turk
-
Nathan Goldbaum