<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
This is in response to the discussion on the list about halos.<br>
<div class="moz-forward-container"><br>
-------- Original Message --------
<table class="moz-email-headers-table" border="0" cellpadding="0"
cellspacing="0">
<tbody>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
</th>
<td>[yt_analysis/yt] Load Text Halos (pull request #192)</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
<td>Tue, 10 Jul 2012 22:25:16 -0000</td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
<td>Stephen Skory <a class="moz-txt-link-rfc2396E" href="mailto:pullrequests-noreply@bitbucket.org"><pullrequests-noreply@bitbucket.org></a></td>
</tr>
<tr>
<th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
<td><a class="moz-txt-link-abbreviated" href="mailto:goldbaum@ucolick.org">goldbaum@ucolick.org</a></td>
</tr>
</tbody>
</table>
<br>
<br>
<pre>A new pull request has been opened by Stephen Skory.
sskory/yt has changes to be pulled into yt_analysis/yt.
<a class="moz-txt-link-freetext" href="https://bitbucket.org/yt_analysis/yt/pull-request/192/load-text-halos">https://bitbucket.org/yt_analysis/yt/pull-request/192/load-text-halos</a>
Title: Load Text Halos
This adds the ability to read in simple text files listing the locations and radii of halos, with optional supplementary data fields. For now the supplementary data fields are assumed to be floats, but eventually (hopefully) this will be changed so that string/integer/other fields can be read in. Perhaps with a re-write/upgrade of halo machinery. The supplementary data is accessed off a halo object using the .supp dict
{{{
#!python
from yt.analysis_modules.halo_finding.api import *
h2 = LoadTextHaloes(pf, "Halos.out", {'x':7,'y':8,'z':9,'r':13, 'm':1})
h2[0].supp['m']
# 1357151571000000.0
h2[0].total_mass()
# 1706602465579130.2
}}}
The first mass is read from the file and is what the halo finder finds; the second is the total DM mass contained in the sphere, which is why the latter is bigger.
The x, y, z, and r columns are required, of course.
Changes to be pulled:
--
This is an issue notification from bitbucket.org.
You are receiving this either because you are the participating
in a pull request, or you are following it.
</pre>
<br>
<br>
</div>
<br>
</body>
</html>