# 23 October 2015 meeting

**URL:** <https://www.rubin.community/t/23-october-2015-meeting/327>\
**Category:** Camera-DM Visualization\
**Created:** [October 22, 2015, 3:57pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327 "2015-10-22T15:57:03Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![jjt](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jjt/32/125_2.png) [@jjt](https://www.rubin.community/u/jjt)\
**Post date:** [October 22, 2015, 3:57pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/1 "2015-10-22T15:57:03Z")

</div>

Folks,

Both John Hart and I have conflicts with this week’s meeting, so I suggest that we cancel it.

```
Next meeting: October 30.

```

Jon

---

<div class="post-metadata">

**Author:** ![gpdf](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/gpdf/32/65_2.png) [@gpdf](https://www.rubin.community/u/gpdf)\
**Post date:** [October 22, 2015, 6:49pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/2 "2015-10-22T18:49:19Z")

</div>

I think the meetings are very useful in keeping things moving. If we are below quorum for a live meeting, can we have a virtual meeting with a review of action items? We are eager to keep the project moving.

---

<div class="post-metadata">

**Author:** ![jjt](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jjt/32/125_2.png) [@jjt](https://www.rubin.community/u/jjt)\
**Post date:** [October 22, 2015, 9:44pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/3 "2015-10-22T21:44:04Z")

</div>

I will really be unavailable (at doctor’s office). I will ask Wei and Dingcheng to connect, so that they can give progress reports. That ought to work.

---

<div class="post-metadata">

**Author:** ![jjt](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/jjt/32/125_2.png) [@jjt](https://www.rubin.community/u/jjt)\
**Post date:** [October 22, 2015, 9:50pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/4 "2015-10-22T21:50:39Z")

</div>

Is it possible to rename a topic? I’d like to remove “canceled” fon this topic.

---

<div class="post-metadata">

**Author:** ![ktl](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/ktl/32/1373_2.png) [@ktl](https://www.rubin.community/u/ktl)\
**Post date:** [October 22, 2015, 9:51pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/5 "2015-10-22T21:51:10Z")

</div>

Click on the pencil next to the topic name (I think you should see it).

---

<div class="post-metadata">

**Author:** ![dyue2](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/dyue2/32/122_2.png) [@dyue2](https://www.rubin.community/u/dyue2)\
**Post date:** [October 23, 2015, 6:25pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/6 "2015-10-23T18:25:47Z")

</div>

Sorry for the late reply. Do we need to use Bluejeans for this meeting?

Here is what I have been doing so far.

Currently I was trying to establish the communication between the backend and frontend. And I wrote my proposed item into a [github wiki](https://github.com/DarwinSenior/LSST-Monitor-Frontend/wiki/Proposed-Communication-Scheme) And I made a small demo for that.

However, there are few issues I ran into.

For the first time I open the browser, I came across the violation of _origin domain policy_. However, if I refresh the page, there is no such problem again. I am not sure what happened.  
The server I set up is only for demo purposes, and might be noticeably lagging for multiple user. (Or even completely blocked).  
So, what I have done is to compute the average value for certain region. And the region is predetermined by the boundary I preset before.

If you go to the page lsst.cs.illinois.edu, and type

```auto
create_box box
read_mouse box
show_bounday

```

And hover the mouse on the displayed image, it will show the average pixel value.

---

<div class="post-metadata">

**Author:** ![gpdf](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/gpdf/32/65_2.png) [@gpdf](https://www.rubin.community/u/gpdf)\
**Post date:** [October 23, 2015, 6:46pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/7 "2015-10-23T18:46:57Z")

</div>

> [@dyue2](#):
>
> Do we need to use Bluejeans for this meeting?

Yes, same instructions as last time.

---

<div class="post-metadata">

**Author:** ![dyue2](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/dyue2/32/122_2.png) [@dyue2](https://www.rubin.community/u/dyue2)\
**Post date:** [October 23, 2015, 7:05pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/8 "2015-10-23T19:05:38Z")

</div>

Is the meeting id 107541143 or is it something else?

---

<div class="post-metadata">

**Author:** ![gpdf](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/gpdf/32/65_2.png) [@gpdf](https://www.rubin.community/u/gpdf)\
**Post date:** [October 23, 2015, 7:06pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/9 "2015-10-23T19:06:38Z")

</div>

That should be correct. We are a little late getting started here at SLAC. Just connecting now.

---

<div class="post-metadata">

**Author:** ![victor\_ren](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/victor_ren/32/281_2.png) [@victor\_ren](https://www.rubin.community/u/victor_ren)\
**Post date:** [October 23, 2015, 10:26pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/10 "2015-10-23T22:26:04Z")

</div>

Oct. 23, 2015.  
So now my script is able to combine all the raft scale FITS into a focal plane scale FITS. I’ve checked the header files. Both the original FITS and generated ones are of single extension. Prof. Jon @jjt can you tell us the source of the files?

Things to do next:

- Include more necessary information in the header of generated files. Add specification on what information we need for display and diagnosis.
- Gap region between CCDs or Amplifiers which is not specified in the header? (Correct me if I’m wrong)
- Test what parameters (especially memory size) are suitable for Firefly to display FITS of ~14GB.
- Upload completed FITS files into shared directory (Dropbox).

---

<div class="post-metadata">

**Author:** ![tony\_johnson](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/tony_johnson/32/124_2.png) [@tony\_johnson](https://www.rubin.community/u/tony_johnson)\
**Post date:** [October 29, 2015, 2:18pm UTC](https://www.rubin.community/t/23-october-2015-meeting/327/11 "2015-10-29T14:18:17Z")

</div>

Hi @gpdf, if i remember correctly you made a list of action items during last week’s meeting. Did these get posted somewhere?

---

<div class="post-metadata">

**Author:** ![gpdf](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/gpdf/32/65_2.png) [@gpdf](https://www.rubin.community/u/gpdf)\
**Post date:** [January 2, 2016, 7:41am UTC](https://www.rubin.community/t/23-october-2015-meeting/327/12 "2016-01-02T07:41:46Z")

</div>

> [@tony\_johnson](#):
>
> Hi @gpdf, if i remember correctly you made a list of action items during last week’s meeting. Did these get posted somewhere?

Sorry, I’d misplaced it until now. Here are the notes:

* * *

@victor_ren still working on raft-scale mosaic - job is running now.

Loading of raft-scale image tested by @xiuqin (10 seconds) and @victor_ren (13 second initial load, 1 second for refreshes after that).

No progress on header keyword item.

Discussion: what is the purpose of raft-scale files? Are they throwaways for use only by Firefly (whether created on-the-fly or in advance), or does the camera need an official format?

Need a specification for what we want to be able to do with these files and what header information is needed in raft-level images.

Some discussion of full focal plane images and the similar issues for them, but we decide to concentrate for now on raft-level images.

- When displaying a raft-level image, we need to be able to get the CCD and amplifier IDs and the integer pixel coordinates within an amplifier.

- Also need to be able to display CCD ID with integer pixel coords within the CCD

- We need a spec for the nominal integer-pixel gaps in raft assembly ( **not** including the additional gaps for pre/post/over-scan, as post- and over-scan are in principle variable):  
@tony_johnson to drive a spec for what’s required and how to include this in the headers of the CCD-level 16-extension files.

@jjt to tell us what the provenance of the raft-scale files already posted is, and what gaps were used.

@victor_ren to post the inputs he used for raft assembly.
