10:50:11 From Francesco Verrecchia to Everyone:
	hello
11:02:22 From Assaf Horesh to Brad Cenko(direct message):
	Good to see you Brad 🙂
11:02:44 From Brad Cenko to Assaf Horesh(direct message):
	Thanks Assaf - great to “see” you too. Hope you and everyone there are OK.
11:03:15 From Assaf Horesh to Brad Cenko(direct message):
	Indeed, thanks.
11:03:30 From Brad Cenko to Chris Shrader(direct message):
	Hi Chris - Did you have a question?
11:04:31 From Chris Shrader to Brad Cenko(direct message):
	Yes, maybe he's answering it now.
11:05:58 From Brad Cenko to Chris Shrader(direct message):
	OK, feel free to ping me here if you need anything.
11:10:16 From RAHUL GUPTA to Everyone:
	Hello everyone from the Swift Team!!!! Excited to meet all of you…
11:10:23 From RAHUL GUPTA to Everyone:
	Please post your questions here and we will track them.
11:16:53 From Lynnie Saade to Everyone:
	Does the gyro problem require a version of Heasoft that was made after March?
11:19:05 From Satish Sonkamble to Everyone:
	full screen please
11:22:59 From Brad Cenko to Everyone:
	Replying to "Does the gyro proble..."
	
	The gyroscope issue exclusively affects the UVOT data - XRT and BAT data are unaffected (the angular resolution is sufficiently large that it doesn’t have any noticeable impact). For the UVOT data, we are working on some routines to allow for better stacking of event mode data, which should allow more precise photometry. For image mode data, there isn’t really much that can be done other than use a larger aperture. @Michael Siegel may want to say more.
11:23:32 From Max De Pasquale to Everyone:
	I have connection problems… how many BAT detectors did he say are currently working alright?
11:23:50 From Kim Page to Everyone:
	17,000
11:23:55 From Max De Pasquale to Everyone:
	Thank you Kim
11:24:10 From Kim Page to Everyone:
	Reacted to "Thank you Kim" with 👍
11:27:15 From Igor Andreoni to Everyone:
	Could you please clarify: Are BAT data acquired during slewing stored, even if it doesn't trigger? Or are BAT data lost during slews?
11:28:23 From sibasish laha to Everyone:
	Replying to "Could you please cla..."
	
	Yes. BAT data is stored during slewing.
11:28:51 From Igor Andreoni to Everyone:
	Replying to "Could you please cla..." 
	
	 Great, thanks!
11:29:00 From sibasish laha to Everyone:
	Replying to "Could you please cla..."
	
	BAT software is designed to NOT trigger on a source during slewing.
11:30:18 From Francesco Verrecchia to Everyone:
	Hi, this BatAnalysis package do use the FTOOLS BAT official tasks I suppose, correct?
11:32:01 From Lynnie Saade to Everyone:
	Can the BatAnalysis package be installed with an Anaconda installation of Python? I am under the impression using conda and pip together is discouraged
11:34:37 From Robin Corbet to Everyone:
	The signal-to-noise of the transient monitor light curves has become much much worse. Is that just the expected decline, or is there any hope of recovering S/N at all?
11:36:37 From Tyler Parsotan to Everyone:
	Replying to "Hi, this BatAnalysis..."
	
	Yes, heasoftpy needs to be installed to use BatAnalysis
11:37:15 From Francesco Verrecchia to Everyone:
	Replying to "Hi, this BatAnalysis..."
	
	thanks, so all python, no need for the standard FTOOLS
11:37:33 From Main Pal to Everyone:
	Hi, will swift bat analysis tool be available like xrt analysis online tool?? 
11:38:22 From Tyler Parsotan to Everyone:
	Replying to "Can the BatAnalysis ..."
	
	Currently, it is only on pypi so installation with the “conda” command is not possible. Nonetheless, installing the package with pip in your conda environment works fine. In the future, this discrepancy will be addressed.
11:39:41 From Lia Corrales to Everyone:
	Replying to "Can the BatAnalysis ..."
	
	I’ve found that installing things with pip while using conda is not an issue, but to be safe you should stay consistent in using pip just for that package. Shouldn’t be a problem here 🙂
11:39:56 From Prof. Chick to Everyone:
	Replying to "Can the BatAnalysis ..."
	
	Does the pip install grab all the right environments properly to resolve (like heasoftpy) issues?
