BEGIN:VCALENDAR
PRODID:-//Microsoft Corporation//Outlook 16.0 MIMEDIR//EN
VERSION:2.0
METHOD:REQUEST
X-MS-OLK-FORCEINSPECTOROPEN:TRUE
BEGIN:VTIMEZONE
TZID:Eastern Standard Time
BEGIN:STANDARD
DTSTART:16011104T020000
RRULE:FREQ=YEARLY;BYDAY=1SU;BYMONTH=11
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010311T020000
RRULE:FREQ=YEARLY;BYDAY=2SU;BYMONTH=3
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
<email obscured><email obscured>
<email obscured><email obscured>
<email obscured><email obscured>
CLASS:PUBLIC
CREATED:20200413T171336Z
DESCRIPTION:April 13\, 2020\n\n \n\nTo: ABRF Executive Board\n\n
CAN-CC \n\n \n\n \n\nABRF is inviting you to a scheduled Zoom meetin
g.\n\n \n\nTopic: ABRF Core Administration Virtual Town Hall\n\nTime: Apr
23\, 2020 01:00 PM Eastern Time (US and Canada)\n\n Every 2 weeks o
n Thu\, until Jul 16\, 2020\, 7 occurrence(s)\n\n Apr 23\, 2020 01:
00 PM\n\n May 7\, 2020 01:00 PM\n\n May 21\, 2020 01:00 PM\n
\n Jun 4\, 2020 01:00 PM\n\n Jun 18\, 2020 01:00 PM\n\n
Jul 2\, 2020 01:00 PM\n\n Jul 16\, 2020 01:00 PM\n\nPlease downl
oad and import the following iCalendar (.ics) files to your calendar syste
m.\n\nWeekly: https://zoom.us/meeting/tJwscOutqTMtGNA10jUro-CO2G-lN6UcewOj
/ics?icsToken=98tyKuCgrzwoH9OdtxuDRow-BY_Ca-_wtlxajY18zU_vNjJcLyDZZMUPPpwp
JdvV\n\n \n\nJoin Zoom Meeting\n\nhttps://zoom.us/j/98172578724?pwd=NkVMej
Q4eVlyUlJKVzhORWdYVG5BUT09 \n\n \n\nMeeting ID: 981 7257 8724\n\nPassword:
355302\n\nOne tap mobile\n\n+13126266799\,\,98172578724# US (Chicago)\n\n
+16465588656\,\,98172578724# US (New York)\n\n \n\nDial by your location\n
\n +1 312 626 6799 US (Chicago)\n\n +1 646 558 8656 US (New
York)\n\n +1 253 215 8782 US\n\n +1 301 715 8592 US\n\n
+1 346 248 7799 US (Houston)\n\n +1 669 900 9128 US (San Jose)\n
\nMeeting ID: 981 7257 8724\n\nFind your local number: https://zoom.us/u/a
GcwlBChI\n\n \n\n
DTEND;TZID="Eastern Standard Time":20200423T140000
DTSTAMP:20200413T171336Z
DTSTART;TZID="Eastern Standard Time":20200423T130000
LAST-MODIFIED:20200413T171336Z
LOCATION:https://zoom.us/j/98172578724?pwd=NkVMejQ4eVlyUlJKVzhORWdYVG5BUT09
<email obscured><email obscured>
PRIORITY:5
RRULE:FREQ=WEEKLY;COUNT=6;INTERVAL=2;BYDAY=TH;WKST=SU
SEQUENCE:0
SUMMARY;LANGUAGE=en-us:ABRF Core Administration Virtual Town Hall
TRANSP:OPAQUE
UID:040000008200E00074C5B7101A82E00800000000C0EA6F579511D601000000000000000
010000000FE42BC8711086C45B62287FA765F1A1D
X-ALT-DESC;FMTTYPE=text/html:<html xmlns:v="urn:schemas-microsoft-com:vml"
xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-mic
rosoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/
12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Co
ntent-Type content="text/html\; charset=us-ascii"><meta name=Generator con
tent="Microsoft Word 15 (filtered medium)"><style><!--\n/* Font Definition
s */\n@font-face\n {font-family:"Cambria Math"\;\n panose-1:2 4 5 3 5 4 6
3 2 4\;}\n@font-face\n {font-family:Calibri\;\n panose-1:2 15 5 2 2 2 4 3
2 4\;}\n/* Style Definitions */\np.MsoNormal\, li.MsoNormal\, div.MsoNorma
l\n {margin:0in\;\n margin-bottom:.0001pt\;\n font-size:11.0pt\;\n font-fa
mily:"Calibri"\,sans-serif\;}\na:link\, span.MsoHyperlink\n {mso-style-pri
ority:99\;\n color:#0563C1\;\n text-decoration:underline\;}\nspan.EmailSty
le18\n {mso-style-type:personal-compose\;\n font-family:"Arial"\,sans-seri
f\;\n color:windowtext\;}\n.MsoChpDefault\n {mso-style-type:export-only\;\
n font-size:10.0pt\;}\n@page WordSection1\n {size:8.5in 11.0in\;\n margin:
1.0in 1.0in 1.0in 1.0in\;}\ndiv.WordSection1\n {page:WordSection1\;}\n--><
/style><!--[if gte mso 9]><xml>\n<o:shapedefaults v:ext="edit" spidmax="10
26" />\n</xml><![endif]--><!--[if gte mso 9]><xml>\n<o:shapelayout v:ext="
edit">\n<o:idmap v:ext="edit" data="1" />\n</o:shapelayout></xml><![endif]
--></head><body lang=EN-US link="#0563C1" vlink="#954F72"><div class=WordS
ection1><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"Ari
al"\,sans-serif'>April 13\, 2020<o:p></o:p></span></p><p class=MsoNormal><
span style='font-size:12.0pt\;font-family:"Arial"\,sans-serif'><o:p> \
;</o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt\;font-f
amily:"Arial"\,sans-serif'>To: \;  \; \; \; ABRF Executive
Board<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0
pt\;font-family:"Arial"\,sans-serif'> \; \; \; \; \;&n
bsp\; \; \; \; \; \; CAN-CC <o:p></o:p></span></p><p c
lass=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial"\,sans-se
rif'><o:p> \;</o:p></span></p><p class=MsoNormal><span style='font-siz
e:12.0pt\;font-family:"Arial"\,sans-serif'><o:p> \;</o:p></span></p><p
class=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial"\,sans-
serif'>ABRF is inviting you to a scheduled Zoom meeting.<o:p></o:p></span>
</p><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial"\
,sans-serif'><o:p> \;</o:p></span></p><p class=MsoNormal><span style='
font-size:12.0pt\;font-family:"Arial"\,sans-serif'>Topic: ABRF Core Admini
stration Virtual Town Hall<o:p></o:p></span></p><p class=MsoNormal><span s
tyle='font-size:12.0pt\;font-family:"Arial"\,sans-serif'>Time: Apr 23\, 20
20 01:00 PM Eastern Time (US and Canada)<o:p></o:p></span></p><p class=Mso
Normal><span style='font-size:12.0pt\;font-family:"Arial"\,sans-serif'>&nb
sp\; \; \; \; \; \; \; Every 2 weeks on Thu\, unti
l Jul 16\, 2020\, 7 occurrence(s)<o:p></o:p></span></p><p class=MsoNormal>
<span style='font-size:12.0pt\;font-family:"Arial"\,sans-serif'> \;&nb
sp\; \; \; \; \; \; Apr 23\, 2020 01:00 PM<o:p></o:p><
/span></p><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"A
rial"\,sans-serif'> \; \; \; \; \; \; \; May 7
\, 2020 01:00 PM<o:p></o:p></span></p><p class=MsoNormal><span style='font
-size:12.0pt\;font-family:"Arial"\,sans-serif'> \; \; \; \
; \; \; \; May 21\, 2020 01:00 PM<o:p></o:p></span></p><p clas
s=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial"\,sans-serif
'> \; \; \; \; \; \; \; Jun 4\, 2020 01:00 PM<
o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt\;fon
t-family:"Arial"\,sans-serif'> \; \; \; \; \; \;&n
bsp\; Jun 18\, 2020 01:00 PM<o:p></o:p></span></p><p class=MsoNormal><span
style='font-size:12.0pt\;font-family:"Arial"\,sans-serif'> \; \;&
nbsp\; \; \; \; \; Jul 2\, 2020 01:00 PM<o:p></o:p></span>
</p><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial"\
,sans-serif'> \; \; \; \; \; \; \; Jul 16\, 20
20 01:00 PM<o:p></o:p></span></p><p class=MsoNormal><span style='font-size
:12.0pt\;font-family:"Arial"\,sans-serif'>Please download and import the f
ollowing iCalendar (.ics) files to your calendar system.<o:p></o:p></span>
</p><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial"\
,sans-serif'>Weekly: <a href="https://zoom.us/meeting/tJwscOutqTMtGNA10jUr
o-CO2G-lN6UcewOj/ics?icsToken=98tyKuCgrzwoH9OdtxuDRow-BY_Ca-_wtlxajY18zU_v
NjJcLyDZZMUPPpwpJdvV">https://zoom.us/meeting/tJwscOutqTMtGNA10jUro-CO2G-l
N6UcewOj/ics?icsToken=98tyKuCgrzwoH9OdtxuDRow-BY_Ca-_wtlxajY18zU_vNjJcLyDZ
ZMUPPpwpJdvV</a><o:p></o:p></span></p><p class=MsoNormal><span style='font
-size:12.0pt\;font-family:"Arial"\,sans-serif'><o:p> \;</o:p></span></
p><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial"\,s
ans-serif'>Join Zoom Meeting<o:p></o:p></span></p><p class=MsoNormal><span
style='font-size:12.0pt\;font-family:"Arial"\,sans-serif'><a href="https:
//zoom.us/j/98172578724?pwd=NkVMejQ4eVlyUlJKVzhORWdYVG5BUT09">https://zoom
.us/j/98172578724?pwd=NkVMejQ4eVlyUlJKVzhORWdYVG5BUT09</a> <o:p></o:p></sp
an></p><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"Aria
l"\,sans-serif'><o:p> \;</o:p></span></p><p class=MsoNormal><span styl
e='font-size:12.0pt\;font-family:"Arial"\,sans-serif'>Meeting ID: 981 7257
8724<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0p
t\;font-family:"Arial"\,sans-serif'>Password: 355302<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial"\,san
s-serif'>One tap mobile<o:p></o:p></span></p><p class=MsoNormal><span styl
e='font-size:12.0pt\;font-family:"Arial"\,sans-serif'>+13126266799\,\,9817
2578724# US (Chicago)<o:p></o:p></span></p><p class=MsoNormal><span style=
'font-size:12.0pt\;font-family:"Arial"\,sans-serif'>+16465588656\,\,981725
78724# US (New York)<o:p></o:p></span></p><p class=MsoNormal><span style='
font-size:12.0pt\;font-family:"Arial"\,sans-serif'><o:p> \;</o:p></spa
n></p><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial
"\,sans-serif'>Dial by your location<o:p></o:p></span></p><p class=MsoNorm
al><span style='font-size:12.0pt\;font-family:"Arial"\,sans-serif'> \;
 \; \; \; \; \; \; +1 312 626 6799 US (Chicago)<o:
p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0pt\;font-
family:"Arial"\,sans-serif'> \; \; \; \; \; \;&nbs
p\; +1 646 558 8656 US (New York)<o:p></o:p></span></p><p class=MsoNormal>
<span style='font-size:12.0pt\;font-family:"Arial"\,sans-serif'> \;&nb
sp\; \; \; \; \; \; +1 253 215 8782 US<o:p></o:p></spa
n></p><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial
"\,sans-serif'> \; \; \; \; \; \; \; +1 301 71
5 8592 US<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:1
2.0pt\;font-family:"Arial"\,sans-serif'> \; \; \; \; \
; \; \; +1 346 248 7799 US (Houston)<o:p></o:p></span></p><p class
=MsoNormal><span style='font-size:12.0pt\;font-family:"Arial"\,sans-serif'
> \; \; \; \; \; \; \; +1 669 900 9128 US (San
Jose)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:12.0
pt\;font-family:"Arial"\,sans-serif'>Meeting ID: 981 7257 8724<o:p></o:p><
/span></p><p class=MsoNormal><span style='font-size:12.0pt\;font-family:"A
rial"\,sans-serif'>Find your local number: <a href="https://zoom.us/u/aGcw
lBChI">https://zoom.us/u/aGcwlBChI</a><o:p></o:p></span></p><p class=MsoNo
rmal><span style='font-size:12.0pt\;font-family:"Arial"\,sans-serif'><o:p>
 \;</o:p></span></p></div></body></html>
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-DISALLOW-COUNTER:FALSE
X-MS-OLK-AUTOSTARTCHECK:FALSE
X-MS-OLK-CONFTYPE:0
<email obscured><email obscured>
.org
Rest of post
BEGIN:VALARM
TRIGGER:-PT15M
ACTION:DISPLAY
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
Has anyone used Teamviewer to let users access data analysis workstations
remotely? In anticipation of needing to maintain social distancing for the
foreseeable future, we are looking at various ways of letting people analyze
their data from remote locations.
Natasha
Natasha Nikolaidis
Center Operations Manager
Bindley Bioscience Center
Discovery Park, Purdue University
P: 765-494-5997
C: 765-491-8524
<email obscured><email obscured>>
Thanks very much to each of you for your replies and insights!
Tom McHugh
I should have noted that the Adam devices are supported by iLab.
Chris
He/Him/His
Christopher J. Gilpin Ph.D.
Director, Life Science Microscopy Facility
Purdue University
Whistler Hall of Agriculture Research, Room S052
170 S. University St
West Lafayette, IN 47907
765-494-7750
<email obscured>
<email obscured> reaches everyone in the facility
Rest of post
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
Aaron J Rosen
Sent: Wednesday, April 8, 2020 10:37 AM
To: <email obscured>
Subject: Re: [core administrators network forum] iLab & Hardware interlocks for
autoclaves?
There is another variety of interlock/relays produced by a company called
DataProbe that uses low-voltage signal wire to control "slave" devices. A
master box such as this:
http://store.dataprobe.com/ipio-8
Can be connected to up to 8 "slave" devices such as this:
http://store.dataprobe.com/iboot-io-off
At the end of the day, these "slave" devices are effectively identical to
Synaccess relays (i.e. glorified, internet-controlled power strips).
However, a number of engineering-based cores at Northwestern have used the
two-prong signal wire connections from the master box, and directly connected
these circuits to very specific "necessary but not absolutely critical"
components in a variety of devices, such that the particular port for the
master box must be switched on for the equipment to operate. Obviously, the
engineers that decide what component to interrupt with these interrupt circuits
are deeply familiar with their equipment (more than a dozen tools in our
microfabrication core are wired up with these interrupts). The cores that have
setup their equipment this way have all been pleased with the results.
I have been advocating for iLab to support DataProbe hardware for a while, as I
want to ensure that the company continues to thrive (for entirely
institutionally selfish reasons). I will note that we have found these devices
to be generally more stable than Synaccess devices. Once behind a protected
firewall, they simply don't go down. Additionally, a single master box can be
controlled with a single internet connection, allowing up to 16 "slave" devices
to be controlled with one port and a whole bunch of low voltage signal wire.
This has saved us a whole lot of time and expense obviating the need to wire up
new campus network panels in many facilities.
If there's a group of iLab users interested in this functionality, I would
suggest getting together to lobby iLab to support Dataprobe hardware
(iPIO-series). They are more likely to listen to you than to me (a
non-customer).
Aaron
ο»ΏOn 4/8/20, 8:42 AM, "Core Administrators Network Forum on behalf of
Nikolaidis, Natasha N" <email obscured> on behalf of <email obscured>>
wrote:
I've forwarded this email thread to Hugh.
We've also considered placing our autoclaves on interlocks in order to
track usage, but haven't found an easy way to make it work, for all the reasons
listed below.
Natasha
Natasha Nikolaidis
Center Operations Manager
Bindley Bioscience Center
Discovery Park, Purdue University
P: 765-494-5997
C: 765-491-8524
<email obscured>
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
Matt DeVries
Sent: Wednesday, April 8, 2020 9:24 AM
To: Core Administrators Network Forum <email obscured>>
Subject: Re: [core administrators network forum] iLab & Hardware interlocks
for autoclaves?
I'm sure you're aware, iLab (and any sane person) very much recommends NOT
connecting the SysAccess interlocks to anything but
cheap(ish)(comparatively) computer monitors that run equipment, rather than
directly to equipment as the SynAccess devices are essentially just power
strips that are cycling power on and off to the device, which could damage
sensitive instruments, especially if you have poorly conditioned mains power
going to your buildings.
That being said, we've for the first time connected an interlock directly
to our Vitrobots, as they don't have computers that run them to which to
connect to monitors, AND (this is important) they have a very short post time
once they've been turned on (it only takes a few 10s of seconds to get to
operating conditions). FEI/Fisher's engineers swore on all holy books we could
practically find that it was rugged enough to handle the power cycling, and put
it in writing (via email).
It's working well for us so far. It has the same interlock challenges that
always exist (people bringing their own mains plug to bypass the interlock,
forcing countermeasures). We're able to track users and usage and ensure only
the trained are able to operate it.
If your autoclave vendor says your devices can be safely power-cycled many
times a day, and it goes from off to fully operational quickly, I'd imagine it
would work.
Another option is if the autoclave requires an operator's key to run, the
key can be placed in an interlock-controlled lockbox.
I've also copied Hugh Gardner (he may need to apply to be a member of CANCC
in order to reply) who has deployed interlocks in all kinds of crazy places.
*Matt DeVries MS, MS*
*Administrative Director of Core Services and Shared Resources*
*Case Western Reserve University: School of Medicine - **Office of Research
Administration*
*Case Western Reserve University: Office of Research & Technology
Management*
*216.368.1266*
<email obscured> <email obscured>>*
On Wed, Apr 8, 2020 at 9:10 AM tmchugh <email obscured>> wrote:
> INTER-LOCKS and AUTOCLAVES???
>
> Has anyone tried managing (tracking) the use of autoclaves with iLab
> and hardware interlocks?
>
> Before the changes in operations took hold due to COVID19 I was
> starting to kick-around the feasibility of this.
>
> Wondering if anyone has tried this
>
> Tom McHugh
> <email obscured>
> University of Maryland School of Medicine) ββ View topic
>
https://urldefense.com/v3/__http://list.abrf.org/r/topic/6JpSiVWrZ6Sc4tvYz6SDBS__;!!Dq0X2DkFhyF93HkjWTBQKhk!Hb7XlQycin_TogOAL7GGZMMws-vUInrCcu4G4gOx9QR2ka0Tc9F7ftwlRTPLoFFgBH6M1_Rb$
> Leave group <email obscured>?Subject=Unsubscribe
>
>
ββ
View topic
https://urldefense.com/v3/__http://list.abrf.org/r/topic/vXxBGvcjheBX8tssNq78h__;!!Dq0X2DkFhyF93HkjWTBQKhk!Hb7XlQycin_TogOAL7GGZMMws-vUInrCcu4G4gOx9QR2ka0Tc9F7ftwlRTPLoFFgBHuKX6Qx$
Leave group <email obscured>?Subject=Unsubscribe
ββ
View topic
https://urldefense.com/v3/__http://list.abrf.org/r/topic/3vbAzc0D2vGDzCCv4TJvv5__;!!Dq0X2DkFhyF93HkjWTBQKhk!Hb7XlQycin_TogOAL7GGZMMws-vUInrCcu4G4gOx9QR2ka0Tc9F7ftwlRTPLoFFgBGmG6gj9$
Leave group <email obscured>?Subject=Unsubscribe
ββ
View topic http://list.abrf.org/r/topic/37rVxnULRP0uAF1xuNJTaH
Leave group <email obscured>?Subject=Unsubscribe
Aaron,
This device looks similar to the Adam 6000 series which I have used here at
Purdue. I would certainly advocate for intercepting " necessary but not
absolutely critical" parts of an instrument. E.g. I used and Adam on an old
electron microscope that was not computer controlled. I cut into the 24V line
that supplied brightness to the crt control panel. It worked very well.
Chris
He/Him/His
Christopher J. Gilpin Ph.D.
Director, Life Science Microscopy Facility
Purdue University
Whistler Hall of Agriculture Research, Room S052
170 S. University St
West Lafayette, IN 47907
765-494-7750
<email obscured>
<email obscured> reaches everyone in the facility
Rest of post
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
Aaron J Rosen
Sent: Wednesday, April 8, 2020 10:37 AM
To: <email obscured>
Subject: Re: [core administrators network forum] iLab & Hardware interlocks for
autoclaves?
There is another variety of interlock/relays produced by a company called
DataProbe that uses low-voltage signal wire to control "slave" devices. A
master box such as this:
http://store.dataprobe.com/ipio-8
Can be connected to up to 8 "slave" devices such as this:
http://store.dataprobe.com/iboot-io-off
At the end of the day, these "slave" devices are effectively identical to
Synaccess relays (i.e. glorified, internet-controlled power strips).
However, a number of engineering-based cores at Northwestern have used the
two-prong signal wire connections from the master box, and directly connected
these circuits to very specific "necessary but not absolutely critical"
components in a variety of devices, such that the particular port for the
master box must be switched on for the equipment to operate. Obviously, the
engineers that decide what component to interrupt with these interrupt circuits
are deeply familiar with their equipment (more than a dozen tools in our
microfabrication core are wired up with these interrupts). The cores that have
setup their equipment this way have all been pleased with the results.
I have been advocating for iLab to support DataProbe hardware for a while, as I
want to ensure that the company continues to thrive (for entirely
institutionally selfish reasons). I will note that we have found these devices
to be generally more stable than Synaccess devices. Once behind a protected
firewall, they simply don't go down. Additionally, a single master box can be
controlled with a single internet connection, allowing up to 16 "slave" devices
to be controlled with one port and a whole bunch of low voltage signal wire.
This has saved us a whole lot of time and expense obviating the need to wire up
new campus network panels in many facilities.
If there's a group of iLab users interested in this functionality, I would
suggest getting together to lobby iLab to support Dataprobe hardware
(iPIO-series). They are more likely to listen to you than to me (a
non-customer).
Aaron
ο»ΏOn 4/8/20, 8:42 AM, "Core Administrators Network Forum on behalf of
Nikolaidis, Natasha N" <email obscured> on behalf of <email obscured>>
wrote:
I've forwarded this email thread to Hugh.
We've also considered placing our autoclaves on interlocks in order to
track usage, but haven't found an easy way to make it work, for all the reasons
listed below.
Natasha
Natasha Nikolaidis
Center Operations Manager
Bindley Bioscience Center
Discovery Park, Purdue University
P: 765-494-5997
C: 765-491-8524
<email obscured>
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
Matt DeVries
Sent: Wednesday, April 8, 2020 9:24 AM
To: Core Administrators Network Forum <email obscured>>
Subject: Re: [core administrators network forum] iLab & Hardware interlocks
for autoclaves?
I'm sure you're aware, iLab (and any sane person) very much recommends NOT
connecting the SysAccess interlocks to anything but
cheap(ish)(comparatively) computer monitors that run equipment, rather than
directly to equipment as the SynAccess devices are essentially just power
strips that are cycling power on and off to the device, which could damage
sensitive instruments, especially if you have poorly conditioned mains power
going to your buildings.
That being said, we've for the first time connected an interlock directly
to our Vitrobots, as they don't have computers that run them to which to
connect to monitors, AND (this is important) they have a very short post time
once they've been turned on (it only takes a few 10s of seconds to get to
operating conditions). FEI/Fisher's engineers swore on all holy books we could
practically find that it was rugged enough to handle the power cycling, and put
it in writing (via email).
It's working well for us so far. It has the same interlock challenges that
always exist (people bringing their own mains plug to bypass the interlock,
forcing countermeasures). We're able to track users and usage and ensure only
the trained are able to operate it.
If your autoclave vendor says your devices can be safely power-cycled many
times a day, and it goes from off to fully operational quickly, I'd imagine it
would work.
Another option is if the autoclave requires an operator's key to run, the
key can be placed in an interlock-controlled lockbox.
I've also copied Hugh Gardner (he may need to apply to be a member of CANCC
in order to reply) who has deployed interlocks in all kinds of crazy places.
*Matt DeVries MS, MS*
*Administrative Director of Core Services and Shared Resources*
*Case Western Reserve University: School of Medicine - **Office of Research
Administration*
*Case Western Reserve University: Office of Research & Technology
Management*
*216.368.1266*
<email obscured> <email obscured>>*
On Wed, Apr 8, 2020 at 9:10 AM tmchugh <email obscured>> wrote:
> INTER-LOCKS and AUTOCLAVES???
>
> Has anyone tried managing (tracking) the use of autoclaves with iLab
> and hardware interlocks?
>
> Before the changes in operations took hold due to COVID19 I was
> starting to kick-around the feasibility of this.
>
> Wondering if anyone has tried this
>
> Tom McHugh
> <email obscured>
> University of Maryland School of Medicine) ββ View topic
>
https://urldefense.com/v3/__http://list.abrf.org/r/topic/6JpSiVWrZ6Sc4tvYz6SDBS__;!!Dq0X2DkFhyF93HkjWTBQKhk!Hb7XlQycin_TogOAL7GGZMMws-vUInrCcu4G4gOx9QR2ka0Tc9F7ftwlRTPLoFFgBH6M1_Rb$
> Leave group <email obscured>?Subject=Unsubscribe
>
>
ββ
View topic
https://urldefense.com/v3/__http://list.abrf.org/r/topic/vXxBGvcjheBX8tssNq78h__;!!Dq0X2DkFhyF93HkjWTBQKhk!Hb7XlQycin_TogOAL7GGZMMws-vUInrCcu4G4gOx9QR2ka0Tc9F7ftwlRTPLoFFgBHuKX6Qx$
Leave group <email obscured>?Subject=Unsubscribe
ββ
View topic
https://urldefense.com/v3/__http://list.abrf.org/r/topic/3vbAzc0D2vGDzCCv4TJvv5__;!!Dq0X2DkFhyF93HkjWTBQKhk!Hb7XlQycin_TogOAL7GGZMMws-vUInrCcu4G4gOx9QR2ka0Tc9F7ftwlRTPLoFFgBGmG6gj9$
Leave group <email obscured>?Subject=Unsubscribe
ββ
View topic http://list.abrf.org/r/topic/37rVxnULRP0uAF1xuNJTaH
Leave group <email obscured>?Subject=Unsubscribe
There is another variety of interlock/relays produced by a company called
DataProbe that uses low-voltage signal wire to control "slave" devices. A
master box such as this:
http://store.dataprobe.com/ipio-8
Can be connected to up to 8 "slave" devices such as this:
http://store.dataprobe.com/iboot-io-off
At the end of the day, these "slave" devices are effectively identical to
Synaccess relays (i.e. glorified, internet-controlled power strips).
However, a number of engineering-based cores at Northwestern have used the
two-prong signal wire connections from the master box, and directly connected
these circuits to very specific "necessary but not absolutely critical"
components in a variety of devices, such that the particular port for the
master box must be switched on for the equipment to operate. Obviously, the
engineers that decide what component to interrupt with these interrupt circuits
are deeply familiar with their equipment (more than a dozen tools in our
microfabrication core are wired up with these interrupts). The cores that have
setup their equipment this way have all been pleased with the results.
I have been advocating for iLab to support DataProbe hardware for a while, as I
want to ensure that the company continues to thrive (for entirely
institutionally selfish reasons). I will note that we have found these devices
to be generally more stable than Synaccess devices. Once behind a protected
firewall, they simply don't go down. Additionally, a single master box can be
controlled with a single internet connection, allowing up to 16 "slave" devices
to be controlled with one port and a whole bunch of low voltage signal wire.
This has saved us a whole lot of time and expense obviating the need to wire up
new campus network panels in many facilities.
If there's a group of iLab users interested in this functionality, I would
suggest getting together to lobby iLab to support Dataprobe hardware
(iPIO-series). They are more likely to listen to you than to me (a
non-customer).
Aaron
ο»ΏOn 4/8/20, 8:42 AM, "Core Administrators Network Forum on behalf of
Nikolaidis, Natasha N" <email obscured> on behalf of <email obscured>>
wrote:
I've forwarded this email thread to Hugh.
We've also considered placing our autoclaves on interlocks in order to
track usage, but haven't found an easy way to make it work, for all the reasons
listed below.
Natasha
Natasha Nikolaidis
Center Operations Manager
Bindley Bioscience Center
Discovery Park, Purdue University
P: 765-494-5997
C: 765-491-8524
<email obscured>
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
Matt DeVries
Sent: Wednesday, April 8, 2020 9:24 AM
To: Core Administrators Network Forum <email obscured>>
Subject: Re: [core administrators network forum] iLab & Hardware interlocks
for autoclaves?
I'm sure you're aware, iLab (and any sane person) very much recommends NOT
connecting the SysAccess interlocks to anything but
cheap(ish)(comparatively) computer monitors that run equipment, rather than
directly to equipment as the SynAccess devices are essentially just power
strips that are cycling power on and off to the device, which could damage
sensitive instruments, especially if you have poorly conditioned mains power
going to your buildings.
That being said, we've for the first time connected an interlock directly
to our Vitrobots, as they don't have computers that run them to which to
connect to monitors, AND (this is important) they have a very short post time
once they've been turned on (it only takes a few 10s of seconds to get to
operating conditions). FEI/Fisher's engineers swore on all holy books we could
practically find that it was rugged enough to handle the power cycling, and put
it in writing (via email).
It's working well for us so far. It has the same interlock challenges that
always exist (people bringing their own mains plug to bypass the interlock,
forcing countermeasures). We're able to track users and usage and ensure only
the trained are able to operate it.
If your autoclave vendor says your devices can be safely power-cycled many
times a day, and it goes from off to fully operational quickly, I'd imagine it
would work.
Another option is if the autoclave requires an operator's key to run, the
key can be placed in an interlock-controlled lockbox.
I've also copied Hugh Gardner (he may need to apply to be a member of CANCC
in order to reply) who has deployed interlocks in all kinds of crazy places.
*Matt DeVries MS, MS*
*Administrative Director of Core Services and Shared Resources*
*Case Western Reserve University: School of Medicine - **Office of Research
Administration*
*Case Western Reserve University: Office of Research & Technology
Management*
*216.368.1266*
<email obscured> <email obscured>>*
On Wed, Apr 8, 2020 at 9:10 AM tmchugh <email obscured>> wrote:
> INTER-LOCKS and AUTOCLAVES???
>
> Has anyone tried managing (tracking) the use of autoclaves with iLab
> and hardware interlocks?
>
> Before the changes in operations took hold due to COVID19 I was
> starting to kick-around the feasibility of this.
>
> Wondering if anyone has tried this
>
> Tom McHugh
> <email obscured>
> University of Maryland School of Medicine) ββ View topic
>
https://urldefense.com/v3/__http://list.abrf.org/r/topic/6JpSiVWrZ6Sc4tvYz6SDBS__;!!Dq0X2DkFhyF93HkjWTBQKhk!Hb7XlQycin_TogOAL7GGZMMws-vUInrCcu4G4gOx9QR2ka0Tc9F7ftwlRTPLoFFgBH6M1_Rb$
> Leave group <email obscured>?Subject=Unsubscribe
>
>
ββ
View topic
https://urldefense.com/v3/__http://list.abrf.org/r/topic/vXxBGvcjheBX8tssNq78h__;!!Dq0X2DkFhyF93HkjWTBQKhk!Hb7XlQycin_TogOAL7GGZMMws-vUInrCcu4G4gOx9QR2ka0Tc9F7ftwlRTPLoFFgBHuKX6Qx$
Leave group <email obscured>?Subject=Unsubscribe
ββ
View topic
https://urldefense.com/v3/__http://list.abrf.org/r/topic/3vbAzc0D2vGDzCCv4TJvv5__;!!Dq0X2DkFhyF93HkjWTBQKhk!Hb7XlQycin_TogOAL7GGZMMws-vUInrCcu4G4gOx9QR2ka0Tc9F7ftwlRTPLoFFgBGmG6gj9$
Leave group <email obscured>?Subject=Unsubscribe
I've forwarded this email thread to Hugh.
We've also considered placing our autoclaves on interlocks in order to track
usage, but haven't found an easy way to make it work, for all the reasons
listed below.
Natasha
Natasha Nikolaidis
Center Operations Manager
Bindley Bioscience Center
Discovery Park, Purdue University
P: 765-494-5997
C: 765-491-8524
<email obscured>
Rest of post
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of Matt
DeVries
Sent: Wednesday, April 8, 2020 9:24 AM
To: Core Administrators Network Forum <email obscured>>
Subject: Re: [core administrators network forum] iLab & Hardware interlocks for
autoclaves?
I'm sure you're aware, iLab (and any sane person) very much recommends NOT
connecting the SysAccess interlocks to anything but
cheap(ish)(comparatively) computer monitors that run equipment, rather than
directly to equipment as the SynAccess devices are essentially just power
strips that are cycling power on and off to the device, which could damage
sensitive instruments, especially if you have poorly conditioned mains power
going to your buildings.
That being said, we've for the first time connected an interlock directly to
our Vitrobots, as they don't have computers that run them to which to connect
to monitors, AND (this is important) they have a very short post time once
they've been turned on (it only takes a few 10s of seconds to get to operating
conditions). FEI/Fisher's engineers swore on all holy books we could
practically find that it was rugged enough to handle the power cycling, and put
it in writing (via email).
It's working well for us so far. It has the same interlock challenges that
always exist (people bringing their own mains plug to bypass the interlock,
forcing countermeasures). We're able to track users and usage and ensure only
the trained are able to operate it.
If your autoclave vendor says your devices can be safely power-cycled many
times a day, and it goes from off to fully operational quickly, I'd imagine it
would work.
Another option is if the autoclave requires an operator's key to run, the key
can be placed in an interlock-controlled lockbox.
I've also copied Hugh Gardner (he may need to apply to be a member of CANCC in
order to reply) who has deployed interlocks in all kinds of crazy places.
*Matt DeVries MS, MS*
*Administrative Director of Core Services and Shared Resources*
*Case Western Reserve University: School of Medicine - **Office of Research
Administration*
*Case Western Reserve University: Office of Research & Technology
Management*
*216.368.1266*
<email obscured> <email obscured>>*
On Wed, Apr 8, 2020 at 9:10 AM tmchugh <email obscured>> wrote:
> INTER-LOCKS and AUTOCLAVES???
>
> Has anyone tried managing (tracking) the use of autoclaves with iLab
> and hardware interlocks?
>
> Before the changes in operations took hold due to COVID19 I was
> starting to kick-around the feasibility of this.
>
> Wondering if anyone has tried this
>
> Tom McHugh
> <email obscured>
> University of Maryland School of Medicine) ββ View topic
> http://list.abrf.org/r/topic/6JpSiVWrZ6Sc4tvYz6SDBS
> Leave group <email obscured>?Subject=Unsubscribe
>
>
ββ
View topic http://list.abrf.org/r/topic/vXxBGvcjheBX8tssNq78h
Leave group <email obscured>?Subject=Unsubscribe
I'm sure you're aware, iLab (and any sane person) very much recommends NOT
connecting the SysAccess interlocks to anything but
cheap(ish)(comparatively) computer monitors that run equipment, rather than
directly to equipment as the SynAccess devices are essentially just power
strips that are cycling power on and off to the device, which could damage
sensitive instruments, especially if you have poorly conditioned mains
power going to your buildings.
That being said, we've for the first time connected an interlock directly
to our Vitrobots, as they don't have computers that run them to which to
connect to monitors, AND (this is important) they have a very short post
time once they've been turned on (it only takes a few 10s of seconds to get
to operating conditions). FEI/Fisher's engineers swore on all holy books we
could practically find that it was rugged enough to handle the power
cycling, and put it in writing (via email).
It's working well for us so far. It has the same interlock challenges that
always exist (people bringing their own mains plug to bypass the interlock,
forcing countermeasures). We're able to track users and usage and ensure
only the trained are able to operate it.
If your autoclave vendor says your devices can be safely power-cycled many
times a day, and it goes from off to fully operational quickly, I'd imagine
it would work.
Another option is if the autoclave requires an operator's key to run, the
key can be placed in an interlock-controlled lockbox.
I've also copied Hugh Gardner (he may need to apply to be a member of CANCC
in order to reply) who has deployed interlocks in all kinds of crazy
places.
*Matt DeVries MS, MS*
*Administrative Director of Core Services and Shared Resources*
*Case Western Reserve University: School of Medicine - **Office of Research
Administration*
*Case Western Reserve University: Office of Research & Technology
Management*
*216.368.1266*
<email obscured> <email obscured>>*
Rest of post
On Wed, Apr 8, 2020 at 9:10 AM tmchugh <email obscured>> wrote:
> INTER-LOCKS and AUTOCLAVES???
>
> Has anyone tried managing (tracking) the use of autoclaves with iLab and
> hardware interlocks?
>
> Before the changes in operations took hold due to COVID19 I was starting
> to kick-around the feasibility of this.
>
> Wondering if anyone has tried this
>
> Tom McHugh
> <email obscured>
> University of Maryland School of Medicine)
> ββ
> View topic http://list.abrf.org/r/topic/6JpSiVWrZ6Sc4tvYz6SDBS
> Leave group <email obscured>?Subject=Unsubscribe
>
>
INTER-LOCKS and AUTOCLAVES???
Has anyone tried managing (tracking) the use of autoclaves with iLab and
hardware interlocks?
Before the changes in operations took hold due to COVID19 I was starting to
kick-around the feasibility of this.
Wondering if anyone has tried this
Tom McHugh
<email obscured>
University of Maryland School of Medicine)
[cid:4fae544c-dc02-4d76-944d-701c6c8a0403]
A silver lining in these challenging times is the opportunity to take time to
learn something new from the safety of our homes. We at SUMS are grateful to
have the time to generate online content that we trust will be useful to you
both now and in the future.
Bring your questions and some lunch, and join us online at noon on Thursdays
for the next four installments of our Mass Spec Fundamentals series. Zoom
connection info will be sent to you upon free registration.
Thursday April 9, 2020
Fundamentals: Intact protein mass spectrometry - tips and best practices
Speaker: Theresa McLaughlin, MS - SUMS
register
here<https://stanford.zoom.us/webinar/register/1615850744262/WN_Qp6QmWqNQ7-ddvy2WD2F0Q>
Thursday April 16, 2020
Fundamentals: New proteomic approaches and essential data handling tips
Speaker: Kratika Singhal; Rowan Matney, BA - SUMS
register
here<https://stanford.zoom.us/webinar/register/4715858420235/WN_x1IUkca-R8O5KyJaJOLdMg>
Thursday April 23, 2020
Fundamentals: Measuring concentrations of small molecules using mass
spectrometry, Part II - Practice
Speaker: Karolina Krasinska, MS - SUMS
register
here<https://stanford.zoom.us/webinar/register/4815858431479/WN_yKRaP-eDRwSL2HgdGe93Ug>
Thursday April 30, 2020
Fundamentals: Peptide quantitation strategies
Speaker: Fang Liu, PhD; Beryl Xia, PhD - SUMS
register
here<https://stanford.zoom.us/webinar/register/7015858430912/WN_WpwlxCHdSjmCvQWqMisGjQ>
Previous webinars are available on-demand, through their listings on the SUMS
Events page.<https://mass-spec.stanford.edu/events> Feel free to send
questions, feedback and ideas for future seminars to us at
<email obscured><email obscured>>.
Stay safe, physically distant, and socially connected!
Best,
Allis
COVID-19 update more info<https://mass-spec.stanford.edu/covid-19>
In compliance with the ongoing "shelter in place" order, SUMS has ceased
laboratory operations. Our staff remain available for discussions, data
analysis, manuscript preparation, etc.
SUMS Seminar Series more info<https://mass-spec.stanford.edu/events>
Now online! Join us via Zoom on Thursdays
Rest of post
____________________________________________________________
Allis Chien, Ph.D.
Director, Stanford University Mass Spectrometry
Vincent Coates Foundation Mass Spectrometry Laboratory
Stanford Cancer Institute Proteomics Shared Resource
Bass Biology Building, room 024 | 327 Campus Drive | Stanford, CA 94305
<email obscured><email obscured><email obscured>>
| 650.723.0710 | http://mass-spec.stanford.edu<http://mass-spec.stanford.edu>
____________________________________________________________
Hello Annabelle,
In fact, on today's "town hall" meeting that Rich led, he announced that we
will create a page on the ABRF web site to include all of the COVID related
resources and activities in one location. We should have this in place
shortly.
Thank you.
Rest of post
Ken
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
Stein, Annabelle
Sent: Wednesday, March 25, 2020 3:04 PM
To: <email obscured>' <email obscured>>
Subject: Re: [core administrators network forum] List of Webinars etc?
Maybe we can set up a page on the ABRF website members only content area to
list all these various activities?
Annabelle Stein
Associate Director, Office of Research Technologies University of North
Carolina Chapel Hill CB #7064, Brinkhous-Bullitt Bldg
919-843-9554
Visit our website at www.med.unc.edu/corefacilities
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
White, Amanda (Nicole)
Sent: Tuesday, March 24, 2020 9:10 AM
To: <email obscured>
Subject: Re: [core administrators network forum] List of Webinars etc?
CTYO Tutorials are also all free at this time (Flow Cytometry)
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
JoshRappo
Sent: Tuesday, March 24, 2020 8:07 AM
To: <email obscured>
Subject: [core administrators network forum] List of Webinars etc?
Hi all:
Given Rich's email yesterday, why don't we start listing potentially
interesting webinars and other online events here?
In case anyone missed it, the ABRF is hosting a Zoom meeting (every?) Weds at
1pm EST starting tomorrow. Here is the link:
https://zoom.us/j/163095953
Beyond that here are a few more webinars etc running in the coming days:
Advaita Bioinformatics:
https://register.gotowebinar.com/register/4341821190461366029
FormLabs 3D Printing:
https://3d.formlabs.com/webinar-introducing-tough-2000?utm_source=direct&utm_medium=email&utm_campaign=webinar-tough-2000-personal-note-long
A bunch from Agilent (including historical repository):
https://www.agilent.com/en/training-events/eseminars
Also from Agilent - a series focusing on lab/instrument shutdown (already
posted by Khale):
https://agilenteseminar.webex.com/mw3300/mywebex/default.do?nomenu=true&siteurl=agilenteseminar&service=6&rnd=0.7038286599217493&main_url=https%3A%2F%2Fagilenteseminar.webex.com%2Fec3300%2Feventcenter%2Fprogram%2FprogramDetail.do%3FtheAction%3Ddetail%26internalProgramTicket%3D4832534b000000047763433026668df0cc04255423fb6e7dfa79f1f4be689fe793a24fb3422cb02e%26siteurl%3Dagilenteseminar%26internalProgramTicketUnList%3D4832534b000000047763433026668df0cc04255423fb6e7dfa79f1f4be689fe793a24fb3422cb02e%26cProgViewID%3D1860642%26PRID%3D6854380d065cf9c8dacf47376dc95f96
Thanks
Josh
ββ
View topic http://list.abrf.org/r/topic/25aYlTXtdeJkhC5NN8oBr6
Leave group <email obscured>?Subject=Unsubscribe
ββ
View topic http://list.abrf.org/r/topic/2w5kgSrN9rLZ3NN6hnT9Rl
Leave group <email obscured>?Subject=Unsubscribe
ββ
View topic http://list.abrf.org/r/topic/3G5X3zzXGSqlcgMebv94hp
Leave group <email obscured>?Subject=Unsubscribe
Good to hear, thanks, I missed today's call due to a previous meeting
Annabelle Stein
Associate Director, Office of Research Technologies
University of North Carolina Chapel Hill
CB #7064, Brinkhous-Bullitt Bldg
919-843-9554
Visit our website at www.med.unc.edu/corefacilities
Rest of post
-----Original Message-----
From: Core Administrators Network Forum <email obscured>> On Behalf Of
JoshRappo
Sent: Wednesday, March 25, 2020 3:06 PM
To: <email obscured>
Subject: Re: [core administrators network forum] List of Webinars etc?
On the Zoom that Rich convened today it was stated that there would soon be a
corona page on the ABRF website will all these resources listed, and I already
forwarded this thread to Ken Schoppmann, who is collecting info to be posted ββ
View topic http://list.abrf.org/r/topic/6VxTk02nyDl0rvRgZsVxK2
Leave group <email obscured>?Subject=Unsubscribe
On the Zoom that Rich convened today it was stated that there would soon be a
corona page on the ABRF website will all these resources listed, and I already
forwarded this thread to Ken Schoppmann, who is collecting info to be posted
Hi all,
Our core is doing a "mass spec fundamentals" series -- see announcement below.
Stay well,
Allis
Rest of post
--------------------------------------------------------
A silver lining in these challenging times is the opportunity to take time to
learn something new. While we at SUMS are working from home, we realized not
only are we spending more time watching webinars, we also have the time to
produce webinar content for you!
Bring your questions and join us online in the coming weeks for the next three
installments of our Mass Spec Fundamentals series. Zoom connection info will
be sent to you upon free registration.
Thursday March 26, 2020
Fundamentals: Quantitation strategies in mass spectrometry-based proteomics
Speaker: Fang Liu, PhD - SUMS
register
here<https://stanford.zoom.us/webinar/register/7415850687972/WN_vcRp8v7eQKWx8YRDrBHvVg>
Thursday April 2, 2020
Fundamentals: Measuring concentrations of small molecules using mass
spectrometry - theory and practice
Speaker: Karolina Krasinska, MS - SUMS
register
here<https://stanford.zoom.us/webinar/register/3915850743671/WN_pEc96D2zSbSyeZ3cLtjT8A>
Thursday April 9, 2020
Fundamentals: Intact protein mass spectrometry - tips and best practices
Speaker: Theresa McLaughlin, MS - SUMS
register
here<https://stanford.zoom.us/webinar/register/1615850744262/WN_Qp6QmWqNQ7-ddvy2WD2F0Q>
Stay safe, physically distant, and socially connected!
Best,
Allis
COVID-19 update more info<https://mass-spec.stanford.edu/covid-19>
In compliance with the Santa Clara County "shelter in place" order, SUMS has
ceased laboratory operations. Our staff remain available for discussions, data
analysis, manuscript preparation, etc.<https://mass-spec.stanford.edu/covid-19>
SUMS Seminar Series more info<https://mass-spec.stanford.edu/events>
Now online! Join us via Zoom on select Thursdays
____________________________________________________________
Allis Chien, Ph.D.
Director, Stanford University Mass Spectrometry
Vincent Coates Foundation Mass Spectrometry Laboratory
Stanford Cancer Institute Proteomics Shared Resource
Bass Biology Building, room 024 | 327 Campus Drive | Stanford, CA 94305
<email obscured><email obscured><email obscured>>
| 650.723.0710 | http://mass-spec.stanford.edu<http://mass-spec.stanford.edu>
____________________________________________________________
________________________________
From: Core Administrators Network Forum <email obscured>> on behalf of
JoshRappo <email obscured>>
Sent: Tuesday, March 24, 2020 9:06 AM
To: <email obscured> <email obscured>>
Subject: Re: [core administrators network forum] List of Webinars etc?
One more mass spec webinar from Agilent (1pm EST today!):
https://bit.ly/2IzFjrp
ββ
View topic http://list.abrf.org/r/topic/792fHIM6s8x2p4jCOC3lQy
Leave group <email obscured>?Subject=Unsubscribe
I thought it was tomorrow
Frances
ZRC 1563
Office 646-888-2354
Mobile 516-967-0656
ο»ΏOn 3/24/20, 1:07 PM, "Core Administrators Network Forum on behalf of Andrew
Chitty" <email obscured> on behalf of <email obscured>> wrote:
Hi folks,
Did the meeting link change? Iβm the only one on.
Andy
Andy Chitty
Director | University Shared Resources
<https://www.ohsu.edu/xd/research/research-cores/>
Oregon Health and Science University
Phone: I am currently working from home - Mobile: 503.422.9347
<email obscured>
On 3/24/20, 5:07 AM, "Core Administrators Network Forum on behalf of
JoshRappo" <email obscured> on behalf of <email obscured>> wrote:
Hi all:
Given Rich's email yesterday, why don't we start listing potentially
interesting webinars and other online events here?
In case anyone missed it, the ABRF is hosting a Zoom meeting (every?)
Weds at 1pm EST starting tomorrow. Here is the link:
https://zoom.us/j/163095953
Beyond that here are a few more webinars etc running in the coming
days:
Advaita Bioinformatics:
https://register.gotowebinar.com/register/4341821190461366029
FormLabs 3D Printing:
https://3d.formlabs.com/webinar-introducing-tough-2000?utm_source=direct&utm_medium=email&utm_campaign=webinar-tough-2000-personal-note-long
A bunch from Agilent (including historical repository):
https://www.agilent.com/en/training-events/eseminars
Also from Agilent - a series focusing on lab/instrument shutdown
(already posted by Khale):
https://agilenteseminar.webex.com/mw3300/mywebex/default.do?nomenu=true&siteurl=agilenteseminar&service=6&rnd=0.7038286599217493&main_url=https%3A%2F%2Fagilenteseminar.webex.com%2Fec3300%2Feventcenter%2Fprogram%2FprogramDetail.do%3FtheAction%3Ddetail%26internalProgramTicket%3D4832534b000000047763433026668df0cc04255423fb6e7dfa79f1f4be689fe793a24fb3422cb02e%26siteurl%3Dagilenteseminar%26internalProgramTicketUnList%3D4832534b000000047763433026668df0cc04255423fb6e7dfa79f1f4be689fe793a24fb3422cb02e%26cProgViewID%3D1860642%26PRID%3D6854380d065cf9c8dacf47376dc95f96
Thanks
Josh
ββ
View topic http://list.abrf.org/r/topic/25aYlTXtdeJkhC5NN8oBr6
Leave group <email obscured>?Subject=Unsubscribe
ββ
View topic http://list.abrf.org/r/topic/6l50T4AtRcn8TriHs5UDFe
Leave group <email obscured>?Subject=Unsubscribe
*** Only open attachments or links from trusted senders. Report phishing to
<email obscured> ***
Rest of post
=====================================================================
Please note that this e-mail and any files transmitted from
Memorial Sloan Kettering Cancer Center may be privileged, confidential,
and protected from disclosure under applicable law. If the reader of
this message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient,
you are hereby notified that any reading, dissemination, distribution,
copying, or other use of this communication or any of its attachments
is strictly prohibited. If you have received this communication in
error, please notify the sender immediately by replying to this message
and deleting this message, any attachments, and all copies and backups
from your computer.