<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Thanks, Francois. You’re probably the only one who has looked at our DataLinks outside the HEASARC. 😉</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<p style="direction: ltr; margin-top: 0px; margin-bottom: 0px; margin-left: 40px;">
<span style="font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">Now, as for Heasarc TAP service, it's very similar in the sense that they often have a DataLink service descriptor in the catalogue response and not in ObsTAP
see for example the CALET GamaRay Burst master catalog : <a href="https://heasarc.gsfc.nasa.gov/xamin/vo/tap/sync?REQUEST=doQuery&LANG=ADQL&MAXREC=20000000&QUERY=SELECT+TOP+9999+*+FROM+calgbmmstr+" class="moz-txt-link-freetext" data-outlook-id="c167686e-f2ec-4c9b-84be-621601b048ab" style="margin-top: 0px; margin-bottom: 0px;">
https://heasarc.gsfc.nasa.gov/xamin/vo/tap/sync?REQUEST=doQuery&LANG=ADQL&MAXREC=20000000&QUERY=SELECT+TOP+9999+*+FROM+calgbmmstr+</a></span></p>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
We are still working on our ObsTAP service, so what you’re seeing is a work in progress, call it a beta. (It isn’t registered yet, and though we have asked ESASky to test it, we have not yet asked them to use it in production.) Indeed, the service descriptor
is not there yet among many other things we are still working on. But it will be very easy to add. </div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Regarding semantics, this is another thing on the list. When I asked about those semantics values that lead to a web page, the developer told me that Tom basically said (this was over 10 years ago) that 'since nobody had done this before, we could do what
we want'. 😃 But that was a while ago, and now we need to update most if not all of our semantics metadata. This is also on the To Do list. </div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
In fact, as we develop ObsTAP in parallel with a new GUI discovery interface that will be based off of it, we have a number of questions about what to put in the ObsTAP discovery result for dataproduct_type and dataproduct_subtype given that all the access_format
values are supposed to be datalinks. Then in the DataLink table result, what semantics and local_semantics should we use is TBD. Maybe a topic for a DAL session I guess, but some coffee chats might help enough. </div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; margin-left: 40px; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
If the issue there is to be required to pass through a two step process, then the TAP interface to the DataLink table would allow to avoid that by joining thecatalog table to the DataLink table on the source id. </div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Chandra has three different IDs in play, the source ID, the stack ID, and the obs ID, but your basic idea is still applicable. The CSC tables will not be part of obscure, only the observations. The stack products link straightforwardly to the CSC itself. And
the source list will link to obscure products using a few nested SQL selects on the different ID tables. AFAIK, we can do all of Ian’s use cases this way, thought I admit we haven’t yet implemented it much less tested it. But the new dev GUI is already
handling the obscure table, the datalink service URL in each row, and then grouping the types of products it finds so that the user can make a selection. </div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
[I give up trying to get my spell checker to stop correcting "obscore" to obscure. Besides, it’s funny.] </div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Looking forward to seeing some of you in a few weeks!</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
Tess</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="direction: ltr; font-family: Aptos, Arial, Helvetica, sans-serif; font-size: 12pt; color: rgb(0, 0, 0);">
<br>
</div>
<div style="color: inherit; background-color: inherit;" id="ms-outlook-mobile-signature">
<div class="MsoNormal" style="direction: ltr;">Get <a href="https://aka.ms/GetOutlookForMac" data-outlook-id="748c35b9-b557-4ca6-8248-2da06d3c72c3">
Outlook for Mac </a></div>
</div>
<div id="mail-editor-reference-message-container" style="color: inherit; background-color: inherit;">
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
</div>
<div style="padding: 3pt 0in 0in; border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) currentcolor currentcolor;">
<div class="ms-outlook-mobile-reference-message skipProofing" style="text-align: left; font-family: Aptos; font-size: 12pt; color: black;">
<b>From: </b>BONNAREL FRANCOIS gmail <francois.bonnarel@gmail.com><br>
<b>Date: </b>Thursday, May 7, 2026 at 3:08 AM<br>
<b>To: </b>Dr. Ian N. Evans <ievans@cfa.harvard.edu>; Jaffe, Tess (GSFC-6601) <tess.jaffe@nasa.gov><br>
<b>Cc: </b>heig@ivoa.net <heig@ivoa.net><br>
<b>Subject: </b>Re: [Heig] [EXTERNAL] [BULK] Re: Post running meeting thoughts<br>
<br>
</div>
</div>
<table class="ms-outlook-mobile-reference-message skipProofing" cellspacing="0" cellpadding="0" border="0" style="direction: ltr; text-indent: revert; line-height: revert; white-space: revert; text-transform: revert; background-color: revert; display: table; margin: revert; width: 100%; height: revert; table-layout: fixed; color: revert;">
<tbody>
<tr style="background-color: revert;">
<td class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr; text-indent: revert; line-height: revert; white-space: revert; text-transform: revert; border-width: revert; border-style: revert; border-color: revert; background-color: rgb(166, 166, 166); padding: 7px 2px; word-break: revert; color: revert; width: 0px; height: revert;">
</td>
<td class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr; text-align: left; text-indent: revert; line-height: revert; white-space: revert; text-transform: revert; border-width: revert; border-style: revert; border-color: revert; background-color: rgb(234, 234, 234); padding: 7px 5px 7px 15px; word-break: revert; color: rgb(33, 33, 33); width: 100%; height: revert;">
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr; text-align: left; text-indent: revert; line-height: revert; white-space: revert; text-transform: revert; font-family: wf_segoe-ui_normal, "Segoe UI", "Segoe WP", Tahoma, Arial, sans-serif; color: revert;">
<span style="letter-spacing: revert; background-color: revert; line-height: revert; text-transform: revert;">You don't often get email from francois.bonnarel@gmail.com.
<a href="https://aka.ms/LearnAboutSenderIdentification" data-outlook-id="6dfb084f-0000-4f2e-9034-68d34c229ae1" style="color: revert; display: revert; background-color: revert;">
Learn why this is important</a></span></div>
</td>
<td class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr; text-align: left; text-indent: revert; line-height: revert; white-space: revert; text-transform: revert; border-width: revert; border-style: revert; border-color: revert; background-color: rgb(234, 234, 234); padding: 7px 5px; word-break: revert; color: rgb(33, 33, 33); width: 75px; height: revert;">
</td>
</tr>
</tbody>
</table>
<table class="ms-outlook-mobile-reference-message skipProofing" align="left" cellspacing="0" style="border-width: 2px; border-style: solid; border-color: black;">
<tbody>
<tr>
<td class="ms-outlook-mobile-reference-message skipProofing" style="line-height: normal; background-color: rgb(255, 235, 156); padding: 5px; width: 100%;">
<div class="ms-outlook-mobile-reference-message skipProofing" style="line-height: normal;">
<span style="font-size: 10pt; color: rgb(0, 0, 0); line-height: normal;"><b>CAUTION:</b></span>
<span style="font-size: 10pt; line-height: normal;">This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC.</span></div>
</td>
</tr>
</tbody>
</table>
<div class="ms-outlook-mobile-reference-message skipProofing" style="direction: ltr;">
<br>
<br>
<br>
</div>
<p class="ms-outlook-mobile-reference-message skipProofing">Hi Tess, Ian, all</p>
<p class="ms-outlook-mobile-reference-message skipProofing">Sorry for the long delay</p>
<p class="ms-outlook-mobile-reference-message skipProofing">After reading Tess email late in March I took the time to look at Heasarc TAP service and I will comment below. Let's first discuss one</p>
<p class="ms-outlook-mobile-reference-message skipProofing">point in Ian's answer.</p>
<blockquote>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">Hi Tess,<br>
<br>
</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">I think whether end users want to search for specific datasets vary depending on the data collection and types of data, and the number of and size of data products in the collection.</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">If the data collection consists solely of individual observations processed through standard data processing pipelines and that need further user data analysis that require the set of associated data products to extract science then
I agree that the ability to search for the individual observation event list (or perhaps event bundle) with associated data products accessible using datalink is likely sufficient.</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">If the data collection contains advanced data products (for example the Chandra Source Catalog data products) the usage patterns change. Our experience is that users doing catalog science typically identify potential sources of interest
and then want to retrieve subsets of data products for those sources, often in several rounds. </div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">For example, they may identify hundreds, thousands, or in some cases tens of thousands of candidate sources matching their search criteria, and may subsequently download (e.g.) the light curves for all of the observations of these
sources (on average 3 times as many as number of sources), do some automated pre-filtering on the light curves, and then download (e.g.) the cutout event lists surrounding the individual observation detections for further analysis. They might subsequently
come back to download the region definitions, and perhaps the individual observation PHA spectra of the detections.</div>
</blockquote>
<div class="moz-text-html">But if the main discovery path is to start from sources then I realize that the first approach would be a SimpleConeSearch or a TAP query on the catalog seen as a table with parameters estimated for this source. You already have
this in Vizier and in your chandra archive (see below within Aladin)</div>
<p class="moz-text-html">The SCS interface to this catalog in VizieR is the following (with randomly chosen RA, DEC, SR):
<a href="https://vizier.cds.unistra.fr/viz-bin/conesearch/IX/70/csc21Mas?RA=00.6405&DEC=-08.2216&SR=5.0" class="moz-txt-link-freetext" originalsrc="https://vizier.cds.unistra.fr/viz-bin/conesearch/IX/70/csc21Mas?RA=00.6405&DEC=-08.2216&SR=5.0" data-outlook-id="e60a26da-7afb-46d1-8595-24eff6c48b42" style="margin-top: 0px; margin-bottom: 0px;">
https://vizier.cds.unistra.fr/viz-bin/conesearch/IX/70/csc21Mas?RA=00.6405&DEC=-08.2216&SR=5.0</a></p>
<p class="moz-text-html">The result is a VOTable where a DataLink service descriptor could be added in order to point to all related event list, response functions and analysis data products.</p>
<p class="moz-text-html">This DataLink usage with Source catalogs (instead of ObsTAP/SIA.SSA context) is an extension introduced with version 1.1 and is perfectly adapted to use cases where</p>
<p class="moz-text-html">you don't know the number and type and content of the additional items you want to attach to the primary resource (here the source record in the table)</p>
<p class="moz-text-html">This is how light curves are related to sources in corot for example :
<a href="https://vizier.cds.unistra.fr/viz-bin/conesearch/B/corot/Faint_star?RA=100.94235&DEC=-00.89651&SR=1" class="moz-txt-link-freetext" originalsrc="https://vizier.cds.unistra.fr/viz-bin/conesearch/B/corot/Faint_star?RA=100.94235&DEC=-00.89651&SR=1" data-outlook-id="86ec5ea6-6af8-493d-88e0-030c1d3461c6" style="margin-top: 0px; margin-bottom: 0px;">
https://vizier.cds.unistra.fr/viz-bin/conesearch/B/corot/Faint_star?RA=100.94235&DEC=-00.89651&SR=1</a></p>
<p class="moz-text-html">You can load this URL in TOPCAT and invoke the service and will discover the different light curves associated with each source</p>
<p class="moz-text-html">Now, as for Heasarc TAP service, it's very similar in the sense that they often have a DataLink service descriptor in the catalogue response and not in ObsTAP see for example the CALET GamaRay Burst master catalog :
<a href="https://heasarc.gsfc.nasa.gov/xamin/vo/tap/sync?REQUEST=doQuery&LANG=ADQL&MAXREC=20000000&QUERY=SELECT+TOP+9999+*+FROM+calgbmmstr+" class="moz-txt-link-freetext" originalsrc="https://heasarc.gsfc.nasa.gov/xamin/vo/tap/sync?REQUEST=doQuery&LANG=ADQL&MAXREC=20000000&QUERY=SELECT+TOP+9999+*+FROM+calgbmmstr+" data-outlook-id="c167686e-f2ec-4c9b-84be-621601b048ab" style="margin-top: 0px; margin-bottom: 0px;">
https://heasarc.gsfc.nasa.gov/xamin/vo/tap/sync?REQUEST=doQuery&LANG=ADQL&MAXREC=20000000&QUERY=SELECT+TOP+9999+*+FROM+calgbmmstr+</a></p>
<p class="moz-text-html">We can look at this VOTable with help of TOPCAT as you can see below in the second screenshot. There are plenty of links attached to each row in the first table, including the #this one.</p>
<p class="moz-text-html">The others are all auxiliary. I would only suggest to detail the various flavors of auxiliary in the local semantics field instead of semantics in order to improve interoperability, because #auxiliary only belongs to the standard vocabulary.</p>
<blockquote>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">This is a very different usage pattern where end users are retrieving particular data products for potentially a large number of objects, and subsequently refining the list and downloading additional data products, sometimes in multiple
steps. One reason for this approach is scale. For example, there are roughly 100x the number of data products, and 10x the data volume, for the Chandra Source Catalog vs. the Chandra data archive data products for the set of processed science observations.</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">Could this be done by requiring end users to search for observations and then using datalink to access the individual data products? Probably not, because many of our data products merge data from multiple observations and it would
be very difficult to encode the necessary source — stack detection — observation detection linkages correctly. In any case, doing queries like this en masse and then having to select subsets of datalinks is going to be much more difficult than a simple ObsCore
query that directly returns the records (and access_urls) that you are looking for.</div>
</blockquote>
<div class="moz-text-html">If the issue there is to be required to pass through a two step process, then the TAP interface to the DataLink table would allow to avoid that by joining thecatalog table to the DataLink table on the source id. </div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">Best regards</div>
<div class="moz-text-html">François</div>
<blockquote>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">With regard to your specific question regarding RMFs. I don’t know that users will download RMFs without either concurrently or previously downloading the PHA. Occasionally users will search for RMFs (and ARFs) separately from PHA
spectra because they have previously retrieved the latter. On the other hand, we do for example see end users downloading PSFs independently from the primary datasets. This is likely because the catalog includes a vast set of high quality PSFs (of order
10M) covering the entire Chandra field of view and PSFs are rather expensive to generate.</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">We have specifically tried very hard to focus on data discovery in the proposed ObsCore extensions note, and have used actual experience - how do we see our users wanting to work - to help guide our proposals.</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html">Thanks,</div>
<div class="moz-text-html">—Ian</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<blockquote>
<div class="moz-text-html">On Mar 20, 2026, at 11:26, Jaffe, Tess (GSFC-6601) via heig
<a href="mailto:heig@ivoa.net" class="moz-txt-link-rfc2396E" data-outlook-id="a9a3dd7b-278a-4e07-8d14-31a729c5784e">
<heig@ivoa.net></a> wrote:</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
Hi everybody,</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
I agree with Francois on a number of things, but especially that there is a lot of misunderstanding and misrepresentation going on here. <b>Nobody</b> has ever expressed reluctance to ensure that HEA-specific ancillary products such as responses etc. are made
available easily through VO protocols. Let’s focus on what the issue actually is, because I think the discussion has lost sight of it.</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
In my opinion, the main issue is not whether things like response matrices are science data, are needed by the users, or should be in the VO. I think we all agree that this is obvious. The question is what is the best method for making them accessible
<i>in the needed context</i> and how far we need to customize what goes in the ObsCore table itself for different fields. That then is a question about discoverability and complexity. </div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
Having an individual row in an ObsCore table enables a user to <b>search for</b> that one specific thing. The best practice recommendation for the use of ObsCore is that the access_url be a datalink. So for a given product listed in an ObsCore table, three
queries are needed: one to find the product, one to get its datalinks, and then one to download the file(s). I cannot recall having heard of a use case where somebody was interested in finding only the RMFs from a given instrument in a given year. (Please
let me know if you have a use case for this so that we can address it directly. I can think of calibration projects, but this is an edge case that can be addressed another way.) Users will instead want to find all of the spectra from some source/time/waveband.
That is why ObsCore has a row for such a product. Nobody disputes that to do the scientific analysis on that spectrum requires the user to also have an RMF. But that RMF does not need to be independently discoverable, just correctly linked to the spectrum
that is of interest. </div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
Francois has proposed a number of solutions to this. ObsCore has a very reasonable amount of flexibility and specificity, and it is quite important to worry about adding unnecessary complexity and size. (I myself was worried about the additional complexity
of the datalink layer, but now in implementation, I’m becoming a fan.) The radio extension doc you may note proposes a number of fields that are
<i>all about discovery</i>. It then states, “Auxiliary datasets such as uv distribution map, dirty beam maps, frequency/amplitude plots, phase/amplitude plots are useful for astronomers to check data quality. In that case DataLink … may provide a solution
to attach these auxiliary data to ObsCore records.” That makes sense to me. </div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
So I suggest we follow what the radio folks are doing. With this in mind, I think that three of the proposed columns -- T_intervals , Obs_mode , Event_type – are very clearly applicable to data discovery and should be added to the ObsCore table. But some
of the other proposed fields would be better added in datalinks with a HEA-specific vocabulary. We should discuss these on a case-by-case basis after having agreed on the purpose of a row in ObsCore. </div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
I hope this helps the discussion move along productively.</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; margin: 0in; font-family: Aptos, sans-serif; font-size: 11pt;">
<br>
Tess</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
</blockquote>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; line-height: 1.2; text-transform: none; background-color: rgb(255, 255, 255); margin-top: 0pt; margin-bottom: 0pt; font-family: Arial; font-size: 9.5pt; color: rgb(0, 0, 0);">
<span style="font-weight: 700; text-transform: none;">—</span></div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; line-height: 1.2; text-transform: none; background-color: rgb(255, 255, 255); margin-top: 0pt; margin-bottom: 0pt; font-family: Arial; font-size: 9.5pt; color: rgb(0, 0, 0);">
<span style="font-weight: 700; text-transform: none;">Dr. Ian Evans</span></div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; line-height: 1.2; text-transform: none; background-color: rgb(255, 255, 255); margin-top: 0pt; margin-bottom: 0pt; font-family: Arial; font-size: 12.666667px; color: rgb(0, 0, 0);">
<b>Astrophysicist</b></div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; line-height: 1.2; text-transform: none; background-color: rgb(255, 255, 255); margin-top: 0pt; margin-bottom: 0pt; font-family: Arial; font-size: 12.666667px; color: rgb(0, 0, 0);">
<b>Chandra X-ray Center</b></div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; line-height: 1.2; text-transform: none; background-color: rgb(255, 255, 255); margin-top: 0pt; margin-bottom: 0pt; font-family: Arial; font-size: 9.5pt; color: rgb(0, 0, 0);">
<span style="background-color: rgb(255, 255, 255); font-weight: 700;">Center for Astrophysics | Harvard & Smithsonian</span></div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; line-height: 1.2; text-transform: none; background-color: rgb(255, 255, 255); margin-top: 0pt; margin-bottom: 0pt; font-family: Arial; font-size: 9.5pt; color: rgb(0, 0, 0);">
Office: (617) 496 7846 | Cell: (617) 699 5152</div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; line-height: 1.2; text-transform: none; background-color: rgb(255, 255, 255); margin-top: 0pt; margin-bottom: 0pt; font-family: Arial; font-size: 9.5pt; color: rgb(0, 0, 0);">
60 Garden Street | MS 81 | Cambridge, MA 02138</div>
<div class="moz-text-html" style="direction: ltr;"><br>
<img src="cid:part1.FumDT6OD.4V02vxx6@gmail.com" alt="PastedGraphic-2.png" width="263" style="width: 263px; max-width: 100%;"><span style="font-family: Monaco; font-size: 12px; color: rgb(0, 0, 0); text-transform: none;"><br>
<br>
</span></div>
<div class="moz-text-html" style="text-align: left; text-indent: 0px; text-transform: none; font-family: Monaco; font-size: 12px; color: rgb(0, 0, 0);">
<span style="text-transform: none;"> </span></div>
<div class="moz-text-html"><img src="cid:part2.gu83Aa20.1VVzscLw@gmail.com" alt="PastedGraphic-3.png" width="111" style="width: 111px; max-width: 100%;"><span style="font-family: Arial, sans-serif; font-size: 9.5pt; color: rgb(0, 0, 0); line-height: 14.566668px; text-transform: none;"><u><br>
<br>
</u></span><span style="font-family: Arial; font-size: 13px; color: rgb(0, 0, 0); line-height: 14.566668px; text-transform: none;"><a href="http://cfa.harvard.edu/" originalsrc="http://cfa.harvard.edu/" data-outlook-id="d9702d74-6ad5-4fef-b63a-f7a0253801b3"><u>cfa.harvard.edu</u></a> |
<a href="http://cfa.harvard.edu/facebook" originalsrc="http://cfa.harvard.edu/facebook" data-outlook-id="d4659586-6632-46df-974c-c33c182fe9b9">
<u>Facebook</u></a> | <a href="http://cfa.harvard.edu/twitter" originalsrc="http://cfa.harvard.edu/twitter" data-outlook-id="f17566ce-7828-4afa-a352-c35b7d155a24">
<u>Twitter</u></a> | <a href="http://cfa.harvard.edu/youtube" originalsrc="http://cfa.harvard.edu/youtube" data-outlook-id="5f83b1b4-fc2d-4043-84f9-ad19cb1ae9a6">
<u>YouTube</u></a> | <a href="http://cfa.harvard.edu/newsletter" originalsrc="http://cfa.harvard.edu/newsletter" data-outlook-id="3a434dc6-82c2-405a-a6cf-ea5eafb980c2">
<u>Newsletter</u></a></span></div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<div class="moz-text-html" style="direction: ltr;"><br>
</div>
<pre><div class="moz-txt-sig" style="font-size: 12px;">--
heig mailing list
<a href="mailto:heig@ivoa.net" class="moz-txt-link-abbreviated moz-txt-link-freetext" data-outlook-id="31d5fa3e-f320-416e-bfdc-350a7ed55b57">heig@ivoa.net</a>
<a href="http://mail.ivoa.net/mailman/listinfo/heig" class="moz-txt-link-freetext" originalsrc="http://mail.ivoa.net/mailman/listinfo/heig" data-outlook-id="4aa45655-a9d2-4aeb-896a-bb49bec014ed">http://mail.ivoa.net/mailman/listinfo/heig</a>
</div></pre>
</blockquote>
<div class="moz-text-html" style="direction: ltr;"><img src="cid:part3.pxuLRFzj.tCCs4XWQ@gmail.com" style="max-width: 100%;"></div>
<p class="moz-text-html"><br>
</p>
<p class="ms-outlook-mobile-reference-message skipProofing"><br>
</p>
<p class="ms-outlook-mobile-reference-message skipProofing"><br>
</p>
<p class="ms-outlook-mobile-reference-message skipProofing"><img src="cid:part4.3v2XZu1k.Y0sxW4IM@gmail.com" style="max-width: 100%; margin-top: 0px; margin-bottom: 0px;"></p>
</div>
</body>
</html>