11:40:27 From Tyler Parsotan to Everyone:
	Replying to "The signal-to-noise ..."
	
	There may not be a way to recover the S/N as the scaled maps are in the lower energy range where the detectors are noisy. The noise has been increasing due to the age of the instrument and is part of the reason that the number of enabled detectors is ~0.5 of the number of total detectors there actually are
11:41:25 From Tyler Parsotan to Everyone:
	Replying to "Hi, will swift bat a..."
	
	This is a long term goal without a clear timeline at this time. In the meantime, it is available for processing BAT data on your local machine
11:42:05 From Osman to Everyone:
	Replying to "Hi, will swift bat a..."
	
	how can we esclude the pileup
11:42:44 From Tyler Parsotan to Everyone:
	Replying to "Can the BatAnalysis ..."
	
	Pip only deals with other pypi packages (such as swifttools) since heasoftpy is not on pypi that is not one that can be automatically installed. All the other dependencies are taken care of
11:43:23 From Kim Page to Everyone:
	Replying to "Hi, will swift bat a..."
	
	https://www.swift.ac.uk/analysis/xrt/pileup.php
11:43:24 From Prof. Chick to Everyone:
	Replying to "Can the BatAnalysis ..."
	
	Tx
11:43:45 From Tyler Parsotan to Everyone:
	Replying to "Hi, this BatAnalysis..."
	
	Heasoftpy is automatically installed when heasoft is installed, so implicitly yes installing heasoft and ftools is needed
11:44:57 From Jonathan Gelbord to Everyone:
	Could the recent gyro problems/pointing instability throw off the estimation of flux lost to XRT bad columns?
11:45:02 From Priyanshu Sharma to Everyone:
	Can these presentations shared with us on email or on the site for future reference ?
11:45:27 From Amy Lien to Everyone:
	Replying to "The signal-to-noise ..."
	
	Hi Robin, in addition to what Tyler said,  I believe some transient monitor data are contaminated by the known “overflown” problem. When we have a chance to look into the code, those should be able to be removed. There are likely some additional problems (e.g., some abnormally low data points seen in the Crab light curve), once we check the transient monitor code and identify the cause, we may be able to remove the known incorrect data to improve some S/N.
11:45:34 From Francesco Verrecchia to Everyone:
	Replying to "Hi, this BatAnalysis..."
	
	Ah, ok, I supposed it should be installed separately. thanks
11:45:57 From Robin Corbet to Everyone:
	Replying to "The signal-to-noise ..."
	
	thanks
11:47:25 From Kyle Cook to Everyone:
	Replying to "Can these presentati..."
	
	Hi Priyanshu, they said the slides and the recording of this workshop will be added to the Swift website
11:47:48 From Kim Page to Everyone:
	Replying to "Could the recent gyr..."
	
	We looked into this (specifically to check our positions were still OK), and we didn't find that there were significant problems for the XRT - mainly because our pixels are much bigger than UVOT's, I think. Basically, within the error bars, the gyro jitter doesn't seem to have an effect on XRT.
11:48:26 From Jonathan Gelbord to Everyone:
	Replying to "Could the recent gyr..."
	
	That's good to hear. Thanks Kim.
11:48:38 From Priyanshu Sharma to Everyone:
	Replying to "Can these presentati..."
	
	👍🏽
11:52:26 From David Palmer to Everyone:
	(David Palmer coming in late) Are there any unaddressed BAT questions that were waiting on me?
11:54:49 From sibasish laha to Everyone:
	Replying to "(David Palmer coming..."
	
	Hi David. Thanks. The queries as of now have been answered.
11:56:59 From Kyle Cook to Everyone:
	Where can I find full info on the red leak in W2 and W1? I’m curious how this may affect the UV colors from UVOT
11:59:59 From Paul Kuin to Everyone:
	Breeveld et al, 2011 describes the filters and the detailed filter curves are in the Swift UVOT CALDB and can be combined with a spectrum to determine the count rates from parts of the spectrum.
12:00:13 From Kyle Cook to Everyone:
	Reacted to "Breeveld et al, 2011..." with 👍
12:01:15 From Osman to Everyone:
	Replying to "Hi, will swift bat a..."
	
	Thanks Kim
12:01:49 From Francesco Verrecchia to Everyone:
	Michael, why intensive except for M2 filter? thanks..
12:02:24 From Max De Pasquale to Everyone:
	Reacted to "Breeveld et al, 2011..." with 👍
12:03:39 From Noel Klingler to Everyone:
	The M2 filter is the least sensitive and the most narrow filter (see:  https://www.swift.ac.uk/analysis/uvot/filters.php ), and combined with the fact that (most) stars are fainter in UV, it results in the smallest telemetry load (fewest number of recorded events) for event mode data.
12:04:46 From Francesco Verrecchia to Everyone:
	Ok, that's known, so just the sensitivity, thank you
12:04:51 From Noel Klingler to Everyone:
	Reacted to "Ok, that's known, so..." with 👍
12:08:16 From Lia Corrales to Everyone:
	With the latest Swift CALDB, what’s the level of precision on the exposure maps for UVOT?
12:08:28 From Paul Kuin to Everyone:
	Replying to "Michael, why intensi..."
	
	The sky background in the uv is much lower than in the u,b,v white filters, and that reduces the telemetry.
12:08:41 From Noel Klingler to Everyone:
	Reacted to "The sky background i..." with 👍
12:08:44 From Benne Holwerda to Everyone:
	Is there a source surface brightness to exposure time calculation?
12:09:00 From Francesco Verrecchia to Everyone:
	Reacted to "The sky background i..." with 👍
12:10:03 From Noel Klingler to Everyone:
	There is a UVOT exposure time calculator hosted by MSSL here:  https://www.mssl.ucl.ac.uk/www_astro/uvot/uvot_observing/uvot_tool.html
12:10:33 From Michael Siegel to Everyone:
	Replying to "With the latest Swif..."
	
	The exposure maps show the time on target for any particular part of the image. Useful for when you stack multiple images and they don’t align. That’s very precise. The large scale sensitivity or flat field is good to <1%.
12:10:50 From Lia Corrales to Everyone:
	Reacted to "The exposure maps sh..." with 👍🏼
12:10:52 From Harsh Kumar to Everyone:
	Reacted to "The exposure maps sh..." with 👍
12:11:30 From Jithesh V to Everyone:
	Reacted to "There is a UVOT expo..." with 👍
12:11:45 From Michael Siegel to Everyone:
	Replying to "Where can I find ful..."
	
	Breeveld et al. 2011 detail this. There’s also some details in a paper by Peter Brown and in one of mine. But the filter functions available on the website include all sensitivity, including the red leak. I have found those to be the most useful in modeling it.
12:12:03 From Paul Kuin to Everyone:
	Reacted to "There is a UVOT expo..." with 👍
12:15:25 From gethr to Everyone:
	Sorry, all. Meeting intensive morning. Wasn't able to get in until now.
12:15:51 From Francesco Verrecchia to Everyone:
	Reacted to "Breeveld et al. 2011..." with 👍
12:17:01 From Benne Holwerda to Everyone:
	Replying to "Is there a source su..."
	
	I did use that before but it assumes stellar spectra and no surface brightness (this is for point sources).
12:18:03 From Lynnie Saade to Everyone:
	Should those greater than signs be less than signs?
12:22:24 From sibasish laha to Everyone:
	Funds are ONLY available to USA based PIs.
12:24:25 From labani to Everyone:
	Reacted to "Funds are ONLY avail..." with 😀
12:27:31 From Patryk Liniewicz to Everyone:
	Reacted to "Funds are ONLY avail..." with 😀
12:27:32 From Patryk Liniewicz to Everyone:
	remove 😀
12:29:11 From Lynnie Saade to Everyone:
	What about if the observation needs to be done before a proposal deadline?
12:29:21 From Lynnie Saade to Everyone:
	For another telescope I mean
12:32:02 From Jonathan Holden to Everyone:
	Were the prior submitted questions already covered?
12:32:21 From Kim Page to Everyone:
	Replying to "For another telescop..."
	
	Is this question related to the urgencies? I would hope no one would be wanting data that close in time to a deadline! 😆
12:32:27 From Priyanshu Sharma to Everyone:
	Reacted to "Funds are ONLY avail..." with 😀
12:32:29 From Priyanshu Sharma to Everyone:
	Removed a 😀 reaction from "Funds are ONLY avail..."
12:32:39 From Lynnie Saade to Everyone:
	Replying to "For another telesc..."
	
	Yes
12:33:36 From Brad Cenko to Everyone:
	Replying to "Should those greater..."
	
	The inequalities indicate where the target must be to be observable (i.e., > 46 deg from the Sun). Sorry if this was confusing.
12:33:58 From Jonathan Holden to Everyone:
	Reacted to "The inequalities ind..." with 👍
12:34:14 From rsankrit to Everyone:
	New user questions: Is there a minimum exposure time for GI proposals?  What are the approximate funding levels?
12:34:58 From Paul Kuin to Everyone:
	Replying to "What about if the ob..."
	
	You can submit a ToO anytime using the ToO requests at the Swift website. (but it does no provide funding)
12:36:46 From Kim Page to Everyone:
	Replying to "For another telescop..."
	
	Telescope deadlines will surely be known in advance, so I don't see why you would need to submit a request for observations within 24 hr (for eg). Am I misunderstanding? Also, it takes time for the data to be downlinked from the spacecraft and processed by the SDC, so  you really can't leave things too close to the deadline if the data are vital!
12:37:25 From Jonathan Holden to Everyone:
	Replying to "What about if the ob..."
	
	Do budgetary constraints, then, need to be defined in the ToO, like in a proposal?
12:38:40 From Bindu Rani to Everyone:
	Replying to "New user questions: ..."
	
	1 ks minimum. The funding is only available for US-based PIs and is ~40k for regular proposals (https://swift.gsfc.nasa.gov/proposals/swiftgi.html)
12:39:07 From Paul Kuin to Everyone:
	Replying to "What about if the ob..."
	
	How so?  The requirement is scientific relevance. not money. The data is public, so that would not make sense
12:41:07 From rsankrit to Everyone:
	Replying to "New user questions: ..."
	
	Thanks!
12:41:34 From Jonathan Holden to Everyone:
	Replying to "What about if the ob..."
	
	This was in reference to the comment on "no funding." If funding is not provided, then is that something that has to funded through the science team's existing grants?
12:42:04 From Paul Kuin to Everyone:
	Replying to "What about if the ob..."
	
	I have had HST time and needed Swift to check if HST could observe safely.
12:42:05 From Margaret Ridder to Everyone:
	Can PhD students volunteer to be panelists?
12:42:07 From Jonathan Holden to Everyone:
	Replying to "New user questions: ..."
	
	@Bindu Rani Okay, that answers the question.
12:44:41 From Paul Kuin to Everyone:
	Replying to "What about if the ob..."
	
	@Jonathan Holden perhaps this needs to be addressed by our US team.
12:44:58 From Jonathan Gelbord to Everyone:
	Replying to "New user questions: ..."
	
	I thought the minimum time per observation was lowered to 0.5 ks in cycle 21.
	
	This statement is in the description: "The requested time per observation (i.e., a single visit to a target) must be between a minimum of 0.5 ks and a maximum of 40 ks." (page 7 of ROSES appendix D5)
12:45:00 From Brad Cenko to Everyone:
	Replying to "What about if the ob..."
	
	@Jonathan Holden - Re: funding for ToO proposals. Unfortunately our budget cannot accommodate funding for them. So yes, in one sense it is dependent on the proposer’s own funding. On the other hand, the data is public immediately, and so the entire community also has the opportunity to make use of the data. Funding support is not an evaluation criteria in any way.
12:45:12 From Brad Cenko to Everyone:
	Replying to "What about if the ob..."
	
	For ToO proposals, I mean.
12:46:38 From Jonathan Holden to Everyone:
	Reacted to "For ToO proposals, I..." with 👍
12:49:18 From Brad Cenko to Bindu Rani(direct message):
	Hi Bindu - I thought we had gone down to 0.5 ks for the minimum exposure time as well (sending just to you).
12:49:25 From Bindu Rani to Everyone:
	Replying to "New user questions: ..."
	
	Yep, the number on NSPIRES is the correct one. We will update on the GI webpage. 500 seconds it is.
12:49:40 From Bindu Rani to Brad Cenko(direct message):
	Yes, that’s correct.
12:49:56 From Brad Cenko to Bindu Rani(direct message):
	Reacted to "Yes, that’s correct." with 👍
12:51:44 From Bindu Rani to Brad Cenko(direct message):
	I asked JD to update the number on the GI webpage.
12:51:57 From Brad Cenko to Bindu Rani(direct message):
	Reacted to "I asked JD to update..." with 👍
12:54:20 From Nazma Islam to Everyone:
	Would the overflow issue affect BAT transient monitor data throughout the years or is the issue more pertinent to recent observations? We do notice the data getting more noisy since 2021
12:54:45 From Francesco Verrecchia to Everyone:
	Is this panelist participation open to all scientists even not from US?
12:55:08 From Raghav Sarangi to Everyone:
	What is considered to be the most accurate Python API for the (future) trajectory of the spacecraft?
12:55:34 From Bindu Rani to Everyone:
	Replying to "Is this panelist par..."
	
	Yes, we usually have participants across the globe.
12:55:45 From Francesco Verrecchia to Everyone:
	Reacted to "Yes, we usually have..." with 👍
12:55:55 From Rick Edelson to Everyone:
	Bindu am I correct that in the upcoming Cycle 21 that the minimum visit time is now 500 s?
12:56:51 From Bindu Rani to Everyone:
	Replying to "Bindu am I correct t..."
	
	Yes, it is 500 seconds.
12:57:37 From labani to Everyone:
	Reacted to "Yes, we usually have..." with 👍
12:58:03 From Jonathan Holden to Everyone:
	Could multi-messenger observations by XRT, together with NIR or other IR spectra, help in narrowing down more precisely and quickly the origins of GRBs triggered by the BAT if/when needed?
12:59:47 From Amy Lien to Everyone:
	Replying to "Would the overflow i..."
	
	It’s only for recent years. This is a known issues, and we have done some fix to the codes years ago and clean up all those incorrect data in the transient monitor light curves. I don’t quite remember when is the last time we fixed it (maybe around 2019), so all the light curves prior to that time should be okay.  
	
	However, some problematic data points seem to appear again in recent years. We would need to look into the code to fix those (for example, maybe the original criteria we set in the code to filter out the overflown data no longer successfully filter all of those for some reasons).
13:00:13 From Bindu Rani to Everyone:
	The minimum observing time is corrected on the GI webpage now.
13:01:28 From Nazma Islam to Everyone:
	Replying to "Would the overflow i..."
	
	Thank you Amy
13:01:30 From Jonathan Holden to Everyone:
	When will the next wave of proposals happen after this next one?
13:02:01 From Simone Dichiara to Everyone:
	Replying to "Could multi-messenge..."
	
	Multi-messenger observations, together with multi-wavelegth observations (including IR spectra), would be extremely important to investigate the GRB progenitor
13:02:09 From Borja Anguiano to Everyone:
	Thank you very much!
13:02:16 From Jonathan Holden to Everyone:
	Thankyou!
13:02:16 From Laura Cotter to Everyone:
	Thank you!
13:02:18 From Ciro Pinto to Everyone:
	Thank you ver much
13:02:18 From Alicia Rouco Escorial (she/her) to Everyone:
	Thanks so much!
13:02:21 From Robin Corbet to Everyone:
	thanks
13:02:24 From Mike Moss to Everyone:
	Thank you!
13:02:25 From Jithesh V to Everyone:
	thanks
13:02:25 From Priyanshu Sharma to Everyone:
	Thank you
13:02:29 From Max De Pasquale to Everyone:
	Goodbye everyone. Thanks for arranging this meeting.
13:02:30 From kouserimam to Everyone:
	Thank you
13:02:36 From Firoza Sutaria to Everyone:
	Thank you!
13:02:43 From Niraj Kumar Sahu to Everyone:
	Thanyou.
13:02:46 From Francesco Verrecchia to Everyone:
	yj
13:02:47 From Yi-Jung Yang to Everyone:
	Thanks!
13:02:51 From Jonathan Holden to Everyone:
	Looking forward to the Q&A on the website!
13:02:52 From David Palmer to Everyone:
	Replying to "What is considered t..."
	
	There are standard propagators used by the satellite community.  The algorithm used is called ‘SGP4’.  There aren’t really any hugely better predictors.  See https://rhodesmill.org/skyfield/earth-satellites.html  for how to use them.
13:02:55 From Francesco Verrecchia to Everyone:
	thank you very much!