diff --git a/.env b/.env index e6079ff9edfc5947458eac8e75d5b019624318cc..3b3dacf6589b3c2a54af72e326e9e398626a12a4 100644 --- a/.env +++ b/.env @@ -1,12 +1,12 @@ ENV=development -DB_USER=test +DB_USER=admin DB_PASSWORD=password DB_HOST=pg_db DB_PORT=5432 DB_NAME=push_dev -POSTGRES_USER=test +POSTGRES_USER=admin POSTGRES_PASSWORD=password POSTGRES_DB=push_dev diff --git a/docker-compose.full.yml b/docker-compose.full.yml index 24f879c4f89bee08eb24122bf178c68d74799561..ec6cc112b74916bfb27f531097797d2705099b0b 100644 --- a/docker-compose.full.yml +++ b/docker-compose.full.yml @@ -28,7 +28,7 @@ services: image: postgres volumes: - pgsql-data:/var/lib/pgsql/data:rw - - ./scripts/push_dev.sql:/docker-entrypoint-initdb.d/init.sql + - ./scripts/dump.sql:/docker-entrypoint-initdb.d/init.sql networks: - default ports: @@ -38,7 +38,7 @@ services: - POSTGRES_PASSWORD - POSTGRES_DB healthcheck: - test: ["CMD-SHELL", "pg_isready -U test -d push_dev"] + test: ["CMD-SHELL", "pg_isready -U admin -d push_dev"] interval: 10s timeout: 5s retries: 5 diff --git a/notifications_routing/data_source/data_source.py b/notifications_routing/data_source/data_source.py index 2ffba56b77955e07fa568c7789091af9b0125bcf..6557327af440118d3ffa1e0df2724b7dbe964796 100644 --- a/notifications_routing/data_source/data_source.py +++ b/notifications_routing/data_source/data_source.py @@ -8,6 +8,7 @@ class DataSource(ABC): # Keys for DataSource responses USER_ID = "user_id" + USERNAME = "username" EMAIL = "email" GROUP_ID = "group_id" PREFERENCES = "preferences" diff --git a/notifications_routing/data_source/postgres/postgres_data_source.py b/notifications_routing/data_source/postgres/postgres_data_source.py index f3ceb5011c275991f29aed4e4f82a43686359b59..e6f8fb6b1fd6700ed21141ede65893fe38505954 100644 --- a/notifications_routing/data_source/postgres/postgres_data_source.py +++ b/notifications_routing/data_source/postgres/postgres_data_source.py @@ -60,8 +60,13 @@ class PostgresDataSource(DataSource): raise NotFoundDataSourceError(Channel, id=channel_id) for member in channel.members: - logging.debug("adding member: %s (%s)", member.id, member.username) - channel_users.append({DataSource.USER_ID: member.id, DataSource.EMAIL: member.email}) + channel_users.append( + { + DataSource.USER_ID: member.id, + DataSource.USERNAME: member.username, + DataSource.EMAIL: member.email, + } + ) return channel_users @@ -87,7 +92,7 @@ class PostgresDataSource(DataSource): members = content["data"] for member in members: - group_users.append({DataSource.USER_ID: member["upn"], DataSource.EMAIL: member["primaryAccountEmail"]}) + group_users.append({DataSource.USERNAME: member["upn"], DataSource.EMAIL: member["primaryAccountEmail"]}) return group_users diff --git a/notifications_routing/preferences.py b/notifications_routing/preferences.py index 43e21a89c6841eac5726be80e5e726724ae25c21..d5a02ee3f0c64bc6c0cc1876c58759f2b36aaa38 100644 --- a/notifications_routing/preferences.py +++ b/notifications_routing/preferences.py @@ -4,17 +4,17 @@ from typing import Dict, List, Set import megabus +from notifications_routing.config import Config from notifications_routing.data_source.data_source import DataSource from notifications_routing.data_source.postgres.postgres_data_source import UserDailyNotification -from notifications_routing import config from .publisher import Publisher from .utils import ( OutputMessageKeys, convert_notification_email_to_json_string, convert_notification_push_to_json_string, - is_created_time_between_allowed_range, generate_daily_preference_delivery_datetime, + is_created_time_between_allowed_range, ) @@ -46,13 +46,13 @@ def get_delivery_methods_and_targets( created_timestamp, preference.rangeStart, preference.rangeEnd ) if not is_in_timewindow: - logging.debug("Skipping Preference: Not in time window. For: %s", preference.userUsername) + logging.debug("Skipping Preference: Not in time window. For: %s", preference.userId) continue if preference.notificationPriority and priority.lower() not in preference.notificationPriority.lower().split( "," ): - logging.debug("Skipping Preference: doesn't match priority. For: %s", preference.userUsername) + logging.debug("Skipping Preference: doesn't match priority. For: %s", preference.userId) continue logging.debug("Checking User Preferences method: %s", preference.type) @@ -81,7 +81,7 @@ def apply_user_preferences( for preference in delivery_methods_and_targets: logging.debug("Applying User Preferences delivery method: %s", preference.method) if preference.method == "DAILY": - delivery_datetime = generate_daily_preference_delivery_datetime(config.DAILY_FEED_TIME) + delivery_datetime = generate_daily_preference_delivery_datetime(Config.DAILY_FEED_TIME) user_daily_notification = UserDailyNotification( user[data_source.USER_ID], message[OutputMessageKeys.ID], diff --git a/notifications_routing/router.py b/notifications_routing/router.py index abbc1766b188d0bc8a85160cacc0109fe1772c78..cec5efb7b308cf450f06d3e5e659cdd2cf64fe4d 100644 --- a/notifications_routing/router.py +++ b/notifications_routing/router.py @@ -4,7 +4,7 @@ import logging import megabus -from notifications_routing import config +from notifications_routing.config import Config from notifications_routing.data_source.data_source import DataSource from notifications_routing.exceptions import NotFoundDataSourceError from notifications_routing.preferences import ( @@ -13,7 +13,7 @@ from notifications_routing.preferences import ( apply_user_preferences, get_delivery_methods_and_targets, ) -from notifications_routing.utils import InputMessageKeys, OutputMessageKeys, get_unique_elements +from notifications_routing.utils import InputMessageKeys, OutputMessageKeys # ActiveMQ @@ -55,9 +55,9 @@ class Router(megabus.Listener): try: self.process_message(self.read_message(message)) self.ack_message(headers[HEADERS_MESSAGE_ID]) - except Exception as e: - logging.critical("An exception happened while processing the message", exception=e, exc_info=True) + except Exception: self.nack_message(headers[HEADERS_MESSAGE_ID]) + logging.exception("An exception happened while processing the message") @staticmethod def read_message(message): @@ -65,15 +65,10 @@ class Router(megabus.Listener): message_json = json.loads(message) return { - str(OutputMessageKeys.CHANNEL_ID): message_json[str(InputMessageKeys.TARGET)][ - str(InputMessageKeys.CHANNEL_ID) - ], - str(OutputMessageKeys.CHANNEL_NAME): message_json[str(InputMessageKeys.TARGET)][ - str(InputMessageKeys.CHANNEL_NAME) - ], - str(OutputMessageKeys.CHANNEL_SLUG): message_json[str(InputMessageKeys.TARGET)][ - str(InputMessageKeys.CHANNEL_SLUG) - ], + str(OutputMessageKeys.ID): message_json[str(InputMessageKeys.ID)], + str(OutputMessageKeys.CHANNEL_ID): message_json[str(InputMessageKeys.TARGET)][str(InputMessageKeys.ID)], + str(OutputMessageKeys.CHANNEL_NAME): message_json[str(InputMessageKeys.TARGET)][str(InputMessageKeys.NAME)], + str(OutputMessageKeys.CHANNEL_SLUG): message_json[str(InputMessageKeys.TARGET)][str(InputMessageKeys.SLUG)], str(OutputMessageKeys.PRIORITY): message_json[str(InputMessageKeys.PRIORITY)], str(OutputMessageKeys.CREATED_TIMESTAMP): message_json[str(InputMessageKeys.SENT_AT)], str(OutputMessageKeys.MESSAGE_BODY): message_json[str(InputMessageKeys.BODY)], @@ -82,26 +77,48 @@ class Router(megabus.Listener): str(OutputMessageKeys.IMGURL): message_json[str(InputMessageKeys.IMGURL)], } - def process_message(self, message): - """Process a message according to user and default preferences and sends to available delivery channels.""" - channel_users = self.data_source.get_channel_users(message[OutputMessageKeys.CHANNEL_ID]) - channel_groups = self.data_source.get_channel_groups(message[OutputMessageKeys.CHANNEL_ID]) + def get_channel_users(self, channel_id): + """Join users from our data source and the grappa system to return a unique users list.""" + channel_users = self.data_source.get_channel_users(channel_id) + unique_usernames = [username for username in channel_users] + logging.debug("channel %s usernames: %s", channel_id, unique_usernames) + + channel_groups = self.data_source.get_channel_groups(channel_id) + logging.debug("channel %s groups %s", channel_id, channel_groups) if channel_groups: for group in channel_groups: for group_id in group.values(): group_users = self.data_source.get_group_users(group_id) - channel_users.extend(group_users) - channel_users = get_unique_elements(channel_users, self.data_source.USER_ID) + logging.debug("channel %s groups %s", channel_id, group_users) + + for user in group_users: + if user[self.data_source.USERNAME] in unique_usernames: + continue + + channel_users.append(user) + unique_usernames.append(self.data_source.USERNAME) + + logging.debug("channel %s final users %s", channel_users) + return channel_users + + def process_message(self, message): + """Process a message according to user and default preferences and sends to available delivery channels.""" + channel_users = self.get_channel_users(message[OutputMessageKeys.CHANNEL_ID]) if not channel_users: logging.debug("no channel_users for channel %s", message[OutputMessageKeys.CHANNEL_ID]) return for user in channel_users: + if self.data_source.USER_ID not in user: + # User not registered in the notifications service (coming from grappa groups) + apply_default_preferences(self.publisher, message, user[self.data_source.EMAIL]) + continue + try: # CRITICAL PRIORITY: send to all devices and mail and override preferences - if message[OutputMessageKeys.PRIORITY].lower() == config.Config.CRITICAL_PRIORITY.lower(): + if message[OutputMessageKeys.PRIORITY].lower() == Config.CRITICAL_PRIORITY.lower(): user_devices = self.data_source.get_user_devices(user[self.data_source.USER_ID]) apply_all(self.publisher, message, user[self.data_source.EMAIL], user_devices) continue @@ -114,13 +131,7 @@ class Router(megabus.Listener): ) # sending to devices per delivery method extracted from preferences - apply_user_preferences( - self.publisher, - self.data_source, - delivery_methods_and_targets, - message, - user - ) + apply_user_preferences(self.publisher, self.data_source, delivery_methods_and_targets, message, user) except NotFoundDataSourceError: # Something failed retrieving preferences or devices, just send by mail diff --git a/notifications_routing/utils.py b/notifications_routing/utils.py index 3aaea60d065269d5ac43df0b3864de4555930000..c9fa0894c7e6cf5f564cfa564f5b39185c49941f 100644 --- a/notifications_routing/utils.py +++ b/notifications_routing/utils.py @@ -16,9 +16,9 @@ class InputMessageKeys(StrEnum): """Incoming message keys.""" TARGET = "target" - CHANNEL_ID = "id" - CHANNEL_NAME = "name" - CHANNEL_SLUG = "slug" + ID = "id" + NAME = "name" + SLUG = "slug" PRIORITY = "priority" SENT_AT = "sentAt" BODY = "body" @@ -60,11 +60,6 @@ def is_time_between(time, start_range, end_range): return start_range <= time <= end_range -def get_unique_elements(list_elements, key): - """Return a list with unique dictionaries as elements.""" - return list({v[key]: v for v in list_elements}.values()) - - def convert_notification_email_to_json_string(message, email): """Convert notification e-mail to json string.""" return json.dumps( diff --git a/scripts/docker-send.py b/scripts/docker-send.py index 239634f353fec27ed64e1f1957d35b059a0f5dac..f6402a732353bf186f13667544df679ec22227d7 100644 --- a/scripts/docker-send.py +++ b/scripts/docker-send.py @@ -4,19 +4,12 @@ import stomp conn = stomp.Connection([("activemq", 61613)]) conn.connect("admin", "admin", wait=True) -message_body = r"""{"id":1,"target":{"primaryKey":2,"id":"The Best Notifications", -"name":"The Best Notifications", -"description":"the very best","visibility":"RESTRICTED","subscriptionPolicy":"DYNAMIC","APIKey":null, -"creationDate":"2020-09-07T10:43:52.885Z", -"lastActivityDate":"2020-09-07T10:43:52.885Z", -"deleteDate":null}, -"body":"<p>test EO body</p>\n", -"sendAt":null, -"sentAt":"2020-09-07T14:53:15.389Z", -"users":[],"summary":"sub test EO","tags":null, -"link":"http://cds.cern.ch/record/2687667", -"contentType":null, -"imgUrl":"http://cds.cern.ch/record/2687667/files/CLICtd.png?subformat=icon-640", -"priority":"CRITICAL"} """ +message_body = r"""{"id":"BD19EEA4-9DCA-48D9-A577-5DE9D2BF374A", +"target":{"id":"EF46ACA0-E73B-4794-8043-FFE974247CC8","slug":"test","name":"Test","description":"", +"visibility":"RESTRICTED","subscriptionPolicy":"DYNAMIC","archive":false,"APIKey":null, +"creationDate":"2021-02-26T12:58:42.131Z","lastActivityDate":"2021-02-26T12:58:42.131Z","incomingEmail":null, +"deleteDate":null}, "body":"<p>test</p>\n", "sendAt":null,"sentAt":"2021-02-26T13:59:40.754Z","users":[], +"link":"https://test-notifications.web.cern.ch/main/channels/a4db5752-8f58-4144-a4f7-a2b6454273f5/notifications/de213d1c-4438-4f24-9bc3-58c0373db527", +"summary":"test","imgUrl":null,"priority":"LOW","tags":null,"contentType":null} """ conn.send(body=message_body, destination="/queue/np.routing", headers={"persistent": "true"}) conn.disconnect() diff --git a/scripts/dump.sql b/scripts/dump.sql new file mode 100644 index 0000000000000000000000000000000000000000..fa5b136773d21699843f4df9809612dbddf572ba --- /dev/null +++ b/scripts/dump.sql @@ -0,0 +1,3533 @@ +-- +-- PostgreSQL database dump +-- + +-- Dumped from database version 9.6.20 +-- Dumped by pg_dump version 13.1 + +SET statement_timeout = 0; +SET lock_timeout = 0; +SET idle_in_transaction_session_timeout = 0; +SET client_encoding = 'UTF8'; +SET standard_conforming_strings = on; +SELECT pg_catalog.set_config('search_path', '', false); +SET check_function_bodies = false; +SET xmloption = content; +SET client_min_messages = warning; +SET row_security = off; + +-- +-- Name: authorization_service; Type: SCHEMA; Schema: -; Owner: admin +-- + +CREATE SCHEMA authorization_service; + + +ALTER SCHEMA authorization_service OWNER TO admin; + +-- +-- Name: push; Type: SCHEMA; Schema: -; Owner: admin +-- + +CREATE SCHEMA push; + + +ALTER SCHEMA push OWNER TO admin; + +-- +-- Name: push_test; Type: SCHEMA; Schema: -; Owner: admin +-- + +CREATE SCHEMA push_test; + + +ALTER SCHEMA push_test OWNER TO admin; + +-- +-- Name: test; Type: SCHEMA; Schema: -; Owner: admin +-- + +CREATE SCHEMA test; + + +ALTER SCHEMA test OWNER TO admin; + +-- +-- Name: pgcrypto; Type: EXTENSION; Schema: -; Owner: - +-- + +CREATE EXTENSION IF NOT EXISTS pgcrypto WITH SCHEMA public; + + +-- +-- Name: EXTENSION pgcrypto; Type: COMMENT; Schema: -; Owner: +-- + +COMMENT ON EXTENSION pgcrypto IS 'cryptographic functions'; + + +SET default_tablespace = ''; + +-- +-- Name: Notifications; Type: TABLE; Schema: authorization_service; Owner: admin +-- + +CREATE TABLE authorization_service."Notifications" ( + id integer NOT NULL, + target character varying NOT NULL, + subject character varying NOT NULL, + body character varying NOT NULL, + sent boolean DEFAULT false NOT NULL, + "sendAt" timestamp without time zone, + "sentAt" timestamp without time zone, + "fromId" integer +); + + +ALTER TABLE authorization_service."Notifications" OWNER TO admin; + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE; Schema: authorization_service; Owner: admin +-- + +CREATE SEQUENCE authorization_service."Notifications_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE authorization_service."Notifications_id_seq" OWNER TO admin; + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE OWNED BY; Schema: authorization_service; Owner: admin +-- + +ALTER SEQUENCE authorization_service."Notifications_id_seq" OWNED BY authorization_service."Notifications".id; + + +-- +-- Name: Rules; Type: TABLE; Schema: authorization_service; Owner: admin +-- + +CREATE TABLE authorization_service."Rules" ( + id integer NOT NULL, + name character varying NOT NULL, + channel character varying NOT NULL, + string character varying, + type character varying NOT NULL, + "userId" integer +); + + +ALTER TABLE authorization_service."Rules" OWNER TO admin; + +-- +-- Name: Rules_id_seq; Type: SEQUENCE; Schema: authorization_service; Owner: admin +-- + +CREATE SEQUENCE authorization_service."Rules_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE authorization_service."Rules_id_seq" OWNER TO admin; + +-- +-- Name: Rules_id_seq; Type: SEQUENCE OWNED BY; Schema: authorization_service; Owner: admin +-- + +ALTER SEQUENCE authorization_service."Rules_id_seq" OWNED BY authorization_service."Rules".id; + + +-- +-- Name: Services; Type: TABLE; Schema: authorization_service; Owner: admin +-- + +CREATE TABLE authorization_service."Services" ( + id integer NOT NULL, + name character varying NOT NULL, + "apiKey" character varying +); + + +ALTER TABLE authorization_service."Services" OWNER TO admin; + +-- +-- Name: Services_id_seq; Type: SEQUENCE; Schema: authorization_service; Owner: admin +-- + +CREATE SEQUENCE authorization_service."Services_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE authorization_service."Services_id_seq" OWNER TO admin; + +-- +-- Name: Services_id_seq; Type: SEQUENCE OWNED BY; Schema: authorization_service; Owner: admin +-- + +ALTER SEQUENCE authorization_service."Services_id_seq" OWNED BY authorization_service."Services".id; + + +-- +-- Name: UserNotifications; Type: TABLE; Schema: authorization_service; Owner: admin +-- + +CREATE TABLE authorization_service."UserNotifications" ( + id integer NOT NULL, + read boolean NOT NULL, + archived boolean NOT NULL, + "userId" integer, + "notificationId" integer +); + + +ALTER TABLE authorization_service."UserNotifications" OWNER TO admin; + +-- +-- Name: UserNotifications_id_seq; Type: SEQUENCE; Schema: authorization_service; Owner: admin +-- + +CREATE SEQUENCE authorization_service."UserNotifications_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE authorization_service."UserNotifications_id_seq" OWNER TO admin; + +-- +-- Name: UserNotifications_id_seq; Type: SEQUENCE OWNED BY; Schema: authorization_service; Owner: admin +-- + +ALTER SEQUENCE authorization_service."UserNotifications_id_seq" OWNED BY authorization_service."UserNotifications".id; + + +-- +-- Name: Users; Type: TABLE; Schema: authorization_service; Owner: admin +-- + +CREATE TABLE authorization_service."Users" ( + id integer NOT NULL, + username character varying(50) NOT NULL, + email character varying NOT NULL, + enabled boolean NOT NULL +); + + +ALTER TABLE authorization_service."Users" OWNER TO admin; + +-- +-- Name: Notfications; Type: TABLE; Schema: public; Owner: admin +-- + +CREATE TABLE public."Notfications" ( + id integer NOT NULL, + target character varying NOT NULL, + subject character varying NOT NULL, + body character varying NOT NULL, + sent boolean DEFAULT false NOT NULL, + "sendAt" timestamp without time zone, + "sentAt" timestamp without time zone +); + + +ALTER TABLE public."Notfications" OWNER TO admin; + +-- +-- Name: Notfications_id_seq; Type: SEQUENCE; Schema: public; Owner: admin +-- + +CREATE SEQUENCE public."Notfications_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE public."Notfications_id_seq" OWNER TO admin; + +-- +-- Name: Notfications_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: admin +-- + +ALTER SEQUENCE public."Notfications_id_seq" OWNED BY public."Notfications".id; + + +-- +-- Name: Notifications; Type: TABLE; Schema: public; Owner: admin +-- + +CREATE TABLE public."Notifications" ( + id integer NOT NULL, + target character varying NOT NULL, + subject character varying NOT NULL, + body character varying NOT NULL, + sent boolean DEFAULT false NOT NULL, + "sendAt" timestamp without time zone, + "sentAt" timestamp without time zone +); + + +ALTER TABLE public."Notifications" OWNER TO admin; + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE; Schema: public; Owner: admin +-- + +CREATE SEQUENCE public."Notifications_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE public."Notifications_id_seq" OWNER TO admin; + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: admin +-- + +ALTER SEQUENCE public."Notifications_id_seq" OWNED BY public."Notifications".id; + + +-- +-- Name: Users; Type: TABLE; Schema: public; Owner: admin +-- + +CREATE TABLE public."Users" ( + id integer NOT NULL, + username character varying(50) NOT NULL, + enabled boolean NOT NULL +); + + +ALTER TABLE public."Users" OWNER TO admin; + +-- +-- Name: Users_id_seq; Type: SEQUENCE; Schema: public; Owner: admin +-- + +CREATE SEQUENCE public."Users_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE public."Users_id_seq" OWNER TO admin; + +-- +-- Name: Users_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: admin +-- + +ALTER SEQUENCE public."Users_id_seq" OWNED BY public."Users".id; + + +-- +-- Name: Channels; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push."Channels" ( + id uuid DEFAULT public.gen_random_uuid() NOT NULL, + slug character varying NOT NULL, + name character varying NOT NULL, + description character varying NOT NULL, + visibility character varying DEFAULT 'RESTRICTED'::character varying NOT NULL, + "subscriptionPolicy" character varying DEFAULT 'SELF_SUBSCRIPTION'::character varying NOT NULL, + archive boolean DEFAULT true NOT NULL, + "APIKey" character varying, + "creationDate" timestamp without time zone DEFAULT now() NOT NULL, + "lastActivityDate" timestamp without time zone DEFAULT now() NOT NULL, + "incomingEmail" character varying, + "deleteDate" timestamp without time zone, + "ownerId" uuid, + "adminGroupId" character varying +); + + +ALTER TABLE push."Channels" OWNER TO admin; + +-- +-- Name: Devices; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push."Devices" ( + id uuid DEFAULT public.gen_random_uuid() NOT NULL, + name character varying NOT NULL, + info character varying, + type character varying NOT NULL, + "subType" character varying, + uuid uuid, + token character varying NOT NULL, + "userId" uuid +); + + +ALTER TABLE push."Devices" OWNER TO admin; + +-- +-- Name: Groups; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push."Groups" ( + id character varying NOT NULL, + "groupIdentifier" character varying NOT NULL +); + + +ALTER TABLE push."Groups" OWNER TO admin; + +-- +-- Name: Notifications; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push."Notifications" ( + id uuid DEFAULT public.gen_random_uuid() NOT NULL, + body character varying NOT NULL, + "sendAt" timestamp without time zone, + "sentAt" timestamp without time zone, + tags text, + link character varying, + summary character varying, + "contentType" character varying, + "imgUrl" character varying, + priority character varying DEFAULT 'NORMAL'::character varying NOT NULL, + "targetId" uuid +); + + +ALTER TABLE push."Notifications" OWNER TO admin; + +-- +-- Name: Preferences; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push."Preferences" ( + id uuid DEFAULT public.gen_random_uuid() NOT NULL, + name character varying, + type character varying NOT NULL, + "notificationPriority" text, + "rangeStart" time without time zone, + "rangeEnd" time without time zone, + "userId" uuid, + "targetId" uuid +); + + +ALTER TABLE push."Preferences" OWNER TO admin; + +-- +-- Name: Services; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push."Services" ( + id uuid NOT NULL, + name character varying NOT NULL, + email character varying +); + + +ALTER TABLE push."Services" OWNER TO admin; + +-- +-- Name: UserDailyNotifications; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push."UserDailyNotifications" ( + "userId" uuid, + "notificationId" uuid, + date date NOT NULL, + "time" time without time zone NOT NULL +); + + +ALTER TABLE push."UserDailyNotifications" OWNER TO admin; + +-- +-- Name: UserNotifications; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push."UserNotifications" ( + id uuid DEFAULT public.gen_random_uuid() NOT NULL, + sent boolean NOT NULL, + read boolean NOT NULL, + pinned boolean DEFAULT false NOT NULL, + archived boolean NOT NULL, + "userId" uuid, + "notificationId" uuid +); + + +ALTER TABLE push."UserNotifications" OWNER TO admin; + +-- +-- Name: Users; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push."Users" ( + id uuid DEFAULT public.gen_random_uuid() NOT NULL, + username character varying NOT NULL, + email character varying NOT NULL, + enabled boolean NOT NULL +); + + +ALTER TABLE push."Users" OWNER TO admin; + +-- +-- Name: channels_groups__groups; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push.channels_groups__groups ( + "channelsId" uuid NOT NULL, + "groupsId" character varying NOT NULL +); + + +ALTER TABLE push.channels_groups__groups OWNER TO admin; + +-- +-- Name: channels_members__users; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push.channels_members__users ( + "channelsId" uuid NOT NULL, + "usersId" uuid NOT NULL +); + + +ALTER TABLE push.channels_members__users OWNER TO admin; + +-- +-- Name: channels_unsubscribed__users; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push.channels_unsubscribed__users ( + "channelsId" uuid NOT NULL, + "usersId" uuid NOT NULL +); + + +ALTER TABLE push.channels_unsubscribed__users OWNER TO admin; + +-- +-- Name: preferences_devices__devices; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push.preferences_devices__devices ( + "preferencesId" uuid NOT NULL, + "devicesId" uuid NOT NULL +); + + +ALTER TABLE push.preferences_devices__devices OWNER TO admin; + +-- +-- Name: preferences_disabled_channels__channels; Type: TABLE; Schema: push; Owner: admin +-- + +CREATE TABLE push.preferences_disabled_channels__channels ( + "preferencesId" uuid NOT NULL, + "channelsId" uuid NOT NULL +); + + +ALTER TABLE push.preferences_disabled_channels__channels OWNER TO admin; + +-- +-- Name: Notifications; Type: TABLE; Schema: push_test; Owner: admin +-- + +CREATE TABLE push_test."Notifications" ( + id integer NOT NULL, + target character varying NOT NULL, + subject character varying NOT NULL, + body character varying NOT NULL, + sent boolean DEFAULT false NOT NULL, + "sendAt" timestamp without time zone, + "sentAt" timestamp without time zone, + "fromId" character varying, + tags text, + link character varying, + summary character varying, + "contentType" character varying, + "imgUrl" character varying, + priority character varying DEFAULT 'NORMAL'::character varying NOT NULL +); + + +ALTER TABLE push_test."Notifications" OWNER TO admin; + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE; Schema: push_test; Owner: admin +-- + +CREATE SEQUENCE push_test."Notifications_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE push_test."Notifications_id_seq" OWNER TO admin; + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE OWNED BY; Schema: push_test; Owner: admin +-- + +ALTER SEQUENCE push_test."Notifications_id_seq" OWNED BY push_test."Notifications".id; + + +-- +-- Name: Rules; Type: TABLE; Schema: push_test; Owner: admin +-- + +CREATE TABLE push_test."Rules" ( + id integer NOT NULL, + name character varying NOT NULL, + channels text DEFAULT 'PUSH'::text NOT NULL, + type character varying NOT NULL, + string character varying, + "userUsername" character varying(50) +); + + +ALTER TABLE push_test."Rules" OWNER TO admin; + +-- +-- Name: Rules_id_seq; Type: SEQUENCE; Schema: push_test; Owner: admin +-- + +CREATE SEQUENCE push_test."Rules_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE push_test."Rules_id_seq" OWNER TO admin; + +-- +-- Name: Rules_id_seq; Type: SEQUENCE OWNED BY; Schema: push_test; Owner: admin +-- + +ALTER SEQUENCE push_test."Rules_id_seq" OWNED BY push_test."Rules".id; + + +-- +-- Name: Services; Type: TABLE; Schema: push_test; Owner: admin +-- + +CREATE TABLE push_test."Services" ( + id character varying NOT NULL, + name character varying NOT NULL, + email character varying +); + + +ALTER TABLE push_test."Services" OWNER TO admin; + +-- +-- Name: UserNotifications; Type: TABLE; Schema: push_test; Owner: admin +-- + +CREATE TABLE push_test."UserNotifications" ( + id integer NOT NULL, + read boolean NOT NULL, + pinned boolean DEFAULT false NOT NULL, + archived boolean NOT NULL, + "userUsername" character varying(50), + "notificationId" integer +); + + +ALTER TABLE push_test."UserNotifications" OWNER TO admin; + +-- +-- Name: UserNotifications_id_seq; Type: SEQUENCE; Schema: push_test; Owner: admin +-- + +CREATE SEQUENCE push_test."UserNotifications_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE push_test."UserNotifications_id_seq" OWNER TO admin; + +-- +-- Name: UserNotifications_id_seq; Type: SEQUENCE OWNED BY; Schema: push_test; Owner: admin +-- + +ALTER SEQUENCE push_test."UserNotifications_id_seq" OWNED BY push_test."UserNotifications".id; + + +-- +-- Name: Users; Type: TABLE; Schema: push_test; Owner: admin +-- + +CREATE TABLE push_test."Users" ( + username character varying(50) NOT NULL, + email character varying NOT NULL, + "deviceTokens" text, + enabled boolean NOT NULL +); + + +ALTER TABLE push_test."Users" OWNER TO admin; + +-- +-- Name: Notifications; Type: TABLE; Schema: test; Owner: admin +-- + +CREATE TABLE test."Notifications" ( + id integer NOT NULL, + target character varying NOT NULL, + subject character varying NOT NULL, + body character varying NOT NULL, + sent boolean DEFAULT false NOT NULL, + "sendAt" timestamp without time zone, + "sentAt" timestamp without time zone, + "from" character varying NOT NULL +); + + +ALTER TABLE test."Notifications" OWNER TO admin; + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE; Schema: test; Owner: admin +-- + +CREATE SEQUENCE test."Notifications_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE test."Notifications_id_seq" OWNER TO admin; + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE OWNED BY; Schema: test; Owner: admin +-- + +ALTER SEQUENCE test."Notifications_id_seq" OWNED BY test."Notifications".id; + + +-- +-- Name: Rules; Type: TABLE; Schema: test; Owner: admin +-- + +CREATE TABLE test."Rules" ( + id integer NOT NULL, + channel character varying NOT NULL, + type character varying NOT NULL, + "userId" integer, + string character varying +); + + +ALTER TABLE test."Rules" OWNER TO admin; + +-- +-- Name: Rules_id_seq; Type: SEQUENCE; Schema: test; Owner: admin +-- + +CREATE SEQUENCE test."Rules_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE test."Rules_id_seq" OWNER TO admin; + +-- +-- Name: Rules_id_seq; Type: SEQUENCE OWNED BY; Schema: test; Owner: admin +-- + +ALTER SEQUENCE test."Rules_id_seq" OWNED BY test."Rules".id; + + +-- +-- Name: Services; Type: TABLE; Schema: test; Owner: admin +-- + +CREATE TABLE test."Services" ( + id integer NOT NULL, + name character varying NOT NULL, + "apiKey" character varying +); + + +ALTER TABLE test."Services" OWNER TO admin; + +-- +-- Name: Services_id_seq; Type: SEQUENCE; Schema: test; Owner: admin +-- + +CREATE SEQUENCE test."Services_id_seq" + START WITH 1 + INCREMENT BY 1 + NO MINVALUE + NO MAXVALUE + CACHE 1; + + +ALTER TABLE test."Services_id_seq" OWNER TO admin; + +-- +-- Name: Services_id_seq; Type: SEQUENCE OWNED BY; Schema: test; Owner: admin +-- + +ALTER SEQUENCE test."Services_id_seq" OWNED BY test."Services".id; + + +-- +-- Name: Users; Type: TABLE; Schema: test; Owner: admin +-- + +CREATE TABLE test."Users" ( + id integer NOT NULL, + username character varying(50) NOT NULL, + email character varying NOT NULL +); + + +ALTER TABLE test."Users" OWNER TO admin; + +-- +-- Name: users_notifications__notifications; Type: TABLE; Schema: test; Owner: admin +-- + +CREATE TABLE test.users_notifications__notifications ( + "usersId" integer NOT NULL, + "notificationsId" integer NOT NULL +); + + +ALTER TABLE test.users_notifications__notifications OWNER TO admin; + +-- +-- Name: Notifications id; Type: DEFAULT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Notifications" ALTER COLUMN id SET DEFAULT nextval('authorization_service."Notifications_id_seq"'::regclass); + + +-- +-- Name: Rules id; Type: DEFAULT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Rules" ALTER COLUMN id SET DEFAULT nextval('authorization_service."Rules_id_seq"'::regclass); + + +-- +-- Name: Services id; Type: DEFAULT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Services" ALTER COLUMN id SET DEFAULT nextval('authorization_service."Services_id_seq"'::regclass); + + +-- +-- Name: UserNotifications id; Type: DEFAULT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."UserNotifications" ALTER COLUMN id SET DEFAULT nextval('authorization_service."UserNotifications_id_seq"'::regclass); + + +-- +-- Name: Notfications id; Type: DEFAULT; Schema: public; Owner: admin +-- + +ALTER TABLE ONLY public."Notfications" ALTER COLUMN id SET DEFAULT nextval('public."Notfications_id_seq"'::regclass); + + +-- +-- Name: Notifications id; Type: DEFAULT; Schema: public; Owner: admin +-- + +ALTER TABLE ONLY public."Notifications" ALTER COLUMN id SET DEFAULT nextval('public."Notifications_id_seq"'::regclass); + + +-- +-- Name: Users id; Type: DEFAULT; Schema: public; Owner: admin +-- + +ALTER TABLE ONLY public."Users" ALTER COLUMN id SET DEFAULT nextval('public."Users_id_seq"'::regclass); + + +-- +-- Name: Notifications id; Type: DEFAULT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."Notifications" ALTER COLUMN id SET DEFAULT nextval('push_test."Notifications_id_seq"'::regclass); + + +-- +-- Name: Rules id; Type: DEFAULT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."Rules" ALTER COLUMN id SET DEFAULT nextval('push_test."Rules_id_seq"'::regclass); + + +-- +-- Name: UserNotifications id; Type: DEFAULT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."UserNotifications" ALTER COLUMN id SET DEFAULT nextval('push_test."UserNotifications_id_seq"'::regclass); + + +-- +-- Name: Notifications id; Type: DEFAULT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Notifications" ALTER COLUMN id SET DEFAULT nextval('test."Notifications_id_seq"'::regclass); + + +-- +-- Name: Rules id; Type: DEFAULT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Rules" ALTER COLUMN id SET DEFAULT nextval('test."Rules_id_seq"'::regclass); + + +-- +-- Name: Services id; Type: DEFAULT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Services" ALTER COLUMN id SET DEFAULT nextval('test."Services_id_seq"'::regclass); + + +-- +-- Data for Name: Notifications; Type: TABLE DATA; Schema: authorization_service; Owner: admin +-- + + + +-- +-- Data for Name: Rules; Type: TABLE DATA; Schema: authorization_service; Owner: admin +-- + + + +-- +-- Data for Name: Services; Type: TABLE DATA; Schema: authorization_service; Owner: admin +-- + +INSERT INTO authorization_service."Services" VALUES (2, 'authorization-service', 'e9ac78c1a8e1d67360036bd4cefef6ffd7a849c2dd97bbf98ef08817b80cf398'); + + +-- +-- Data for Name: UserNotifications; Type: TABLE DATA; Schema: authorization_service; Owner: admin +-- + + + +-- +-- Data for Name: Users; Type: TABLE DATA; Schema: authorization_service; Owner: admin +-- + + + +-- +-- Data for Name: Notfications; Type: TABLE DATA; Schema: public; Owner: admin +-- + +INSERT INTO public."Notfications" VALUES (1, 'Me', 'Test', 'Send push notification test', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (2, 'Me', 'Test', 'Send push notification test', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (3, 'Me', 'Test', 'Send push notification test', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (4, 'Me', 'Test', 'Send push notification test', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (5, 'Me', 'Test', 'Send push notification test', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (6, 'Me', 'Test', 'Send push notification test', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (7, 'Me', 'Test', 'Send push notification test', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (8, 'Me', 'Test', 'Send push notification test', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (9, 'Me', 'Test', 'Send push notification test', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (10, 'Test 19 July 2018', 'Test 19 July 2018', 'Test 19 July 2018', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (11, 'Test 20 July 2018', 'Test 20 July 2018', 'Test 20 July 2018', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (17, 'target', 'Test', 'This is a test notifications', false, NULL, NULL); +INSERT INTO public."Notfications" VALUES (19, 'all', 'Test', 'This is a test notifications', false, NULL, NULL); +INSERT INTO public."Notfications" VALUES (20, 'all', 'test', 'This is a test notification', false, NULL, NULL); +INSERT INTO public."Notfications" VALUES (21, 'Test 20 July 2018 David [2]', 'Test 20 July 2018 David [2]', 'Test 20 July 2018 David [2]', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (22, 'Test 20 July 2018 David [3]', 'Test 20 July 2018 David [3]', 'Test 20 July 2018 David [3]', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (23, 'david.martin.clavo@cern.ch', 'Test 20 July 2018 David [4]', 'Test 20 July 2018 David [4]', false, '2018-08-17 00:00:00', NULL); +INSERT INTO public."Notfications" VALUES (24, 'Mario', 'Test', 'This is a test notification', false, NULL, NULL); +INSERT INTO public."Notfications" VALUES (28, 'all', 'test', 'eeey testing material ui', false, NULL, NULL); +INSERT INTO public."Notfications" VALUES (29, 'all', 'test', 'eeey testing material ui', false, NULL, NULL); +INSERT INTO public."Notfications" VALUES (30, 'all', 'test', 'eeey testing material ui', false, NULL, NULL); +INSERT INTO public."Notfications" VALUES (31, 'all', 'test', 'eeey testing material ui', false, NULL, NULL); +INSERT INTO public."Notfications" VALUES (32, 'all', 'test', 'eeey testing material ui', false, NULL, NULL); +INSERT INTO public."Notfications" VALUES (36, 'adsf', 'adsf', 'adsf', false, NULL, NULL); + + +-- +-- Data for Name: Notifications; Type: TABLE DATA; Schema: public; Owner: admin +-- + +INSERT INTO public."Notifications" VALUES (1, 'Panero', 'Test', 'This is a test notification', false, NULL, NULL); +INSERT INTO public."Notifications" VALUES (2, 'Mario', 'Test', 'This is a test notification', false, NULL, NULL); +INSERT INTO public."Notifications" VALUES (4, 'pablo.roncer.fernandez@cern.ch', 'Test', 'This is a test notification', false, NULL, NULL); + + +-- +-- Data for Name: Users; Type: TABLE DATA; Schema: public; Owner: admin +-- + + + +-- +-- Data for Name: Channels; Type: TABLE DATA; Schema: push; Owner: admin +-- + +INSERT INTO push."Channels" VALUES ('a8b1b6db-2543-4549-b143-442735739fed', 'notifications-dev-test-channel', 'Notifications DEV Test Channel', 'Notifications DEV Test Channel', 'RESTRICTED', 'DYNAMIC', false, NULL, '2021-02-26 18:38:30.292949', '2021-02-26 18:38:30.292949', NULL, NULL, 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', '186d8dfc-2774-43a8-91b5-a887fcb6ba4a'); +INSERT INTO push."Channels" VALUES ('00736a81-9f42-49c8-9d2c-1b8536507706', '0', 'Test-Notifications', 'Test Channel For notifications', 'INTERNAL', 'SELF_SUBSCRIPTION', false, NULL, '2021-02-26 19:44:44.030731', '2021-02-26 19:44:44.030731', 'igor.jakovljevic@outlook.com', NULL, '598d151c-f850-451e-9eac-1f6a3d987a5c', '08d7bc9a-583b-4015-86a5-4ab9f3f771b8'); +INSERT INTO push."Channels" VALUES ('ac47643d-0f6e-4c33-9d96-3fa3946215a8', 'caetan-test-channel', 'Caetan Test Channel (edit)', 'This is the test Channel for Caetán (edited)', 'RESTRICTED', 'DYNAMIC', false, NULL, '2021-03-01 10:04:22.492549', '2021-03-01 10:04:22.492549', NULL, NULL, 'a7fc13ae-f38c-4501-83f3-e37a35661fa1', NULL); +INSERT INTO push."Channels" VALUES ('93015feb-b53d-4806-ae9c-1f630bca5a0c', 'a', 'a', '', 'RESTRICTED', 'DYNAMIC', false, NULL, '2021-03-01 11:37:22.570865', '2021-03-01 11:37:22.570865', NULL, '2021-03-01 11:37:29.779889', 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', NULL); +INSERT INTO push."Channels" VALUES ('9367e33e-47df-4648-825e-e6b52d73b593', 'test-public-channel', 'Test Public Channel', 'A Public Channel for testing', 'PUBLIC', 'SELF_SUBSCRIPTION', false, NULL, '2021-03-01 11:38:04.611044', '2021-03-01 11:38:04.611044', NULL, NULL, 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', NULL); +INSERT INTO push."Channels" VALUES ('ef46aca0-e73b-4794-8043-ffe974247cc8', 'my-internal-test-channel', 'My Internal Test Channel', 'My Internal Test Channel', 'RESTRICTED', 'DYNAMIC', false, NULL, '2021-03-01 12:52:17.25554', '2021-03-01 12:52:17.25554', NULL, NULL, 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', NULL); +INSERT INTO push."Channels" VALUES ('54f42ef2-8dc8-4dd1-986d-18025eb74b82', 'carina-s-internal-test-channel', 'Carina''s Internal Test Channel', '', 'INTERNAL', 'SELF_SUBSCRIPTION_APPROVAL', false, NULL, '2021-03-01 12:56:47.422348', '2021-03-01 12:56:47.422348', NULL, NULL, 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', NULL); +INSERT INTO push."Channels" VALUES ('23ada92a-e7dd-4c19-90b0-a9493f95f1e4', 'a-wf-restricted-test-channel', 'A WF Restricted test channel', '', 'RESTRICTED', 'DYNAMIC', false, NULL, '2021-03-01 12:58:00.902803', '2021-03-01 12:58:00.902803', NULL, NULL, 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', '186d8dfc-2774-43a8-91b5-a887fcb6ba4a'); +INSERT INTO push."Channels" VALUES ('e4aa1f94-9eba-43cc-ad3e-9d9d49b03891', 'test-self-subscription-with-approval', 'Test Self Subscription with approval', '', 'INTERNAL', 'SELF_SUBSCRIPTION_APPROVAL', false, NULL, '2021-03-01 14:14:03.452426', '2021-03-01 14:14:03.452426', NULL, NULL, 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', NULL); +INSERT INTO push."Channels" VALUES ('fbd18055-a847-40b9-9a98-d9f400ebd08b', 'my-internal-test-channel-2', 'My Internal Test Channel 2', '', 'RESTRICTED', 'DYNAMIC', false, NULL, '2021-03-01 12:53:48.935061', '2021-03-01 12:53:48.935061', NULL, '2021-03-01 15:39:48.298667', 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', NULL); + + +-- +-- Data for Name: Devices; Type: TABLE DATA; Schema: push; Owner: admin +-- + +INSERT INTO push."Devices" VALUES ('d4e15d11-a56e-4568-9e9f-497110426a72', 'carina.oliveira.antunes@cern.ch', 'Default', 'MAIL', NULL, NULL, 'carina.oliveira.antunes@cern.ch', 'edeebd44-29db-43f6-98d5-a3852b0fcbe7'); +INSERT INTO push."Devices" VALUES ('c14467fd-acd5-446a-b2e8-31f4eb601a37', 'caetan.tojeiro.carpente@cern.ch', 'Default', 'MAIL', NULL, NULL, 'caetan.tojeiro.carpente@cern.ch', 'a7fc13ae-f38c-4501-83f3-e37a35661fa1'); +INSERT INTO push."Devices" VALUES ('5b2d3c49-e4dc-4827-ae75-0ab48e1b5ac6', 'igor.jakovljevic@cern.ch', 'Default', 'MAIL', NULL, NULL, 'igor.jakovljevic@cern.ch', '598d151c-f850-451e-9eac-1f6a3d987a5c'); +INSERT INTO push."Devices" VALUES ('fa69dcc7-8c71-41af-9886-8993c124c8de', 'emmanuel.ormancey@cern.ch', 'Default', 'MAIL', NULL, NULL, 'emmanuel.ormancey@cern.ch', '60a5b86e-345e-47bc-915f-2a8af500485b'); +INSERT INTO push."Devices" VALUES ('4d36d008-ee1e-4e66-8c46-6dc4742210ef', 'Mac Chrome', 'Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.192 Safari/537.36', 'BROWSER', 'OTHER', '2c8e2dd3-c850-417c-b1a6-57fedee8bd60', '{"endpoint":"https://fcm.googleapis.com/fcm/send/e-OO6NZSAdA:APA91bEotRFt3nj7wo_6UKD0xp3N3kt9YCWGvSz9jrwtvHYlssW6jjpO5znRvac_azKIrpHvcAJ88ucBZ15WLRj0aNrytkwdoB-CNmbirF9cz462QgNYjSZwwUslH6aU8aB7QYICy8jj","expirationTime":null,"keys":{"p256dh":"BK71DL-82wyjT68Xv0Rr7C8LwJQWwkiKYvgr5D2I_SgQS30o8Nu0wFSQDoB8q3HVjTskn3_LvQVN3_ocT4_-4UE","auth":"8t1uf7_SYN_bY5__-40UYQ"}}', 'edeebd44-29db-43f6-98d5-a3852b0fcbe7'); +INSERT INTO push."Devices" VALUES ('7b338d47-a34d-46f6-a6be-ce123f03a8ac', 'Mac Chrome', 'Mozilla/5.0 (Macintosh; Intel Mac OS X 11_2_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.192 Safari/537.36', 'BROWSER', 'OTHER', '92fee1b5-838c-4f10-9bf2-cc4a593f2fa9', '{"endpoint":"https://fcm.googleapis.com/fcm/send/eDyYgiUXIKY:APA91bHKPJ7s3MbHoP9oNAL16RkAZGS08qo9DmTd8x7abUjQbNCqsaLjqUjHfcC_qv3BAIkMJg_ZgpaOz6rvt9_jVOGmFgPBGAmQVqoOfMI86ACl0xoE6bQES-ZjIIpVScfK5Lf9U824","expirationTime":null,"keys":{"p256dh":"BP9a5bhIQFbAp4doR0MpkW_mAM94RBupsMoVXARke72yXadW7ZbebdugAHtIXJWk58l3Ks5tmCkoGoE4VYMta5o","auth":"peGTvAd3tL2_KuEay5xvpg"}}', '60a5b86e-345e-47bc-915f-2a8af500485b'); + + +-- +-- Data for Name: Groups; Type: TABLE DATA; Schema: push; Owner: admin +-- + +INSERT INTO push."Groups" VALUES ('186d8dfc-2774-43a8-91b5-a887fcb6ba4a', 'it-dep-cda-wf'); +INSERT INTO push."Groups" VALUES ('08d82a52-7972-4fed-8135-bf603f002247', 'notifications-service-admins'); +INSERT INTO push."Groups" VALUES ('08d7bc9a-583b-4015-86a5-4ab9f3f771b8', 'notifications-admins'); + + +-- +-- Data for Name: Notifications; Type: TABLE DATA; Schema: push; Owner: admin +-- + +INSERT INTO push."Notifications" VALUES ('550d47a8-5247-47a8-ab7c-b5452485e69b', '<p><img alt="" src="https://codimd.web.cern.ch/uploads/upload_e3ccd0101f70e1b546ae45db09922bde.png" /></p> + +<p> </p> + +<h1>My first notification!</h1> + +<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Mauris justo turpis, sodales at neque pulvinar, cursus rutrum erat. Ut laoreet faucibus arcu, vel convallis nibh efficitur at. Nam tincidunt dolor quis scelerisque faucibus. Pellentesque nec nulla in leo mollis consequat. Nullam euismod, diam ac mollis blandit, dolor nulla sollicitudin enim, eget blandit mi libero nec sem. In et tortor neque. Donec ullamcorper magna eget ornare luctus. Duis pretium diam et arcu finibus ultrices. Aliquam condimentum interdum sem, sagittis rutrum leo hendrerit ac. Curabitur placerat tellus sed felis congue, ut gravida nisl tristique. Fusce at elementum mauris.</p> + +<p>Sed nulla purus, consequat at suscipit ac, semper vitae diam. Vestibulum quis tincidunt mi. Vestibulum ante ipsum primis in faucibus orci luctus et ultrices posuere cubilia curae; Etiam vel lobortis nisi. Pellentesque sit amet risus libero. Sed erat sem, ullamcorper at eleifend lacinia, vestibulum ut lorem. Sed euismod odio et ornare accumsan. Ut non venenatis purus. Aenean tellus tellus, vulputate ut nisi at, luctus vestibulum augue. Maecenas sed est neque. Mauris lorem tellus, gravida ac justo at, cursus tincidunt leo.</p> + +<p>Morbi vitae massa in ipsum ultrices mollis. Mauris accumsan rutrum gravida. Nullam rutrum tortor eu ante volutpat lobortis. Suspendisse vel rutrum tellus, in tempor sapien. Duis a risus id velit vestibulum laoreet. Curabitur sit amet elementum odio. Aenean sed magna ut augue ornare rutrum. Quisque fermentum, risus et faucibus pellentesque, enim diam porttitor odio, sed sodales mi est eget enim. Cras mattis risus mattis est lacinia, vel interdum justo ornare.</p> + +<p>Nullam eleifend, felis a ornare egestas, justo nibh mollis quam, eget facilisis sapien nulla ac nisl. Sed efficitur lacinia mauris, ut dictum odio sagittis quis. Fusce ut diam nibh. Aliquam pretium a nunc id finibus. Praesent laoreet dapibus turpis, a ullamcorper velit semper eu. Sed sed nisi lectus. Mauris eget condimentum mauris. Morbi bibendum ac est at volutpat. Morbi dapibus dui ex, eget rutrum massa tristique ac. Aenean nulla turpis, laoreet vitae quam at, condimentum rhoncus erat.</p> + +<p>Phasellus imperdiet auctor felis non posuere. Morbi egestas pharetra dui non porta. Aliquam laoreet finibus ullamcorper. Phasellus eget magna vitae nisi scelerisque tincidunt. Quisque ornare odio in pharetra faucibus. Vivamus semper, velit eu viverra tristique, felis libero vehicula elit, in interdum felis magna a lacus. Etiam ut purus cursus, consectetur urna eu, rhoncus ante. Nam aliquam massa quis ullamcorper elementum. Vestibulum sagittis, dui at semper lobortis, eros felis dignissim ligula, ut pulvinar arcu ante ut dui. Aliquam ac ultrices lorem.</p> +', NULL, '2021-02-26 17:42:17.91', NULL, NULL, 'My first test notification!', NULL, NULL, 'NORMAL', 'a8b1b6db-2543-4549-b143-442735739fed'); +INSERT INTO push."Notifications" VALUES ('283e560a-9b08-4fda-8841-fe8682b755e0', '<p>Mega Test</p> +', NULL, '2021-02-26 18:45:37.19', NULL, NULL, 'Title', NULL, NULL, 'NORMAL', '00736a81-9f42-49c8-9d2c-1b8536507706'); +INSERT INTO push."Notifications" VALUES ('c56ed0c6-af50-44fe-a631-76465c5150e6', '<p>Test 2</p> +', NULL, '2021-03-01 08:48:47.525', NULL, NULL, 'Test 2', NULL, NULL, 'NORMAL', '00736a81-9f42-49c8-9d2c-1b8536507706'); +INSERT INTO push."Notifications" VALUES ('d53a7d79-0c5e-4b72-9d6f-8492b7415340', '<p>This is my first notification in Caetan's channel</p> +', NULL, '2021-03-01 10:07:21.657', NULL, NULL, 'My first Noti - Caetán', NULL, 'https://upload.wikimedia.org/wikipedia/commons/e/e0/Deportivodelacoruna2008.jpg', 'NORMAL', 'ac47643d-0f6e-4c33-9d96-3fa3946215a8'); +INSERT INTO push."Notifications" VALUES ('bd19eea4-9dca-48d9-a577-5de9d2bf374a', '<p>My Daily Notification Body.</p> + +<p>- C</p> +', NULL, '2021-03-01 14:17:47.47', NULL, NULL, 'My Daily Notification', NULL, NULL, 'NORMAL', 'ef46aca0-e73b-4794-8043-ffe974247cc8'); +INSERT INTO push."Notifications" VALUES ('c086358b-df22-48d3-b518-12b18d100cc6', '<p>Test</p> +', NULL, '2021-03-01 14:23:11.609', NULL, NULL, 'Test', NULL, NULL, 'NORMAL', 'ef46aca0-e73b-4794-8043-ffe974247cc8'); +INSERT INTO push."Notifications" VALUES ('508cd4db-74cb-4ea6-941c-d45170dca8f6', '<p>Daily Test Notification Body</p> +', NULL, '2021-03-01 14:40:18.556', NULL, NULL, 'Daily Test Notification', NULL, NULL, 'NORMAL', 'ef46aca0-e73b-4794-8043-ffe974247cc8'); + + +-- +-- Data for Name: Preferences; Type: TABLE DATA; Schema: push; Owner: admin +-- + +INSERT INTO push."Preferences" VALUES ('f3cf5209-8678-4516-93da-c01a4f9f1f88', 'Default Daily Low', 'DAILY', 'low', NULL, NULL, 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', NULL); +INSERT INTO push."Preferences" VALUES ('4d73e456-c151-45d6-bc4c-edbc6fb77462', 'Default Normal', 'LIVE', 'important', NULL, NULL, 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', NULL); +INSERT INTO push."Preferences" VALUES ('d43886dd-d6fd-486f-969b-65a4c6f229f7', 'Default', 'LIVE', 'normal', NULL, NULL, 'edeebd44-29db-43f6-98d5-a3852b0fcbe7', NULL); +INSERT INTO push."Preferences" VALUES ('7639f452-ea92-4049-ab9f-7f07ae9be8b7', 'Default preference', 'LIVE', 'Low,Normal,Important', NULL, NULL, 'a7fc13ae-f38c-4501-83f3-e37a35661fa1', NULL); +INSERT INTO push."Preferences" VALUES ('e9e07557-22c5-42ee-9c50-33d8a6c17901', 'Default preference', 'LIVE', 'Low,Normal,Important', NULL, NULL, '598d151c-f850-451e-9eac-1f6a3d987a5c', NULL); +INSERT INTO push."Preferences" VALUES ('b0b013a0-c07e-43fb-b651-2f386376ac1a', 'Default preference', 'LIVE', 'Low,Normal,Important', NULL, NULL, '60a5b86e-345e-47bc-915f-2a8af500485b', NULL); + + +-- +-- Data for Name: Services; Type: TABLE DATA; Schema: push; Owner: admin +-- + + + +-- +-- Data for Name: UserDailyNotifications; Type: TABLE DATA; Schema: push; Owner: admin +-- + + + +-- +-- Data for Name: UserNotifications; Type: TABLE DATA; Schema: push; Owner: admin +-- + + + +-- +-- Data for Name: Users; Type: TABLE DATA; Schema: push; Owner: admin +-- + +INSERT INTO push."Users" VALUES ('edeebd44-29db-43f6-98d5-a3852b0fcbe7', 'crdeoliv', 'carina.oliveira.antunes@cern.ch', true); +INSERT INTO push."Users" VALUES ('a7fc13ae-f38c-4501-83f3-e37a35661fa1', 'ctojeiro', 'caetan.tojeiro.carpente@cern.ch', true); +INSERT INTO push."Users" VALUES ('598d151c-f850-451e-9eac-1f6a3d987a5c', 'ijakovlj', 'igor.jakovljevic@cern.ch', true); +INSERT INTO push."Users" VALUES ('60a5b86e-345e-47bc-915f-2a8af500485b', 'ormancey', 'emmanuel.ormancey@cern.ch', true); + + +-- +-- Data for Name: channels_groups__groups; Type: TABLE DATA; Schema: push; Owner: admin +-- + +INSERT INTO push.channels_groups__groups VALUES ('a8b1b6db-2543-4549-b143-442735739fed', '186d8dfc-2774-43a8-91b5-a887fcb6ba4a'); +INSERT INTO push.channels_groups__groups VALUES ('a8b1b6db-2543-4549-b143-442735739fed', '08d82a52-7972-4fed-8135-bf603f002247'); + + +-- +-- Data for Name: channels_members__users; Type: TABLE DATA; Schema: push; Owner: admin +-- + +INSERT INTO push.channels_members__users VALUES ('00736a81-9f42-49c8-9d2c-1b8536507706', '598d151c-f850-451e-9eac-1f6a3d987a5c'); +INSERT INTO push.channels_members__users VALUES ('9367e33e-47df-4648-825e-e6b52d73b593', 'edeebd44-29db-43f6-98d5-a3852b0fcbe7'); +INSERT INTO push.channels_members__users VALUES ('e4aa1f94-9eba-43cc-ad3e-9d9d49b03891', '598d151c-f850-451e-9eac-1f6a3d987a5c'); +INSERT INTO push.channels_members__users VALUES ('ef46aca0-e73b-4794-8043-ffe974247cc8', 'edeebd44-29db-43f6-98d5-a3852b0fcbe7'); +INSERT INTO push.channels_members__users VALUES ('fbd18055-a847-40b9-9a98-d9f400ebd08b', 'edeebd44-29db-43f6-98d5-a3852b0fcbe7'); + + +-- +-- Data for Name: channels_unsubscribed__users; Type: TABLE DATA; Schema: push; Owner: admin +-- + + + +-- +-- Data for Name: preferences_devices__devices; Type: TABLE DATA; Schema: push; Owner: admin +-- + +INSERT INTO push.preferences_devices__devices VALUES ('f3cf5209-8678-4516-93da-c01a4f9f1f88', 'd4e15d11-a56e-4568-9e9f-497110426a72'); +INSERT INTO push.preferences_devices__devices VALUES ('4d73e456-c151-45d6-bc4c-edbc6fb77462', 'd4e15d11-a56e-4568-9e9f-497110426a72'); +INSERT INTO push.preferences_devices__devices VALUES ('d43886dd-d6fd-486f-969b-65a4c6f229f7', 'd4e15d11-a56e-4568-9e9f-497110426a72'); +INSERT INTO push.preferences_devices__devices VALUES ('7639f452-ea92-4049-ab9f-7f07ae9be8b7', 'c14467fd-acd5-446a-b2e8-31f4eb601a37'); +INSERT INTO push.preferences_devices__devices VALUES ('e9e07557-22c5-42ee-9c50-33d8a6c17901', '5b2d3c49-e4dc-4827-ae75-0ab48e1b5ac6'); +INSERT INTO push.preferences_devices__devices VALUES ('b0b013a0-c07e-43fb-b651-2f386376ac1a', 'fa69dcc7-8c71-41af-9886-8993c124c8de'); + + +-- +-- Data for Name: preferences_disabled_channels__channels; Type: TABLE DATA; Schema: push; Owner: admin +-- + + + +-- +-- Data for Name: Notifications; Type: TABLE DATA; Schema: push_test; Owner: admin +-- + +INSERT INTO push_test."Notifications" VALUES (5, 'proncero', 'test', 'test', true, NULL, '2019-10-24 12:59:02.644', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (6, 'proncero', 'test', 'test', true, NULL, '2019-11-05 14:16:15.384', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (7, 'proncero', 'test', 'test', true, NULL, '2019-11-05 15:12:13.049', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (9, 'proncero', 'How to build beautiful CERN websites ', '<span>How to build beautiful CERN websites </span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Kate Kahle</div> + </div> + <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span> +<span>Tue, 11/05/2019 - 14:19</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p> + +<p>Last year, when D8 was launched at CERN, it was accompanied by a <a href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p> + +<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p> + +<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p> + +<p>If you would like to join the Drupal community to find out the latest news and improvements, <a href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p> +</div> + ', true, NULL, '2019-11-11 16:39:03.673', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (12, 'proncero', 'Be seen, be safe', '<span>Be seen, be safe</span> +<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 11/05/2019 - 12:27</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a> +<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p> + +<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p> +</div> + ', true, NULL, '2019-11-11 16:39:03.648', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (13, 'proncero', 'Halfway towards LHC consolidation', '<span>Halfway towards LHC consolidation</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Corinne Pralavorio</div> + </div> + <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span> +<span>Fri, 10/18/2019 - 11:18</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The Large Hadron Collider is such a huge and sophisticated machine that the slightest alteration requires an enormous amount of work. During the second long shutdown (LS2), teams are hard at work <a href="https://home.cern/news/news/accelerators/more-spring-clean-lhc-magnets">reinforcing the electrical insulation of the accelerator’s superconducting dipole diodes</a>. The LHC contains not one, not two, but 1232 superconducting dipole magnets, each with a diode system to upgrade. That’s why no fewer than 150 people are needed to carry out the 70 000 tasks involved in this work.</p> + +<p>The project is now halfway to completion. One of the machine’s eight sectors, containing 154 magnets, is now closed and the final leak tests are under way. Work is ongoing in the seven other sectors and the teams are working at a rate of ten interconnections consolidated per day.</p> + +<p>The work is part of a broader project called DISMAC (“Diodes Insulation and Superconducting Magnets Consolidation”), which also includes the replacement of magnets and maintenance operations on the current leads, the devices that supply the LHC with electricity. Twenty-two magnets have already been replaced and two others have been removed from the machine in order to replace their beam screens, which are components located in the vacuum chamber.</p> + +<p>A plethora of upgrade and maintenance work is also being carried out in the tunnel on all the equipment, from the cryogenics system to the vacuum, beam instrumentation and technical infrastructures.</p> + +<figure><img alt="magnet,LHC,LS2,tunnel,TI2,Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201906-163-1/file?size=large" /><figcaption>Replacement of one of the LHC superconducting dipole magnets during the accelerator consolidation campaign. (Image: Maximilien Brice and Julien Ordan/CERN)</figcaption></figure><hr /></div> + ', true, NULL, '2019-11-11 16:39:03.58', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (10, 'proncero', 'Beamline for Schools 2019 participants present results', '<span>Beamline for Schools 2019 participants present results</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Joseph Piergrossi</div> + </div> + <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 11/08/2019 - 13:58</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS"> + <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a> + <figcaption> + The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p> + +<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p> + +<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p> + +<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p> + +<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p> + +<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p> + +<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p> + +<p>Want to join? Preregistration for BL4S 2020 is <a href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p> + +<hr /><p>More photos <a href="https://cds.cern.ch/record/2698994">on CDS</a>:</p> + +<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p> +</div> + ', true, NULL, '2019-11-11 16:39:03.579', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (11, 'proncero', 'Medipix: Two decades of turning technology into applications', '<span>Medipix: Two decades of turning technology into applications</span> +<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 10/18/2019 - 10:11</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2253263" data-filename="studio%2000051" id="CERN-PHOTO-201702-048-3"><a href="//cds.cern.ch/images/CERN-PHOTO-201702-048-3" title="View on CDS"> + <img alt="Knowledge Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201702-048-3/file?size=medium" /></a> + <figcaption><span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>How could microchips developed for detectors at the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC) be used beyond high-energy physics? This was a question that led to the <a href="https://cern.ch/medipix">Medipix</a> and Timepix families of pixel-sensor chips. Researchers saw many possible applications for this technology, and for the last 20 years these chips have been used in medical imaging, in spotting forgeries in the art world, in detecting radioactive material and more. A <a href="https://indico.cern.ch/event/782801/timetable/">recent CERN symposium</a> commemorated the two decades since the Medipix2 collaboration was established, in 1999.</p> + +<p>Pixel-sensor chips are used in detectors at the LHC to trace the paths of electrically charged particles. When a particle hits the sensor, it deposits a charge that is processed by the electronics. This is similar to light hitting pixels in a digital camera, but instead they register particles up to 40 million times a second.</p> + +<p>In the late 1990s, engineers and physicists at CERN were developing integrated circuits for pixel technologies. They realised that adding a counter to each pixel and counting the number of particles hitting the sensors could allow the chips to be used for medical imaging. The Medipix2 chip was born. Later, the Timepix chip added the ability to record either the arrival time of the particles or the energy deposited within a pixel.</p> + +<p>As the chips evolved from Medipix2 to Medipix3, their growing use in medical imaging led to the <a href="https://home.cern/news/news/knowledge-sharing/first-3d-colour-x-ray-human-using-cern-technology">first colour X-ray of parts of the human body</a> in 2018, with the first clinical trials now beginning in New Zealand. In addition, the versatile chips have gone beyond medicine, for example, a start-up called InsightART allows researchers to use Medipix3 chips to <a href="https://home.cern/news/news/knowledge-sharing/particle-detectors-meet-canvas">peer through the layers of works of art</a> and study the composition of materials to determine the authenticity of pieces attributed to renowned artists.</p> + +<p>The team behind InsightART, based in Prague, <a href="https://insightart.eu/2018/06/08/is-this-a-newly-discovered-van-gogh/">recently scanned an alleged Van Gogh</a>, concluding that the work was most likely to have been produced by the Dutch master, having observed an underlying sketch very similar to other figures Van Gogh painted at the time. The work will be sent to the Van Gogh Museum to be vetted with this evidence, and it might be that not one but two Van Goghs have been found in the same piece.</p> + +<p><a href="https://medipix.web.cern.ch/news/nasa-cern-timepix-technology-advances-miniaturized-radiation-detection">Timepix-based detectors have been aboard the International Space Station since 2012</a> to measure the radiation dose to which astronauts and equipment are exposed, and in 2015, high-school students from the UK <a href="https://home.cern/news/news/knowledge-sharing/tim-peakes-timpix-launch-space">sent </a><a href="https://home.cern/news/news/knowledge-sharing/tim-peakes-timpix-launch-space">their own</a> Timepix-based detector to the ISS with astronaut Tim Peake. The ability of the chips to detect gamma rays has been exploited to help with the decommissioning of nuclear reactors and is being evaluated for the detection of thyroid cancer with greater resolution than before and with a lower radiation dose to the patient.</p> + +<p>The Medipix and Timepix chips, developed by three collaborations involving 32 institutes in total, have been remarkable examples of <a href="https://kt.cern/">knowledge transfer from CERN</a> to wider society. You can learn more about the history of Medipix and their many applications <a class="bulletin" href="https://cds.cern.ch/video/2678560?showTitle=true">in this talk</a> by Medipix spokesperson Michael Campbell, given in June 2019.</p> + +<p><iframe allowfullscreen="" frameborder="0" height="360" src="https://cds.cern.ch/video/2678560?showTitle=true" width="640"></iframe></p> +</div> + ', true, NULL, '2019-11-11 16:39:03.672', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (8, 'proncero', 'Broadening tunnel vision for future accelerators', '<span>Broadening tunnel vision for future accelerators</span> +<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Wed, 10/23/2019 - 10:20</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692937" data-filename="201910-334_08" id="CERN-PHOTO-201910-334-8"><a href="//cds.cern.ch/images/CERN-PHOTO-201910-334-8" title="View on CDS"> + <img alt="HL-LHC Underground civil engineering galleries progress" src="//cds.cern.ch/images/CERN-PHOTO-201910-334-8/file?size=medium" /></a> + <figcaption> + HL-LHC Underground civil engineering galleries + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>What could the next generation of particle accelerators look like? With current technology, the bigger an accelerator, the higher the energy of the collisions it produces and the greater the likelihood of discovering new physics phenomena. Particle physicists and accelerator engineers therefore dream of machines that are even bigger than the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC), with its 27-km circumference.</p> + +<p>For CERN’s civil engineers, a new accelerator requires a bespoke deep-underground tunnel, and the tunnel’s shape, depth and orientation as well as its access shafts are largely constrained by the local geography. Such an accelerator built at CERN would be bound by mountains, and, if circular, would need to go under Lake Geneva and completely enclose the Salève mountain of the Prealps.</p> + +<figure class="cds-image breakout-right" id="OPEN-PHO-CIVIL-2019-001-1"><a href="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1" title="View on CDS"><img alt="home.cern,Civil Engineering and Infrastructure" src="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1/file?size=medium" /></a> +<figcaption>Two proposed post-LHC accelerators – CLIC and the FCC – present unique challenges to CERN’s civil engineers<span> (Image: CERN)</span></figcaption></figure><p>The two largest projects under consideration for a post-LHC collider at CERN are the <a href="https://home.cern/science/accelerators/compact-linear-collider">Compact Linear Collider</a> (CLIC) and the <a href="https://home.cern/science/accelerators/future-circular-collider">Future Circular Collider</a> (FCC). Their scale would dwarf CERN’s existing infrastructure, making them some of the largest tunnelling projects in the world. Civil engineers therefore need to survey the geological, environmental and technical constraints of these machines.</p> + +<p>A <a href="https://indico.cern.ch/event/823271/">tunnelling workshop</a> that took place last week at CERN brought together civil-engineering experts from industry and academia to examine how new technologies and methods could optimise tunnel design and asset management. It is part of ongoing collaborations that have already seen CERN and the engineering consultancy Arup develop a first-of-its-kind tunnel optimisation tool to provide the best design when fed all the required parameters. The tool has already shown the feasibility of tunnels for either the FCC or CLIC in the local area, to help support the ongoing update for the European Strategy of Particle Physics that will guide the direction of particle physics and related fields to the mid-2020s and beyond.</p> + +<p>Find out more about the tunnelling challenges of CERN’s civil engineers for the next-generation of particle accelerators in “<a href="https://cerncourier.com/a/tunnelling-for-physics/">Tunnelling for Physics</a>” on the <em>CERN Courier</em>’s website.</p> +</div> + ', true, NULL, '2019-11-11 16:39:03.576', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (16, 'proncero', 'ALICE: the journey of a cosmopolitan detector', '<span>ALICE: the journey of a cosmopolitan detector</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Camille Monnin</div> + </div> + <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span> +<span>Thu, 10/31/2019 - 10:04</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p> + +<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p> + +<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p> + +<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p> + +<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p> + +<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-128-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1/file?size=large" /></a> +<figcaption>A detector piece from Berkeley Lab, on its way to CERN.<span> (Image: Lawrence Berkeley National Laboratory)</span></figcaption></figure><p> </p> +</div> + ', true, NULL, '2019-11-11 16:39:03.671', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (14, 'proncero', 'LHCf gears up to probe birth of cosmic-ray showers', '<span>LHCf gears up to probe birth of cosmic-ray showers</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Ana Lopes</div> + </div> + <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span> +<span>Fri, 11/08/2019 - 13:48</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS"> + <img alt="One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a> + <figcaption> + One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p> + +<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p> + +<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p> + +<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p> + +<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p> + +<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p> + +<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p> + +<p> </p> +</div> + ', true, NULL, '2019-11-11 16:39:03.65', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (15, 'proncero', 'LS2 Report: Linac4 knocking at the door of the PS Booster', '<span>LS2 Report: Linac4 knocking at the door of the PS Booster</span> +<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 10/29/2019 - 14:05</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Busy activity has returned to the CERN Control Centre (CCC), where the Operation group coordinates the current <a href="https://home.cern/science/accelerators/linear-accelerator-4">Linac4</a> test run, supported by the Accelerators and Beam Physics (ABP) group and all the involved equipment groups. As we write, the nominal 160 MeV beam has already reached the Linac4 dump.</p> + +<p>After the ongoing second long shutdown of CERN’s accelerator complex (LS2), Linac4 will replace the retired Linac2 to provide protons to the LHC and all the CERN experiments that are served by CERN’s proton-accelerator chain. “For this purpose, Linac4 has by now been connected to the LHC injector chain through its new transfer line to the PS tunnel and the existing transfer lines to the PS Booster (PSB),” says Bettina Mikulec, who coordinates the test run.</p> + +<p>In order to prepare Linac4 for the challenge of delivering reliably high-quality beam to the PSB from its first day of post-LS2 operation in 2020, a special beam run started on 30 September to measure its beam parameters in the completely renovated 15-m-long emittance-measurement line (LBE), only 50 m away from the PSB injection point. “In this line, we can of course measure the emittance of the beam – the transverse dimensions of the beam and its energy spread – but also its longitudinal parameters in the transfer line,” adds Bettina Mikulec. “The LBE line is also very close to the PSB entrance, so everything we measure there should not be far off from the final characteristics at the PSB injection point.”</p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-127-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1/file?size=large" /></a> +<figcaption>The new LBE line. At the end of this line, we can see the LBE dump (green shielding blocks) located just at the wall of the PSB<span> (Image: CERN)</span></figcaption></figure><p>Until 6 December, negative hydrogen ions* will cover the 86 m of the Linac4 to be sent along the new and renovated transfer lines (160 m in total) into the new LBE line, before terminating their flight in a dump located just at the wall of the PSB.</p> + +<p>“During this run, hardware and software changes deployed since <a href="https://home.cern/news/news/accelerators/long-road-linac4">the last Linac4 reliability run</a>, which took place in 2018, will be commissioned, with the aim of solving some remaining issues and enhance the beam quality,” says Alessandra Lombardi, Linac4 project leader in the ABP group.</p> + +<p>In addition, the required operational beam configurations for the 2020 start-up will be prepared as much as possible in advance to allow a rapid Linac4 start in April 2020, when various beams will be set up for the PSB, so that the PSB can restart with beam under optimum conditions in September 2020.</p> + +<p> </p> + +<p><em>* Hydrogen atoms with an additional electron, giving it a net negative charge. Both electrons are stripped during injection from Linac4 into the PS Booster to leave only protons. </em></p> + +<p>________</p> + +<p><em>Follow the progress of the LBE run on <a class="bulletin" href="https://op-webtools.web.cern.ch/vistar/vistars.php?usr=Linac4">the online Vistar</a>.</em></p> +</div> + ', true, NULL, '2019-11-11 16:39:03.675', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (17, 'proncero', 'CMS measures Higgs boson’s mass with unprecedented precision', '<span>CMS measures Higgs boson’s mass with unprecedented precision</span> +<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 10/25/2019 - 10:37</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692545" data-filename="HtoGammaGamma_v1" id="CMS-PHO-EVENTS-2019-008-4"><a href="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4" title="View on CDS"> + <img alt="Measurement of the Higgs boson mass: candidate two-photon and four-lepton events" src="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4/file?size=medium" /></a> + <figcaption> + Event in which a candidate SM Higgs boson decays into two photons indicated by the green towers representing energy deposited in the electromagnetic calorimeter. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The <a href="https://home.cern/science/physics/higgs-boson">Higgs boson</a> is a special particle. It is the manifestation of a field that gives mass to elementary particles. But this field also gives mass to the Higgs boson itself. A precise measurement of the Higgs boson’s mass not only furthers our knowledge of physics but also sheds new light on searches planned at future colliders.</p> + +<p>Since discovering this unique particle in 2012, the <a href="https://home.cern/science/experiments/atlas">ATLAS</a> and <a href="https://home.cern/science/experiments/cms">CMS</a> collaborations at CERN’s <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> have been busy determining its properties. In the <a href="https://home.cern/science/physics/standard-model">Standard Model of particle physics</a>, the Higgs boson’s mass is closely related to the strength of the particle’s interaction with itself. Comparing precise measurements of these two properties is a crucial means of testing the predictions of the Standard Model and helps search for physics beyond the predictions of this theory. In addition to probing its “self-interaction” strength, the researchers have also paid careful attention to the exact mass of the Higgs boson.</p> + +<p>When it was first discovered, the particle’s mass was measured to be around 125 gigaelectronvolts (GeV) but it wasn’t known with high precision. Analysis of much more data was needed before reducing the errors in such a measurement. Indeed, ATLAS and CMS have been improving this precision with their respective measurements over the years. Last year, ATLAS measured the Higgs mass to be 124.97 GeV with a precision of 0.24 GeV or 0.19%. Now, the CMS collaboration has announced the most precise measurement so far of this property: 125.35 GeV with a precision of 0.15 GeV, or 0.12%.</p> + +<p>Like most members of the zoo of known particles, the Higgs boson is unstable and transforms – or “decays” – nearly instantaneously into lighter particles. The mass measurement was based on two very different transformations of the Higgs boson, namely decays to four leptons via two intermediate Z bosons and decays to pairs of photons. To arrive at the mass value, the scientists combined CMS results of these two decays from two datasets: the first was recorded in 2011 and 2012 while the second came from 2016.</p> + +<p>This measurement adds another piece to the puzzle of the exciting world of subatomic particles.</p> + +<p><em>More details on the <a href="https://cms.cern/news/cms-precisely-measures-mass-higgs-boson">CMS website</a>.</em></p> +</div> + ', true, NULL, '2019-11-11 16:39:03.676', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (18, 'proncero', 'ALICE: the journey of a cosmopolitan detector', '<span>ALICE: the journey of a cosmopolitan detector</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Camille Monnin</div> + </div> + <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span> +<span>Thu, 10/31/2019 - 10:04</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p> + +<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p> + +<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p> + +<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p> + +<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p> + +<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-128-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1/file?size=large" /></a> +<figcaption>A detector piece from Berkeley Lab, on its way to CERN.<span> (Image: Lawrence Berkeley National Laboratory)</span></figcaption></figure><p> </p> +</div> + ', true, NULL, '2019-11-12 09:39:46.793', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (20, 'proncero', 'Broadening tunnel vision for future accelerators', '<span>Broadening tunnel vision for future accelerators</span> +<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Wed, 10/23/2019 - 10:20</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692937" data-filename="201910-334_08" id="CERN-PHOTO-201910-334-8"><a href="//cds.cern.ch/images/CERN-PHOTO-201910-334-8" title="View on CDS"> + <img alt="HL-LHC Underground civil engineering galleries progress" src="//cds.cern.ch/images/CERN-PHOTO-201910-334-8/file?size=medium" /></a> + <figcaption> + HL-LHC Underground civil engineering galleries + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>What could the next generation of particle accelerators look like? With current technology, the bigger an accelerator, the higher the energy of the collisions it produces and the greater the likelihood of discovering new physics phenomena. Particle physicists and accelerator engineers therefore dream of machines that are even bigger than the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC), with its 27-km circumference.</p> + +<p>For CERN’s civil engineers, a new accelerator requires a bespoke deep-underground tunnel, and the tunnel’s shape, depth and orientation as well as its access shafts are largely constrained by the local geography. Such an accelerator built at CERN would be bound by mountains, and, if circular, would need to go under Lake Geneva and completely enclose the Salève mountain of the Prealps.</p> + +<figure class="cds-image breakout-right" id="OPEN-PHO-CIVIL-2019-001-1"><a href="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1" title="View on CDS"><img alt="home.cern,Civil Engineering and Infrastructure" src="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1/file?size=medium" /></a> +<figcaption>Two proposed post-LHC accelerators – CLIC and the FCC – present unique challenges to CERN’s civil engineers<span> (Image: CERN)</span></figcaption></figure><p>The two largest projects under consideration for a post-LHC collider at CERN are the <a href="https://home.cern/science/accelerators/compact-linear-collider">Compact Linear Collider</a> (CLIC) and the <a href="https://home.cern/science/accelerators/future-circular-collider">Future Circular Collider</a> (FCC). Their scale would dwarf CERN’s existing infrastructure, making them some of the largest tunnelling projects in the world. Civil engineers therefore need to survey the geological, environmental and technical constraints of these machines.</p> + +<p>A <a href="https://indico.cern.ch/event/823271/">tunnelling workshop</a> that took place last week at CERN brought together civil-engineering experts from industry and academia to examine how new technologies and methods could optimise tunnel design and asset management. It is part of ongoing collaborations that have already seen CERN and the engineering consultancy Arup develop a first-of-its-kind tunnel optimisation tool to provide the best design when fed all the required parameters. The tool has already shown the feasibility of tunnels for either the FCC or CLIC in the local area, to help support the ongoing update for the European Strategy of Particle Physics that will guide the direction of particle physics and related fields to the mid-2020s and beyond.</p> + +<p>Find out more about the tunnelling challenges of CERN’s civil engineers for the next-generation of particle accelerators in “<a href="https://cerncourier.com/a/tunnelling-for-physics/">Tunnelling for Physics</a>” on the <em>CERN Courier</em>’s website.</p> +</div> + ', true, NULL, '2019-11-12 09:39:46.966', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (21, 'proncero', 'Beamline for Schools 2019 participants present results', '<span>Beamline for Schools 2019 participants present results</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Joseph Piergrossi</div> + </div> + <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 11/08/2019 - 13:58</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS"> + <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a> + <figcaption> + The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p> + +<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p> + +<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p> + +<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p> + +<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p> + +<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p> + +<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p> + +<p>Want to join? Preregistration for BL4S 2020 is <a href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p> + +<hr /><p>More photos <a href="https://cds.cern.ch/record/2698994">on CDS</a>:</p> + +<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p> +</div> + ', true, NULL, '2019-11-12 09:39:46.796', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (22, 'proncero', 'LHCf gears up to probe birth of cosmic-ray showers', '<span>LHCf gears up to probe birth of cosmic-ray showers</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Ana Lopes</div> + </div> + <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span> +<span>Fri, 11/08/2019 - 13:48</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS"> + <img alt="One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a> + <figcaption> + One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p> + +<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p> + +<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p> + +<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p> + +<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p> + +<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p> + +<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p> + +<p> </p> +</div> + ', true, NULL, '2019-11-12 09:39:46.795', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (23, 'proncero', 'Medipix: Two decades of turning technology into applications', '<span>Medipix: Two decades of turning technology into applications</span> +<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 10/18/2019 - 10:11</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2253263" data-filename="studio%2000051" id="CERN-PHOTO-201702-048-3"><a href="//cds.cern.ch/images/CERN-PHOTO-201702-048-3" title="View on CDS"> + <img alt="Knowledge Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201702-048-3/file?size=medium" /></a> + <figcaption><span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>How could microchips developed for detectors at the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC) be used beyond high-energy physics? This was a question that led to the <a href="https://cern.ch/medipix">Medipix</a> and Timepix families of pixel-sensor chips. Researchers saw many possible applications for this technology, and for the last 20 years these chips have been used in medical imaging, in spotting forgeries in the art world, in detecting radioactive material and more. A <a href="https://indico.cern.ch/event/782801/timetable/">recent CERN symposium</a> commemorated the two decades since the Medipix2 collaboration was established, in 1999.</p> + +<p>Pixel-sensor chips are used in detectors at the LHC to trace the paths of electrically charged particles. When a particle hits the sensor, it deposits a charge that is processed by the electronics. This is similar to light hitting pixels in a digital camera, but instead they register particles up to 40 million times a second.</p> + +<p>In the late 1990s, engineers and physicists at CERN were developing integrated circuits for pixel technologies. They realised that adding a counter to each pixel and counting the number of particles hitting the sensors could allow the chips to be used for medical imaging. The Medipix2 chip was born. Later, the Timepix chip added the ability to record either the arrival time of the particles or the energy deposited within a pixel.</p> + +<p>As the chips evolved from Medipix2 to Medipix3, their growing use in medical imaging led to the <a href="https://home.cern/news/news/knowledge-sharing/first-3d-colour-x-ray-human-using-cern-technology">first colour X-ray of parts of the human body</a> in 2018, with the first clinical trials now beginning in New Zealand. In addition, the versatile chips have gone beyond medicine, for example, a start-up called InsightART allows researchers to use Medipix3 chips to <a href="https://home.cern/news/news/knowledge-sharing/particle-detectors-meet-canvas">peer through the layers of works of art</a> and study the composition of materials to determine the authenticity of pieces attributed to renowned artists.</p> + +<p>The team behind InsightART, based in Prague, <a href="https://insightart.eu/2018/06/08/is-this-a-newly-discovered-van-gogh/">recently scanned an alleged Van Gogh</a>, concluding that the work was most likely to have been produced by the Dutch master, having observed an underlying sketch very similar to other figures Van Gogh painted at the time. The work will be sent to the Van Gogh Museum to be vetted with this evidence, and it might be that not one but two Van Goghs have been found in the same piece.</p> + +<p><a href="https://medipix.web.cern.ch/news/nasa-cern-timepix-technology-advances-miniaturized-radiation-detection">Timepix-based detectors have been aboard the International Space Station since 2012</a> to measure the radiation dose to which astronauts and equipment are exposed, and in 2015, high-school students from the UK <a href="https://home.cern/news/news/knowledge-sharing/tim-peakes-timpix-launch-space">sent </a><a href="https://home.cern/news/news/knowledge-sharing/tim-peakes-timpix-launch-space">their own</a> Timepix-based detector to the ISS with astronaut Tim Peake. The ability of the chips to detect gamma rays has been exploited to help with the decommissioning of nuclear reactors and is being evaluated for the detection of thyroid cancer with greater resolution than before and with a lower radiation dose to the patient.</p> + +<p>The Medipix and Timepix chips, developed by three collaborations involving 32 institutes in total, have been remarkable examples of <a href="https://kt.cern/">knowledge transfer from CERN</a> to wider society. You can learn more about the history of Medipix and their many applications <a class="bulletin" href="https://cds.cern.ch/video/2678560?showTitle=true">in this talk</a> by Medipix spokesperson Michael Campbell, given in June 2019.</p> + +<p><iframe allowfullscreen="" frameborder="0" height="360" src="https://cds.cern.ch/video/2678560?showTitle=true" width="640"></iframe></p> +</div> + ', true, NULL, '2019-11-12 09:39:46.964', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (47, 'proncero', 'LHCf gears up to probe birth of cosmic-ray showers', '<span>LHCf gears up to probe birth of cosmic-ray showers</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Ana Lopes</div> + </div> + <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span> +<span>Fri, 11/08/2019 - 13:48</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS"> + <img alt="One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a> + <figcaption> + One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p> + +<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p> + +<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p> + +<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p> + +<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p> + +<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p> + +<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p> + +<p> </p> +</div> + ', true, NULL, '2019-11-15 11:21:33.627', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (48, 'proncero', 'LS2 Report: LHCb looks to the future with SciFi detector', '<span>LS2 Report: LHCb looks to the future with SciFi detector</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Achintya Rao</div> + </div> + <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Tue, 11/12/2019 - 08:53</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2701306" data-filename="201911-373_04" id="CERN-PHOTO-201911-373-4"><a href="//cds.cern.ch/images/CERN-PHOTO-201911-373-4" title="View on CDS"> + <img alt="LHCb''s new scintillating-fibre (SciFi) tracker" src="//cds.cern.ch/images/CERN-PHOTO-201911-373-4/file?size=medium" /></a> + <figcaption> + The new tracker is made of over 10,000 kilometres of polystyrene-based scintillating fibres and will help LHCb record data at a higher luminosity and rate from Run 3 onwards + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the <a href="https://home.cern/science/experiments/lhcb">LHCb detector</a> at the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a>, the ongoing <a href="https://home.cern/tags/long-shutdown-2">second long shutdown (LS2)</a> of CERN’s accelerator complex will be a period of metamorphosis. After two successful data-collection runs, the detector is being upgraded to improve the precision of its physics measurements, many of which are the best in the world. There will therefore be five times more collisions every time proton bunches cross within the detector after LS2 and the LHCb collaboration plans on increasing the data-readout rate from 1 MHz to the LHC’s maximum interaction frequency of 40 MHz (or every 25 nanoseconds).</p> + +<p>In addition to replacing nearly all of the electronics and data-acquisition systems to handle the enormous increase in data production, LHCb is replacing its tracking detectors with new ones, such as the scintillating-fibre tracker, or SciFi. It is the first time such a large tracker, with a small granularity and high spatial resolution, has been made using this technology. The SciFi will be placed behind the dipole magnet of LHCb.</p> + +<p>Scintillating fibres, as the name suggests, are optical fibres – with a polystyrene base, in this case – that emit tens of photons in the blue-green wavelength when a particle interacts with them. Secondary scintillator dyes have been added to the polystyrene to amplify the light and shift it to longer wavelengths so it can reach custom-made silicon photomultipliers (SiPM) that convert optical light to electrical signals. The technology has been well tested at other high-energy-physics experiments. The fibres themselves are lightweight, they can produce and transmit light within the 25-nanosecond window and they are suitably tolerant to the ionising radiation expected in the future.</p> + +<p>Each scintillating fibre making up the sub-detector is 0.25 mm in diameter and nearly 2.5 m in length. The fibres will be packed into modules that will reside in three stations within LHCb, each made of four so-called “detection planes”, with the photomultipliers located at the top and bottom of each plane. “The fibres have been painstakingly examined, wound into multi-layer ribbons, assembled into detector modules and thoroughly tested,” explains Blake Leverington, who is coordinating part of the SciFi project for LHCb. “The fibres provide a single-hit precision better than 100 microns and the single-hit efficiency over the area of the detector is better than 99%.” In total, over 10 000 km of precision-made scintillating fibres will adorn LHCb.</p> + +<p>Unlike the other LHC detectors, LHCb is asymmetric in design and studies particles that fly very close to the beam pipe after being produced in proton–proton collisions. However, operating a sensitive detector this close to the beam pipe brings its own problems. Simulations show that radiation damage from collision debris would darken the fibres closest to the beam pipe by up to 40% over the lifetime of LHCb. This would make it harder for the produced light to be transmitted through the fibres, but the detector is expected to remain efficient despite this.</p> + +<p>The photomultipliers located at the top and bottom of each SciFi detection plane will be bombarded by neutrons produced in the calorimeters that sit further downstream. The radiation damage results in so-called “dark noise”, where thermally excited electrons cause the SiPMs to produce a signal that mimics the signal coming from individual photons. In addition to shielding placed between the SciFi and the calorimeters, a complex cooling system has been developed to chill the SiPMs. “Measurements have shown that the rate of dark noise can be reduced by a factor of two for every 10 °C drop in temperature,” points out Leverington. The SiPMs have been mounted on special 3D-printed titanium cold-bars that are cooled to −40 °C.</p> + +<p>“The project has had contributions from more than a hundred scientists, students, engineers and technicians from 17 partner institutes in 10 countries,” says Leverington. “We have worked together for seven years to bring SciFi to life.” Currently, the SciFi modules, services and electronics are being assembled and installed in the 12 mechanical frames in the assembly hall at the LHCb site at Point 8 of the LHC ring. The first SciFi components are planned to be installed in spring next year.</p> +</div> + ', true, NULL, '2019-11-15 11:30:30.955', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (49, 'proncero', 'Beamline for Schools 2019 participants present results', '<span>Beamline for Schools 2019 participants present results</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Joseph Piergrossi</div> + </div> + <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 11/08/2019 - 13:58</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS"> + <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a> + <figcaption> + The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p> + +<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p> + +<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p> + +<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p> + +<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p> + +<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p> + +<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p> + +<p>Want to join? Preregistration for BL4S 2020 is <a class="bulletin" href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p> + +<hr /><p>More photos <a class="bulletin" href="https://cds.cern.ch/record/2698994">on CDS</a></p> + +<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p> +</div> + ', true, NULL, '2019-11-15 11:30:30.955', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (51, 'proncero', 'Spacewalk for AMS: Watch live with CERN and ESA', '<span>Spacewalk for AMS: Watch live with CERN and ESA</span> +<span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span> +<span>Thu, 11/14/2019 - 12:33</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>On Friday 15 November, European Space Agency (ESA) astronaut Luca Parmitano and NASA astronaut Andrew Morgan will begin the first of a series of complex spacewalks to service the <a href="https://home.cern/science/experiments/ams">Alpha Magnetic Spectrometer (AMS-02)</a>. The spacewalk will be streamed live via <a href="http://www.esa.int/ESA_Multimedia/ESA_Web_TV">ESA Web TV</a> from 12.50 p.m. CET and will include commentaries from CERN and ESA.</p> + +<p>This series of spacewalks is expected to be the most challenging since those to repair the <a href="https://www.nasa.gov/mission_pages/hubble/servicing/index.html">Hubble Space Telescope</a>. AMS was originally intended to run for three years, after its installation on the International Space Station in 2011, and was not designed to be maintained in orbit. However, the success of its results to date have meant that its mission has been extended.</p> + +<figure><iframe allowfullscreen="" frameborder="0" height="360" id="ls_embed_1573808401" scrolling="no" src="https://livestream.com/accounts/362/events/8890996/player?width=640&height=360&enableInfoAndActivity=true&defaultDrawer=&autoPlay=true&mute=false" width="640"></iframe> +<figcaption>Watch the spacewalk live on <a href="https://livestream.com/ESA/SpacewalkforAMS">ESA Web TV</a></figcaption></figure><p>AMS-02 is a particle-physics detector that uses the unique environment of space to study the universe and its origin. It searches for antimatter and dark matter while precisely measuring cosmic-ray particles – more than 140 billion particles to date. The detector, which measures 60 cubic metres and weighs 7.5 tonnes, was assembled by an international team at CERN, and researchers, astronauts and operations teams have had to develop new procedures and more than 20 custom tools to extend the instrument’s life.</p> + +<p>A key task for the astronauts is to replace the AMS-02 cooling system and to fix a coolant leak, and the pair have trained extensively for this intricate operation on the ground. It will involve cutting and splicing eight cooling tubes, connecting them to the new system and reconnecting a myriad of power and data cables. It is the first time that astronauts will cut and reconnect cooling lines in orbit.</p> + +<p>The first AMS spacewalk on Friday is expected to last about six hours and sets the scene for at least three more. It will be streamed live on <a href="http://www.esa.int/ESA_Multimedia/ESA_Web_TV">ESA Web TV</a> and the first two hours will feature commentary from scientists at the AMS Payload Operations Control Centre (POCC) at CERN as well as astronaut and operation experts at ESA’s astronaut centre in Germany.</p> + +<p>CERN’s contributions will include a tour of the POCC by AMS Experiment and Operations Coordinator Mike Capell, from Massachusetts Institute of Technology (MIT). Here, AMS physicists take 24-hour shifts to operate and control the various components of AMS from the ground. Zhan Zhang, also from MIT, is the lead engineer of the Upgraded Tracker Thermal System, which is being installed during the spacewalks. She will show the laboratory at CERN where an identical spare of the system is kept in space conditions and will explain how the system works and what the astronauts will have to do to install it on the AMS detector in space. AMS scientists Mercedes Paniccia from the University of Geneva, Alberto Oliva from INFN Bologna and Andrei Kounine, from MIT, will explain the science of AMS as the spacewalk takes place and can answer your questions.</p> + +<p>You can already tweet questions ahead of the live broadcast to <a href="https://twitter.com/esaspaceflight">@esaspaceflight</a> or <a href="https://twitter.com/CERN">@CERN</a> using the hashtag <a href="https://twitter.com/hashtag/SpacewalkForAMS">#SpacewalkForAMS</a>.</p> +</div> + ', true, NULL, '2019-11-15 11:30:30.956', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (19, 'proncero', 'Be seen, be safe', '<span>Be seen, be safe</span> +<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 11/05/2019 - 12:27</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a> +<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p> + +<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p> +</div> + ', true, NULL, '2019-11-12 09:39:46.795', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (24, 'proncero', 'How to build beautiful CERN websites ', '<span>How to build beautiful CERN websites </span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Kate Kahle</div> + </div> + <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span> +<span>Tue, 11/05/2019 - 14:19</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p> + +<p>Last year, when D8 was launched at CERN, it was accompanied by a <a href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p> + +<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p> + +<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p> + +<p>If you would like to join the Drupal community to find out the latest news and improvements, <a href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p> +</div> + ', true, NULL, '2019-11-12 09:39:46.997', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (25, 'proncero', 'Halfway towards LHC consolidation', '<span>Halfway towards LHC consolidation</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Corinne Pralavorio</div> + </div> + <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span> +<span>Fri, 10/18/2019 - 11:18</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The Large Hadron Collider is such a huge and sophisticated machine that the slightest alteration requires an enormous amount of work. During the second long shutdown (LS2), teams are hard at work <a href="https://home.cern/news/news/accelerators/more-spring-clean-lhc-magnets">reinforcing the electrical insulation of the accelerator’s superconducting dipole diodes</a>. The LHC contains not one, not two, but 1232 superconducting dipole magnets, each with a diode system to upgrade. That’s why no fewer than 150 people are needed to carry out the 70 000 tasks involved in this work.</p> + +<p>The project is now halfway to completion. One of the machine’s eight sectors, containing 154 magnets, is now closed and the final leak tests are under way. Work is ongoing in the seven other sectors and the teams are working at a rate of ten interconnections consolidated per day.</p> + +<p>The work is part of a broader project called DISMAC (“Diodes Insulation and Superconducting Magnets Consolidation”), which also includes the replacement of magnets and maintenance operations on the current leads, the devices that supply the LHC with electricity. Twenty-two magnets have already been replaced and two others have been removed from the machine in order to replace their beam screens, which are components located in the vacuum chamber.</p> + +<p>A plethora of upgrade and maintenance work is also being carried out in the tunnel on all the equipment, from the cryogenics system to the vacuum, beam instrumentation and technical infrastructures.</p> + +<figure><img alt="magnet,LHC,LS2,tunnel,TI2,Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201906-163-1/file?size=large" /><figcaption>Replacement of one of the LHC superconducting dipole magnets during the accelerator consolidation campaign. (Image: Maximilien Brice and Julien Ordan/CERN)</figcaption></figure><hr /></div> + ', true, NULL, '2019-11-12 09:39:46.998', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (26, 'proncero', 'CMS measures Higgs boson’s mass with unprecedented precision', '<span>CMS measures Higgs boson’s mass with unprecedented precision</span> +<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 10/25/2019 - 10:37</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692545" data-filename="HtoGammaGamma_v1" id="CMS-PHO-EVENTS-2019-008-4"><a href="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4" title="View on CDS"> + <img alt="Measurement of the Higgs boson mass: candidate two-photon and four-lepton events" src="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4/file?size=medium" /></a> + <figcaption> + Event in which a candidate SM Higgs boson decays into two photons indicated by the green towers representing energy deposited in the electromagnetic calorimeter. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The <a href="https://home.cern/science/physics/higgs-boson">Higgs boson</a> is a special particle. It is the manifestation of a field that gives mass to elementary particles. But this field also gives mass to the Higgs boson itself. A precise measurement of the Higgs boson’s mass not only furthers our knowledge of physics but also sheds new light on searches planned at future colliders.</p> + +<p>Since discovering this unique particle in 2012, the <a href="https://home.cern/science/experiments/atlas">ATLAS</a> and <a href="https://home.cern/science/experiments/cms">CMS</a> collaborations at CERN’s <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> have been busy determining its properties. In the <a href="https://home.cern/science/physics/standard-model">Standard Model of particle physics</a>, the Higgs boson’s mass is closely related to the strength of the particle’s interaction with itself. Comparing precise measurements of these two properties is a crucial means of testing the predictions of the Standard Model and helps search for physics beyond the predictions of this theory. In addition to probing its “self-interaction” strength, the researchers have also paid careful attention to the exact mass of the Higgs boson.</p> + +<p>When it was first discovered, the particle’s mass was measured to be around 125 gigaelectronvolts (GeV) but it wasn’t known with high precision. Analysis of much more data was needed before reducing the errors in such a measurement. Indeed, ATLAS and CMS have been improving this precision with their respective measurements over the years. Last year, ATLAS measured the Higgs mass to be 124.97 GeV with a precision of 0.24 GeV or 0.19%. Now, the CMS collaboration has announced the most precise measurement so far of this property: 125.35 GeV with a precision of 0.15 GeV, or 0.12%.</p> + +<p>Like most members of the zoo of known particles, the Higgs boson is unstable and transforms – or “decays” – nearly instantaneously into lighter particles. The mass measurement was based on two very different transformations of the Higgs boson, namely decays to four leptons via two intermediate Z bosons and decays to pairs of photons. To arrive at the mass value, the scientists combined CMS results of these two decays from two datasets: the first was recorded in 2011 and 2012 while the second came from 2016.</p> + +<p>This measurement adds another piece to the puzzle of the exciting world of subatomic particles.</p> + +<p><em>More details on the <a href="https://cms.cern/news/cms-precisely-measures-mass-higgs-boson">CMS website</a>.</em></p> +</div> + ', true, NULL, '2019-11-12 09:39:46.994', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (27, 'proncero', 'LS2 Report: Linac4 knocking at the door of the PS Booster', '<span>LS2 Report: Linac4 knocking at the door of the PS Booster</span> +<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 10/29/2019 - 14:05</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Busy activity has returned to the CERN Control Centre (CCC), where the Operation group coordinates the current <a href="https://home.cern/science/accelerators/linear-accelerator-4">Linac4</a> test run, supported by the Accelerators and Beam Physics (ABP) group and all the involved equipment groups. As we write, the nominal 160 MeV beam has already reached the Linac4 dump.</p> + +<p>After the ongoing second long shutdown of CERN’s accelerator complex (LS2), Linac4 will replace the retired Linac2 to provide protons to the LHC and all the CERN experiments that are served by CERN’s proton-accelerator chain. “For this purpose, Linac4 has by now been connected to the LHC injector chain through its new transfer line to the PS tunnel and the existing transfer lines to the PS Booster (PSB),” says Bettina Mikulec, who coordinates the test run.</p> + +<p>In order to prepare Linac4 for the challenge of delivering reliably high-quality beam to the PSB from its first day of post-LS2 operation in 2020, a special beam run started on 30 September to measure its beam parameters in the completely renovated 15-m-long emittance-measurement line (LBE), only 50 m away from the PSB injection point. “In this line, we can of course measure the emittance of the beam – the transverse dimensions of the beam and its energy spread – but also its longitudinal parameters in the transfer line,” adds Bettina Mikulec. “The LBE line is also very close to the PSB entrance, so everything we measure there should not be far off from the final characteristics at the PSB injection point.”</p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-127-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1/file?size=large" /></a> +<figcaption>The new LBE line. At the end of this line, we can see the LBE dump (green shielding blocks) located just at the wall of the PSB<span> (Image: CERN)</span></figcaption></figure><p>Until 6 December, negative hydrogen ions* will cover the 86 m of the Linac4 to be sent along the new and renovated transfer lines (160 m in total) into the new LBE line, before terminating their flight in a dump located just at the wall of the PSB.</p> + +<p>“During this run, hardware and software changes deployed since <a href="https://home.cern/news/news/accelerators/long-road-linac4">the last Linac4 reliability run</a>, which took place in 2018, will be commissioned, with the aim of solving some remaining issues and enhance the beam quality,” says Alessandra Lombardi, Linac4 project leader in the ABP group.</p> + +<p>In addition, the required operational beam configurations for the 2020 start-up will be prepared as much as possible in advance to allow a rapid Linac4 start in April 2020, when various beams will be set up for the PSB, so that the PSB can restart with beam under optimum conditions in September 2020.</p> + +<p> </p> + +<p><em>* Hydrogen atoms with an additional electron, giving it a net negative charge. Both electrons are stripped during injection from Linac4 into the PS Booster to leave only protons. </em></p> + +<p>________</p> + +<p><em>Follow the progress of the LBE run on <a class="bulletin" href="https://op-webtools.web.cern.ch/vistar/vistars.php?usr=Linac4">the online Vistar</a>.</em></p> +</div> + ', true, NULL, '2019-11-12 09:39:46.996', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (28, 'proncero', 'Broadening tunnel vision for future accelerators', '<span>Broadening tunnel vision for future accelerators</span> +<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Wed, 10/23/2019 - 10:20</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692937" data-filename="201910-334_08" id="CERN-PHOTO-201910-334-8"><a href="//cds.cern.ch/images/CERN-PHOTO-201910-334-8" title="View on CDS"> + <img alt="HL-LHC Underground civil engineering galleries progress" src="//cds.cern.ch/images/CERN-PHOTO-201910-334-8/file?size=medium" /></a> + <figcaption> + HL-LHC Underground civil engineering galleries + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>What could the next generation of particle accelerators look like? With current technology, the bigger an accelerator, the higher the energy of the collisions it produces and the greater the likelihood of discovering new physics phenomena. Particle physicists and accelerator engineers therefore dream of machines that are even bigger than the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC), with its 27-km circumference.</p> + +<p>For CERN’s civil engineers, a new accelerator requires a bespoke deep-underground tunnel, and the tunnel’s shape, depth and orientation as well as its access shafts are largely constrained by the local geography. Such an accelerator built at CERN would be bound by mountains, and, if circular, would need to go under Lake Geneva and completely enclose the Salève mountain of the Prealps.</p> + +<figure class="cds-image breakout-right" id="OPEN-PHO-CIVIL-2019-001-1"><a href="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1" title="View on CDS"><img alt="home.cern,Civil Engineering and Infrastructure" src="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1/file?size=medium" /></a> +<figcaption>Two proposed post-LHC accelerators – CLIC and the FCC – present unique challenges to CERN’s civil engineers<span> (Image: CERN)</span></figcaption></figure><p>The two largest projects under consideration for a post-LHC collider at CERN are the <a href="https://home.cern/science/accelerators/compact-linear-collider">Compact Linear Collider</a> (CLIC) and the <a href="https://home.cern/science/accelerators/future-circular-collider">Future Circular Collider</a> (FCC). Their scale would dwarf CERN’s existing infrastructure, making them some of the largest tunnelling projects in the world. Civil engineers therefore need to survey the geological, environmental and technical constraints of these machines.</p> + +<p>A <a href="https://indico.cern.ch/event/823271/">tunnelling workshop</a> that took place last week at CERN brought together civil-engineering experts from industry and academia to examine how new technologies and methods could optimise tunnel design and asset management. It is part of ongoing collaborations that have already seen CERN and the engineering consultancy Arup develop a first-of-its-kind tunnel optimisation tool to provide the best design when fed all the required parameters. The tool has already shown the feasibility of tunnels for either the FCC or CLIC in the local area, to help support the ongoing update for the European Strategy of Particle Physics that will guide the direction of particle physics and related fields to the mid-2020s and beyond.</p> + +<p>Find out more about the tunnelling challenges of CERN’s civil engineers for the next-generation of particle accelerators in “<a href="https://cerncourier.com/a/tunnelling-for-physics/">Tunnelling for Physics</a>” on the <em>CERN Courier</em>’s website.</p> +</div> + ', true, NULL, '2019-11-12 11:16:29.71', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (29, 'proncero', 'ALICE: the journey of a cosmopolitan detector', '<span>ALICE: the journey of a cosmopolitan detector</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Camille Monnin</div> + </div> + <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span> +<span>Thu, 10/31/2019 - 10:04</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p> + +<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p> + +<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p> + +<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p> + +<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p> + +<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-128-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1/file?size=large" /></a> +<figcaption>A detector piece from Berkeley Lab, on its way to CERN.<span> (Image: Lawrence Berkeley National Laboratory)</span></figcaption></figure><p> </p> +</div> + ', true, NULL, '2019-11-12 11:16:29.71', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (30, 'proncero', 'LS2 Report: Linac4 knocking at the door of the PS Booster', '<span>LS2 Report: Linac4 knocking at the door of the PS Booster</span> +<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 10/29/2019 - 14:05</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Busy activity has returned to the CERN Control Centre (CCC), where the Operation group coordinates the current <a href="https://home.cern/science/accelerators/linear-accelerator-4">Linac4</a> test run, supported by the Accelerators and Beam Physics (ABP) group and all the involved equipment groups. As we write, the nominal 160 MeV beam has already reached the Linac4 dump.</p> + +<p>After the ongoing second long shutdown of CERN’s accelerator complex (LS2), Linac4 will replace the retired Linac2 to provide protons to the LHC and all the CERN experiments that are served by CERN’s proton-accelerator chain. “For this purpose, Linac4 has by now been connected to the LHC injector chain through its new transfer line to the PS tunnel and the existing transfer lines to the PS Booster (PSB),” says Bettina Mikulec, who coordinates the test run.</p> + +<p>In order to prepare Linac4 for the challenge of delivering reliably high-quality beam to the PSB from its first day of post-LS2 operation in 2020, a special beam run started on 30 September to measure its beam parameters in the completely renovated 15-m-long emittance-measurement line (LBE), only 50 m away from the PSB injection point. “In this line, we can of course measure the emittance of the beam – the transverse dimensions of the beam and its energy spread – but also its longitudinal parameters in the transfer line,” adds Bettina Mikulec. “The LBE line is also very close to the PSB entrance, so everything we measure there should not be far off from the final characteristics at the PSB injection point.”</p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-127-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1/file?size=large" /></a> +<figcaption>The new LBE line. At the end of this line, we can see the LBE dump (green shielding blocks) located just at the wall of the PSB<span> (Image: CERN)</span></figcaption></figure><p>Until 6 December, negative hydrogen ions* will cover the 86 m of the Linac4 to be sent along the new and renovated transfer lines (160 m in total) into the new LBE line, before terminating their flight in a dump located just at the wall of the PSB.</p> + +<p>“During this run, hardware and software changes deployed since <a href="https://home.cern/news/news/accelerators/long-road-linac4">the last Linac4 reliability run</a>, which took place in 2018, will be commissioned, with the aim of solving some remaining issues and enhance the beam quality,” says Alessandra Lombardi, Linac4 project leader in the ABP group.</p> + +<p>In addition, the required operational beam configurations for the 2020 start-up will be prepared as much as possible in advance to allow a rapid Linac4 start in April 2020, when various beams will be set up for the PSB, so that the PSB can restart with beam under optimum conditions in September 2020.</p> + +<p> </p> + +<p><em>* Hydrogen atoms with an additional electron, giving it a net negative charge. Both electrons are stripped during injection from Linac4 into the PS Booster to leave only protons. </em></p> + +<p>________</p> + +<p><em>Follow the progress of the LBE run on <a class="bulletin" href="https://op-webtools.web.cern.ch/vistar/vistars.php?usr=Linac4">the online Vistar</a>.</em></p> +</div> + ', true, NULL, '2019-11-12 11:16:29.879', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (31, 'proncero', 'Beamline for Schools 2019 participants present results', '<span>Beamline for Schools 2019 participants present results</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Joseph Piergrossi</div> + </div> + <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 11/08/2019 - 13:58</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS"> + <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a> + <figcaption> + The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p> + +<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p> + +<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p> + +<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p> + +<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p> + +<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p> + +<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p> + +<p>Want to join? Preregistration for BL4S 2020 is <a href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p> + +<hr /><p>More photos <a href="https://cds.cern.ch/record/2698994">on CDS</a>:</p> + +<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p> +</div> + ', true, NULL, '2019-11-12 11:16:29.81', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (32, 'proncero', 'Computer Security: When CERN.CH is not CERN…', '<span>Computer Security: When CERN.CH is not CERN…</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">The Computer Security Team</div> + </div> + <span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 11/12/2019 - 11:34</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>We recently received an e-mail from a colleague who was astonished to learn that an e-mail that appears to be sent from “CERN.CH” does not necessarily really come from someone at CERN… Indeed, everything is not always what it seems. Therefore, let us explain to you when CERN.CH is CERN and when it isn’t.</p> + +<p>For e-mail, the sender address can be anything. Just like on the envelope of a normal hand-written letter, any sender address can be specified. “CERN.CH” can easily be spoofed so that an e-mail looks like it comes from someone at CERN, but actually doesn’t<sup>1</sup>. The ancient e-mail protocol cannot do better and any technical means to improve on this break other functions when sending e-mails (like posting to mailing lists...) – see our <em>Bulletin</em> article “<a href="https://cds.cern.ch/record/2215901?ln=en">E-mail is broken and there is nothing we can do</a>”. There is no good protection apart from CERN’s SPAM filters. Once an e-mail has passed those filters, the second line of defence is you... So, just hold on a second and think about whether each e-mail is really intended for you. See our recommendations on how to identify malicious e-mails on <a href="https://cern.ch/security/recommendations/en/malicious_email.shtml">the Computer Security Team’s homepage</a>. If you’re really in doubt, just ask us to check by e-mailing Computer.Security@cern.ch.</p> + +<p>And since we are already on the subject: no, similar domains with different endings (so-called top-level domains like .CH) are definitely not CERN’s! For example, browsing to CERN.CA gives you “…a non-profit organisation in Canada striving to promote the Francophone culture throughout the country”. CERN.BE points to a neuropsychologist. And CERN.SK is the webpage of a Slovak central register for work-related accidents… Moreover, there are also many other domains that look like CERN’s but aren’t: CERM.CH, CERN.ORG, CERN.CG, XERN.CH, CEM.CH (this one is more difficult to detect in lowercase as “cem.ch” – “r” and “n” look quite like “m”, don’t they?). These are usually called typo-squatting or Doppelgänger domains, i.e. domains whose name is just one character away from CERN’s. Attackers love them as they can be used to trick us into clicking on the wrong link: “cem.ch”, anyone?</p> + +<p>For your protection, since adversaries might try to use them for their malicious deeds, we have blocked a series of these typo-squatting domains within CERN’s domain name servers. That means that you should be redirected to a warning page instead of arriving at the adversary’s malicious one. However, this only protects you when browsing to those domains from within CERN. For a more holistic approach, we also tried to buy some of these domains in order to prevent any abuse, but didn’t succeed in all cases...</p> + +<p>Therefore, once more, we have to count on you: security is not complete without you! Be vigilant!!! CERN is CERN.CH and dotCERN. Any other domain does not belong to the Organization<sup>2</sup> and should be accessed with care. The best thing is just to ignore these domains and go somewhere else. Or ping us at Computer.Security@cern.ch and we will check for you whether or not a domain is benign.</p> + +<p> </p> + +<p><em><sup>1</sup>For the technically-minded among you: checking the so-called header information does reveal the real origin of an e-mail unless this has also been heavily tampered with. If that information points to the CERN e-mail servers, it is most likely that the mail has been sent from a real CERN e-mail address. Still, there is no guarantee that the sender is the person behind the name in that e-mail address. His or her account might have been compromised. But that’s another story. </em></p> + +<p><em><sup>2</sup>For the pettifoggers among you: CERN does indeed own a series of other domains: e.g. CERN.EU, CERN.JOBS and CERN.ORG, but also CIXP.CH, INDICO.GLOBAL, OHWR.COM, REANA.IO, ZENODO.COM. But mentioning all of those would double the length of this article…</em></p> + +<p>_________</p> + +<p><em>Do you want to learn more about computer security incidents and issues at CERN? Follow our <a href="https://cern.ch/security/reports/en/monthly_reports.shtml">Monthly Report</a>. For further information, questions or help, check <a href="https://cern.ch/Computer.Security">our website</a> or contact us at Computer.Security@cern.ch.</em></p> +</div> + ', true, NULL, '2019-11-12 11:16:29.709', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (33, 'proncero', 'Be seen, be safe', '<span>Be seen, be safe</span> +<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 11/05/2019 - 12:27</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a> +<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p> + +<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p> +</div> + ', true, NULL, '2019-11-12 11:16:29.706', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (50, 'proncero', 'Aligning the HL-LHC magnets with interferometry', '<span>Aligning the HL-LHC magnets with interferometry</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Anaïs Schaeffer</div> + </div> + <span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 11/12/2019 - 09:35</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>CERN surveyors have just finalised a system that can determine, in real time, the position of certain components inside the (sealed) cryostats of the future <a href="https://home.cern/science/accelerators/high-luminosity-lhc">High-Luminosity LHC</a> (HL-LHC). Currently, only the position of the cryostats themselves can be measured, using sensors that perform continuous measurements. “This new system has been specially developed for the HL-LHC, to be able directly to determine the position of cold masses at the level of the inner triplets, located on either side of the ATLAS and CMS experiments, and the position of the crab cavities inside their cryostat,” says Hélène Mainaud Durand, in charge of alignment in the High-Luminosity LHC upgrade. “It will be a real plus to be able to monitor the alignment of these components continuously, especially during the accelerator’s cycles of heating and cooling.”</p> + +<p>The new procedure is based on frequency sweeping interferometry (FSI), a distance-measurement method that simultaneously performs several absolute distance measurements between a measuring head and targets, and relates them to a common benchmark measurement. “Thanks to this technique, it will be possible to deduce the position of the cold mass to within a few micrometres relative to the cryostat by making 12 distance measurements between the cryostat and the cold mass,” says Mainaud Durand. Each cold mass will therefore be equipped with 12 targets, which are reflective glass spheres that have been specially designed for this procedure. Opposite the targets are 12 laser heads, which are attached to the cryostat and connected by optical fibres to a laser acquisition system.</p> + +<p>Even though FSI is commonly used in metrology, adapting it for use in a cryogenic environment has not been completely straightforward: “We have had to overcome several challenges posed by the extreme conditions inside the accelerators,” says Mateusz Sosin, the mechatronic engineer in charge of this development. “The first problem became apparent during a test carried out at the cryogenic temperature of 1.9 K (–271.3 °C) on one of the LHC dipoles fitted with the system. At this temperature, the cold masses contract and lose up to 12 mm, taking our interferometry targets with them, meaning the targets are no longer aligned with the laser heads.” To get around the problem, a divergent, or conical, laser beam has been developed, such that the source remains “in the spotlight” despite the movements caused by contraction and expansion.</p> + +<p>The second problem is caused by condensation. At 1.9 K, the targets are covered by a fine layer of frost caused by the condensation of residual gases, which make them impervious to the laser beams. “Following the advice of our colleagues in the cryostat section, we decided to use the thermal radiation emitted by the vacuum vessel to heat up the targets,” explains Mateusz Sosin. “The radiation is ‘absorbed’ by an aluminium plate located under the target, keeping it at just the right temperature to avoid condensation. The plate is attached to an epoxy insulating support, which is in turn attached to the cold mass.”</p> + +<p>Several tests have already been carried out, including on <a href="https://home.cern/news/news/engineering/crabs-settled-tunnel">a crab cavity prototype installed in the SPS</a>, as well as on an LHC dipole. The final tests, currently in progress, look very promising, and surveyors from other laboratories, notably DESY and Fermilab, have already shown great interest.</p> +</div> + ', true, NULL, '2019-11-15 11:30:30.956', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (34, 'proncero', 'Halfway towards LHC consolidation', '<span>Halfway towards LHC consolidation</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Corinne Pralavorio</div> + </div> + <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span> +<span>Fri, 10/18/2019 - 11:18</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The Large Hadron Collider is such a huge and sophisticated machine that the slightest alteration requires an enormous amount of work. During the second long shutdown (LS2), teams are hard at work <a href="https://home.cern/news/news/accelerators/more-spring-clean-lhc-magnets">reinforcing the electrical insulation of the accelerator’s superconducting dipole diodes</a>. The LHC contains not one, not two, but 1232 superconducting dipole magnets, each with a diode system to upgrade. That’s why no fewer than 150 people are needed to carry out the 70 000 tasks involved in this work.</p> + +<p>The project is now halfway to completion. One of the machine’s eight sectors, containing 154 magnets, is now closed and the final leak tests are under way. Work is ongoing in the seven other sectors and the teams are working at a rate of ten interconnections consolidated per day.</p> + +<p>The work is part of a broader project called DISMAC (“Diodes Insulation and Superconducting Magnets Consolidation”), which also includes the replacement of magnets and maintenance operations on the current leads, the devices that supply the LHC with electricity. Twenty-two magnets have already been replaced and two others have been removed from the machine in order to replace their beam screens, which are components located in the vacuum chamber.</p> + +<p>A plethora of upgrade and maintenance work is also being carried out in the tunnel on all the equipment, from the cryogenics system to the vacuum, beam instrumentation and technical infrastructures.</p> + +<figure><img alt="magnet,LHC,LS2,tunnel,TI2,Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201906-163-1/file?size=large" /><figcaption>Replacement of one of the LHC superconducting dipole magnets during the accelerator consolidation campaign. (Image: Maximilien Brice and Julien Ordan/CERN)</figcaption></figure><hr /></div> + ', true, NULL, '2019-11-12 11:16:29.816', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (35, 'proncero', 'How to build beautiful CERN websites ', '<span>How to build beautiful CERN websites </span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Kate Kahle</div> + </div> + <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span> +<span>Tue, 11/05/2019 - 14:19</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p> + +<p>Last year, when D8 was launched at CERN, it was accompanied by a <a href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p> + +<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p> + +<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p> + +<p>If you would like to join the Drupal community to find out the latest news and improvements, <a class="bulletin" href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p> +</div> + ', true, NULL, '2019-11-12 11:16:29.864', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (36, 'proncero', 'CMS measures Higgs boson’s mass with unprecedented precision', '<span>CMS measures Higgs boson’s mass with unprecedented precision</span> +<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 10/25/2019 - 10:37</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692545" data-filename="HtoGammaGamma_v1" id="CMS-PHO-EVENTS-2019-008-4"><a href="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4" title="View on CDS"> + <img alt="Measurement of the Higgs boson mass: candidate two-photon and four-lepton events" src="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4/file?size=medium" /></a> + <figcaption> + Event in which a candidate SM Higgs boson decays into two photons indicated by the green towers representing energy deposited in the electromagnetic calorimeter. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The <a href="https://home.cern/science/physics/higgs-boson">Higgs boson</a> is a special particle. It is the manifestation of a field that gives mass to elementary particles. But this field also gives mass to the Higgs boson itself. A precise measurement of the Higgs boson’s mass not only furthers our knowledge of physics but also sheds new light on searches planned at future colliders.</p> + +<p>Since discovering this unique particle in 2012, the <a href="https://home.cern/science/experiments/atlas">ATLAS</a> and <a href="https://home.cern/science/experiments/cms">CMS</a> collaborations at CERN’s <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> have been busy determining its properties. In the <a href="https://home.cern/science/physics/standard-model">Standard Model of particle physics</a>, the Higgs boson’s mass is closely related to the strength of the particle’s interaction with itself. Comparing precise measurements of these two properties is a crucial means of testing the predictions of the Standard Model and helps search for physics beyond the predictions of this theory. In addition to probing its “self-interaction” strength, the researchers have also paid careful attention to the exact mass of the Higgs boson.</p> + +<p>When it was first discovered, the particle’s mass was measured to be around 125 gigaelectronvolts (GeV) but it wasn’t known with high precision. Analysis of much more data was needed before reducing the errors in such a measurement. Indeed, ATLAS and CMS have been improving this precision with their respective measurements over the years. Last year, ATLAS measured the Higgs mass to be 124.97 GeV with a precision of 0.24 GeV or 0.19%. Now, the CMS collaboration has announced the most precise measurement so far of this property: 125.35 GeV with a precision of 0.15 GeV, or 0.12%.</p> + +<p>Like most members of the zoo of known particles, the Higgs boson is unstable and transforms – or “decays” – nearly instantaneously into lighter particles. The mass measurement was based on two very different transformations of the Higgs boson, namely decays to four leptons via two intermediate Z bosons and decays to pairs of photons. To arrive at the mass value, the scientists combined CMS results of these two decays from two datasets: the first was recorded in 2011 and 2012 while the second came from 2016.</p> + +<p>This measurement adds another piece to the puzzle of the exciting world of subatomic particles.</p> + +<p><em>More details on the <a href="https://cms.cern/news/cms-precisely-measures-mass-higgs-boson">CMS website</a>.</em></p> +</div> + ', true, NULL, '2019-11-12 11:16:29.877', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (37, 'proncero', 'LHCf gears up to probe birth of cosmic-ray showers', '<span>LHCf gears up to probe birth of cosmic-ray showers</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Ana Lopes</div> + </div> + <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span> +<span>Fri, 11/08/2019 - 13:48</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS"> + <img alt="One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a> + <figcaption> + One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p> + +<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p> + +<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p> + +<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p> + +<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p> + +<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p> + +<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p> + +<p> </p> +</div> + ', true, NULL, '2019-11-12 11:16:29.818', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (39, 'proncero', 'Spacewalk for AMS: Watch live with CERN and ESA', '<span>Spacewalk for AMS: Watch live with CERN and ESA</span> +<span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span> +<span>Thu, 11/14/2019 - 12:33</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>On Friday 15 November, European Space Agency (ESA) astronaut Luca Parmitano and NASA astronaut Andrew Morgan will begin the first of a series of complex spacewalks to service the <a href="https://home.cern/science/experiments/ams">Alpha Magnetic Spectrometer (AMS-02)</a>. The spacewalk will be streamed live via <a href="http://www.esa.int/ESA_Multimedia/ESA_Web_TV">ESA Web TV</a> from 12.50 p.m. CET and will include commentaries from CERN and ESA.</p> + +<p>This series of spacewalks is expected to be the most challenging since those to repair the <a href="https://www.nasa.gov/mission_pages/hubble/servicing/index.html">Hubble Space Telescope</a>. AMS was originally intended to run for three years, after its installation on the International Space Station in 2011, and was not designed to be maintained in orbit. However, the success of its results to date have meant that its mission has been extended.</p> + +<figure><iframe allowfullscreen="" frameborder="0" height="360" id="ls_embed_1573808401" scrolling="no" src="https://livestream.com/accounts/362/events/8890996/player?width=640&height=360&enableInfoAndActivity=true&defaultDrawer=&autoPlay=true&mute=false" width="640"></iframe> +<figcaption>Watch the spacewalk live on <a href="https://livestream.com/ESA/SpacewalkforAMS">ESA Web TV</a></figcaption></figure><p>AMS-02 is a particle-physics detector that uses the unique environment of space to study the universe and its origin. It searches for antimatter and dark matter while precisely measuring cosmic-ray particles – more than 140 billion particles to date. The detector, which measures 60 cubic metres and weighs 7.5 tonnes, was assembled by an international team at CERN, and researchers, astronauts and operations teams have had to develop new procedures and more than 20 custom tools to extend the instrument’s life.</p> + +<p>A key task for the astronauts is to replace the AMS-02 cooling system and to fix a coolant leak, and the pair have trained extensively for this intricate operation on the ground. It will involve cutting and splicing eight cooling tubes, connecting them to the new system and reconnecting a myriad of power and data cables. It is the first time that astronauts will cut and reconnect cooling lines in orbit.</p> + +<p>The first AMS spacewalk on Friday is expected to last about six hours and sets the scene for at least three more. It will be streamed live on <a href="http://www.esa.int/ESA_Multimedia/ESA_Web_TV">ESA Web TV</a> and the first two hours will feature commentary from scientists at the AMS Payload Operations Control Centre (POCC) at CERN as well as astronaut and operation experts at ESA’s astronaut centre in Germany.</p> + +<p>CERN’s contributions will include a tour of the POCC by AMS Experiment and Operations Coordinator Mike Capell, from Massachusetts Institute of Technology (MIT). Here, AMS physicists take 24-hour shifts to operate and control the various components of AMS from the ground. Zhan Zhang, also from MIT, is the lead engineer of the Upgraded Tracker Thermal System, which is being installed during the spacewalks. She will show the laboratory at CERN where an identical spare of the system is kept in space conditions and will explain how the system works and what the astronauts will have to do to install it on the AMS detector in space. AMS scientists Mercedes Paniccia from the University of Geneva, Alberto Oliva from INFN Bologna and Andrei Kounine, from MIT, will explain the science of AMS as the spacewalk takes place and can answer your questions.</p> + +<p>You can already tweet questions ahead of the live broadcast to <a href="https://twitter.com/esaspaceflight">@esaspaceflight</a> or <a href="https://twitter.com/CERN">@CERN</a> using the hashtag <a href="https://twitter.com/hashtag/SpacewalkForAMS">#SpacewalkForAMS</a>.</p> +</div> + ', true, NULL, '2019-11-15 11:21:33.553', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (38, 'proncero', 'Probing dark matter using antimatter', '<span>Probing dark matter using antimatter</span> +<span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span> +<span>Tue, 11/12/2019 - 10:11</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p><a href="https://home.cern/science/physics/dark-matter">Dark matter</a> and the <a href="https://home.cern/science/physics/matter-antimatter-asymmetry-problem">imbalance between matter and antimatter</a> are two of the biggest mysteries of the universe. Astronomical observations tell us that dark matter makes up most of the matter in the cosmos but we do not know what it is made of. On the other hand, theories of the early universe predict that both antimatter and matter should have been produced in equal amounts, yet for some reason matter prevailed. Could there be a relation between this matter–antimatter asymmetry and dark matter?</p> + +<p>In a <a href="https://www.nature.com/articles/s41586-019-1727-9">paper</a> published today in the journal Nature, the <a href="https://home.cern/science/experiments/base">BASE </a>collaboration reports the first laboratory search for an interaction between antimatter and a dark-matter candidate, the hypothetical axion. A possible interaction would not only establish the origin of dark matter, but would also revolutionise long-established certainties about the symmetry properties of nature. Working at <a href="http://visit.cern/ad">CERN’s antimatter factory</a>, the BASE team obtained the first laboratory-based limits on the existence of dark-matter axions, assuming that they prefer to interact with antimatter rather than with matter.</p> + +<p>Axions were originally introduced to explain the symmetry properties of the strong force, which binds quarks into protons and neutrons, and protons and neutrons into nuclei. Their existence is also predicted by many theories beyond the <a href="https://home.cern/science/physics/standard-model">Standard Model</a>, notably superstring theories. They would be light and interact very weakly with other particles. Being stable, axions produced during the Big Bang would still be present throughout the universe, possibly accounting for observed dark matter. The so-called wave–particle duality of quantum mechanics would cause the dark-matter axion’s field to oscillate, at a frequency proportional to the axion’s mass. This oscillation would vary the intensity of this field’s interactions with matter and antimatter in the laboratory, inducing periodic variations in their properties.</p> + +<p>Laboratory experiments made with ordinary matter have so far shown no evidence of these oscillations, setting stringent limits on the existence of cosmic axions. The established laws of physics predict that axions interact in the same way with protons and antiprotons (the antiparticles of protons), but it is the role of experiments to challenge such wisdom, in this particular case by directly probing the existence of dark-matter axions using antiprotons.</p> + +<p>In their study, the BASE researchers searched for the oscillations in the rotational motion of the antiproton’s magnetic moment or “spin” – think of the wobbling motion of a spinning top just before it stops spinning; it spins around its rotational axis and “precesses” around a vertical axis. An unexpectedly large axion–antiproton interaction strength would lead to variations in the frequency of this precession.</p> + +<p>To look for the oscillations, the researchers first took antiprotons from CERN’s antimatter factory, the only place in the world where antiprotons are created on a daily basis. They then confined them in a device called a Penning trap to avoid their coming into contact with ordinary matter and annihilating. Next, they fed a single antiproton into a high-precision multi-Penning trap to measure and flip its spin state. By performing these measurements almost a thousand times over the course of about three months, they were able to determine a time-averaged frequency of the antiproton’s precession of around 80 megahertz with an uncertainty of 120 millihertz. By looking for regular time variations of the individual measurements over their three-month-long experimental campaign, they were able to probe any possible axion–antiproton interaction for many values of the axion mass.</p> + +<p>The BASE researchers were not able to detect any such variations in their measurements that would reveal a possible axion–antiproton interaction. However, the lack of this signal allowed them to put lower limits on the axion–antiproton interaction strength for a range of possible axion masses. These laboratory-based limits range from 0.1 GeV to 0.6 GeV depending on the assumed axion mass. For comparison, the most precise matter-based experiments achieve much more stringent limits, between about 10 000 and 1 000 000 GeV. This shows that today’s experimental sensitivity would require a major violation of established symmetry properties in order to reveal a possible signal.</p> + +<p>If axions were not a dominant component of dark matter, they could nevertheless be directly produced during the collapse and explosion of stars as supernovae, and limits on their interaction strength with protons or antiprotons could be extracted by examining the evolution of such stellar explosions. The observation of the explosion of the famous supernova SN1987A, however, set constraints on the axion–antiproton interaction strength that are about 100 000 times weaker than those obtained by BASE.</p> + +<p>The new measurements by the BASE collaboration, which teamed up with researchers from the Helmholtz Institute Mainz for this study, provide a novel way to probe dark matter and its possible interaction with antimatter. While relying on specific assumptions about the nature of dark matter and on the pattern of the matter–antimatter asymmetry, the experiment’s results are a unique probe of unexpected new phenomena, which could unveil extraordinary modifications to our established understanding of how the universe works.</p> +</div> + ', true, NULL, '2019-11-15 11:21:33.555', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (40, 'proncero', 'ALICE: the journey of a cosmopolitan detector', '<span>ALICE: the journey of a cosmopolitan detector</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Camille Monnin</div> + </div> + <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span> +<span>Thu, 10/31/2019 - 10:04</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p> + +<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p> + +<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p> + +<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p> + +<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p> + +<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p> +</div> + ', true, NULL, '2019-11-15 11:21:33.623', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (42, 'proncero', 'How to build beautiful CERN websites ', '<span>How to build beautiful CERN websites </span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Kate Kahle</div> + </div> + <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span> +<span>Tue, 11/05/2019 - 14:19</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a class="bulletin" href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p> + +<p>Last year, when D8 was launched at CERN, it was accompanied by a <a class="bulletin" href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a class="bulletin" href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p> + +<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p> + +<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p> + +<p>If you would like to join the Drupal community to find out the latest news and improvements, <a class="bulletin" href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p> +</div> + ', true, NULL, '2019-11-15 11:21:33.623', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (41, 'proncero', 'LS2 Report: LHCb looks to the future with SciFi detector', '<span>LS2 Report: LHCb looks to the future with SciFi detector</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Achintya Rao</div> + </div> + <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Tue, 11/12/2019 - 08:53</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2701306" data-filename="201911-373_04" id="CERN-PHOTO-201911-373-4"><a href="//cds.cern.ch/images/CERN-PHOTO-201911-373-4" title="View on CDS"> + <img alt="LHCb''s new scintillating-fibre (SciFi) tracker" src="//cds.cern.ch/images/CERN-PHOTO-201911-373-4/file?size=medium" /></a> + <figcaption> + The new tracker is made of over 10,000 kilometres of polystyrene-based scintillating fibres and will help LHCb record data at a higher luminosity and rate from Run 3 onwards + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the <a href="https://home.cern/science/experiments/lhcb">LHCb detector</a> at the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a>, the ongoing <a href="https://home.cern/tags/long-shutdown-2">second long shutdown (LS2)</a> of CERN’s accelerator complex will be a period of metamorphosis. After two successful data-collection runs, the detector is being upgraded to improve the precision of its physics measurements, many of which are the best in the world. There will therefore be five times more collisions every time proton bunches cross within the detector after LS2 and the LHCb collaboration plans on increasing the data-readout rate from 1 MHz to the LHC’s maximum interaction frequency of 40 MHz (or every 25 nanoseconds).</p> + +<p>In addition to replacing nearly all of the electronics and data-acquisition systems to handle the enormous increase in data production, LHCb is replacing its tracking detectors with new ones, such as the scintillating-fibre tracker, or SciFi. It is the first time such a large tracker, with a small granularity and high spatial resolution, has been made using this technology. The SciFi will be placed behind the dipole magnet of LHCb.</p> + +<p>Scintillating fibres, as the name suggests, are optical fibres – with a polystyrene base, in this case – that emit tens of photons in the blue-green wavelength when a particle interacts with them. Secondary scintillator dyes have been added to the polystyrene to amplify the light and shift it to longer wavelengths so it can reach custom-made silicon photomultipliers (SiPM) that convert optical light to electrical signals. The technology has been well tested at other high-energy-physics experiments. The fibres themselves are lightweight, they can produce and transmit light within the 25-nanosecond window and they are suitably tolerant to the ionising radiation expected in the future.</p> + +<p>Each scintillating fibre making up the sub-detector is 0.25 mm in diameter and nearly 2.5 m in length. The fibres will be packed into modules that will reside in three stations within LHCb, each made of four so-called “detection planes”, with the photomultipliers located at the top and bottom of each plane. “The fibres have been painstakingly examined, wound into multi-layer ribbons, assembled into detector modules and thoroughly tested,” explains Blake Leverington, who is coordinating part of the SciFi project for LHCb. “The fibres provide a single-hit precision better than 100 microns and the single-hit efficiency over the area of the detector is better than 99%.” In total, over 10 000 km of precision-made scintillating fibres will adorn LHCb.</p> + +<p>Unlike the other LHC detectors, LHCb is asymmetric in design and studies particles that fly very close to the beam pipe after being produced in proton–proton collisions. However, operating a sensitive detector this close to the beam pipe brings its own problems. Simulations show that radiation damage from collision debris would darken the fibres closest to the beam pipe by up to 40% over the lifetime of LHCb. This would make it harder for the produced light to be transmitted through the fibres, but the detector is expected to remain efficient despite this.</p> + +<p>The photomultipliers located at the top and bottom of each SciFi detection plane will be bombarded by neutrons produced in the calorimeters that sit further downstream. The radiation damage results in so-called “dark noise”, where thermally excited electrons cause the SiPMs to produce a signal that mimics the signal coming from individual photons. In addition to shielding placed between the SciFi and the calorimeters, a complex cooling system has been developed to chill the SiPMs. “Measurements have shown that the rate of dark noise can be reduced by a factor of two for every 10 °C drop in temperature,” points out Leverington. The SiPMs have been mounted on special 3D-printed titanium cold-bars that are cooled to −40 °C.</p> + +<p>“The project has had contributions from more than a hundred scientists, students, engineers and technicians from 17 partner institutes in 10 countries,” says Leverington. “We have worked together for seven years to bring SciFi to life.” Currently, the SciFi modules, services and electronics are being assembled and installed in the 12 mechanical frames in the assembly hall at the LHCb site at Point 8 of the LHC ring. The first SciFi components are planned to be installed in spring next year.</p> +</div> + ', true, NULL, '2019-11-15 11:21:33.591', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (43, 'proncero', 'Around the LHC in 252 days ', '<span>Around the LHC in 252 days </span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Corinne Pralavorio</div> + </div> + <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span> +<span>Tue, 11/12/2019 - 14:26</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the teams involved in the <a href="https://home.cern/news/news/accelerators/ls2-report-insulation-lhc-diodes-has-begun">DISMAC (Diode Insulation and Superconducting Magnets Consolidation)</a> project, the LHC tour is a long adventure. On 7 November, they opened the last and 1360th LHC magnet interconnection, 252 days after having opened the first. The electrical insulation work of the magnets’ diodes is done in sequence: opening of the interconnection, cleaning, installation of the insulation, electrical and quality tests, welding, and so on. The teams work sequentially, and the diode insulation is scheduled to be completed next summer.</p> +</div> + ', true, NULL, '2019-11-15 11:21:33.572', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (44, 'proncero', 'Be seen, be safe', '<span>Be seen, be safe</span> +<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 11/05/2019 - 12:27</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a> +<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p> + +<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p> +</div> + ', true, NULL, '2019-11-15 11:21:33.643', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (45, 'proncero', 'Beamline for Schools 2019 participants present results', '<span>Beamline for Schools 2019 participants present results</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Joseph Piergrossi</div> + </div> + <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span> +<span>Fri, 11/08/2019 - 13:58</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS"> + <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a> + <figcaption> + The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p> + +<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p> + +<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p> + +<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p> + +<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p> + +<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p> + +<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p> + +<p>Want to join? Preregistration for BL4S 2020 is <a class="bulletin" href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p> + +<hr /><p>More photos <a class="bulletin" href="https://cds.cern.ch/record/2698994">on CDS</a></p> + +<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p> +</div> + ', true, NULL, '2019-11-15 11:21:33.572', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (46, 'proncero', 'Aligning the HL-LHC magnets with interferometry', '<span>Aligning the HL-LHC magnets with interferometry</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Anaïs Schaeffer</div> + </div> + <span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 11/12/2019 - 09:35</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>CERN surveyors have just finalised a system that can determine, in real time, the position of certain components inside the (sealed) cryostats of the future <a href="https://home.cern/science/accelerators/high-luminosity-lhc">High-Luminosity LHC</a> (HL-LHC). Currently, only the position of the cryostats themselves can be measured, using sensors that perform continuous measurements. “This new system has been specially developed for the HL-LHC, to be able directly to determine the position of cold masses at the level of the inner triplets, located on either side of the ATLAS and CMS experiments, and the position of the crab cavities inside their cryostat,” says Hélène Mainaud Durand, in charge of alignment in the High-Luminosity LHC upgrade. “It will be a real plus to be able to monitor the alignment of these components continuously, especially during the accelerator’s cycles of heating and cooling.”</p> + +<p>The new procedure is based on frequency sweeping interferometry (FSI), a distance-measurement method that simultaneously performs several absolute distance measurements between a measuring head and targets, and relates them to a common benchmark measurement. “Thanks to this technique, it will be possible to deduce the position of the cold mass to within a few micrometres relative to the cryostat by making 12 distance measurements between the cryostat and the cold mass,” says Mainaud Durand. Each cold mass will therefore be equipped with 12 targets, which are reflective glass spheres that have been specially designed for this procedure. Opposite the targets are 12 laser heads, which are attached to the cryostat and connected by optical fibres to a laser acquisition system.</p> + +<p>Even though FSI is commonly used in metrology, adapting it for use in a cryogenic environment has not been completely straightforward: “We have had to overcome several challenges posed by the extreme conditions inside the accelerators,” says Mateusz Sosin, the mechatronic engineer in charge of this development. “The first problem became apparent during a test carried out at the cryogenic temperature of 1.9 K (–271.3 °C) on one of the LHC dipoles fitted with the system. At this temperature, the cold masses contract and lose up to 12 mm, taking our interferometry targets with them, meaning the targets are no longer aligned with the laser heads.” To get around the problem, a divergent, or conical, laser beam has been developed, such that the source remains “in the spotlight” despite the movements caused by contraction and expansion.</p> + +<p>The second problem is caused by condensation. At 1.9 K, the targets are covered by a fine layer of frost caused by the condensation of residual gases, which make them impervious to the laser beams. “Following the advice of our colleagues in the cryostat section, we decided to use the thermal radiation emitted by the vacuum vessel to heat up the targets,” explains Mateusz Sosin. “The radiation is ‘absorbed’ by an aluminium plate located under the target, keeping it at just the right temperature to avoid condensation. The plate is attached to an epoxy insulating support, which is in turn attached to the cold mass.”</p> + +<p>Several tests have already been carried out, including on <a href="https://home.cern/news/news/engineering/crabs-settled-tunnel">a crab cavity prototype installed in the SPS</a>, as well as on an LHC dipole. The final tests, currently in progress, look very promising, and surveyors from other laboratories, notably DESY and Fermilab, have already shown great interest.</p> +</div> + ', true, NULL, '2019-11-15 11:21:33.59', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (52, 'proncero', 'Around the LHC in 252 days ', '<span>Around the LHC in 252 days </span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Corinne Pralavorio</div> + </div> + <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span> +<span>Tue, 11/12/2019 - 14:26</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the teams involved in the <a href="https://home.cern/news/news/accelerators/ls2-report-insulation-lhc-diodes-has-begun">DISMAC (Diode Insulation and Superconducting Magnets Consolidation)</a> project, the LHC tour is a long adventure. On 7 November, they opened the last and 1360th LHC magnet interconnection, 252 days after having opened the first. The electrical insulation work of the magnets’ diodes is done in sequence: opening of the interconnection, cleaning, installation of the insulation, electrical and quality tests, welding, and so on. The teams work sequentially, and the diode insulation is scheduled to be completed next summer.</p> +</div> + ', true, NULL, '2019-11-15 11:30:30.966', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (53, 'proncero', 'LHCf gears up to probe birth of cosmic-ray showers', '<span>LHCf gears up to probe birth of cosmic-ray showers</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Ana Lopes</div> + </div> + <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span> +<span>Fri, 11/08/2019 - 13:48</span> + + <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS"> + <img alt="One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a> + <figcaption> + One of the LHCf experiment''s two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC''s beam pipe. + <span> (Image: CERN)</span> + </figcaption></figure></div> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p> + +<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p> + +<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p> + +<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p> + +<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p> + +<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p> + +<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p> + +<p> </p> +</div> + ', true, NULL, '2019-11-15 11:30:30.967', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (54, 'proncero', 'How to build beautiful CERN websites ', '<span>How to build beautiful CERN websites </span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Kate Kahle</div> + </div> + <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span> +<span>Tue, 11/05/2019 - 14:19</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a class="bulletin" href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p> + +<p>Last year, when D8 was launched at CERN, it was accompanied by a <a class="bulletin" href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a class="bulletin" href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p> + +<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p> + +<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p> + +<p>If you would like to join the Drupal community to find out the latest news and improvements, <a class="bulletin" href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p> +</div> + ', true, NULL, '2019-11-15 11:30:30.971', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (55, 'proncero', 'Probing dark matter using antimatter', '<span>Probing dark matter using antimatter</span> +<span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span> +<span>Tue, 11/12/2019 - 10:11</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p><a href="https://home.cern/science/physics/dark-matter">Dark matter</a> and the <a href="https://home.cern/science/physics/matter-antimatter-asymmetry-problem">imbalance between matter and antimatter</a> are two of the biggest mysteries of the universe. Astronomical observations tell us that dark matter makes up most of the matter in the cosmos but we do not know what it is made of. On the other hand, theories of the early universe predict that both antimatter and matter should have been produced in equal amounts, yet for some reason matter prevailed. Could there be a relation between this matter–antimatter asymmetry and dark matter?</p> + +<p>In a <a href="https://www.nature.com/articles/s41586-019-1727-9">paper</a> published today in the journal Nature, the <a href="https://home.cern/science/experiments/base">BASE </a>collaboration reports the first laboratory search for an interaction between antimatter and a dark-matter candidate, the hypothetical axion. A possible interaction would not only establish the origin of dark matter, but would also revolutionise long-established certainties about the symmetry properties of nature. Working at <a href="http://visit.cern/ad">CERN’s antimatter factory</a>, the BASE team obtained the first laboratory-based limits on the existence of dark-matter axions, assuming that they prefer to interact with antimatter rather than with matter.</p> + +<p>Axions were originally introduced to explain the symmetry properties of the strong force, which binds quarks into protons and neutrons, and protons and neutrons into nuclei. Their existence is also predicted by many theories beyond the <a href="https://home.cern/science/physics/standard-model">Standard Model</a>, notably superstring theories. They would be light and interact very weakly with other particles. Being stable, axions produced during the Big Bang would still be present throughout the universe, possibly accounting for observed dark matter. The so-called wave–particle duality of quantum mechanics would cause the dark-matter axion’s field to oscillate, at a frequency proportional to the axion’s mass. This oscillation would vary the intensity of this field’s interactions with matter and antimatter in the laboratory, inducing periodic variations in their properties.</p> + +<p>Laboratory experiments made with ordinary matter have so far shown no evidence of these oscillations, setting stringent limits on the existence of cosmic axions. The established laws of physics predict that axions interact in the same way with protons and antiprotons (the antiparticles of protons), but it is the role of experiments to challenge such wisdom, in this particular case by directly probing the existence of dark-matter axions using antiprotons.</p> + +<p>In their study, the BASE researchers searched for the oscillations in the rotational motion of the antiproton’s magnetic moment or “spin” – think of the wobbling motion of a spinning top just before it stops spinning; it spins around its rotational axis and “precesses” around a vertical axis. An unexpectedly large axion–antiproton interaction strength would lead to variations in the frequency of this precession.</p> + +<p>To look for the oscillations, the researchers first took antiprotons from CERN’s antimatter factory, the only place in the world where antiprotons are created on a daily basis. They then confined them in a device called a Penning trap to avoid their coming into contact with ordinary matter and annihilating. Next, they fed a single antiproton into a high-precision multi-Penning trap to measure and flip its spin state. By performing these measurements almost a thousand times over the course of about three months, they were able to determine a time-averaged frequency of the antiproton’s precession of around 80 megahertz with an uncertainty of 120 millihertz. By looking for regular time variations of the individual measurements over their three-month-long experimental campaign, they were able to probe any possible axion–antiproton interaction for many values of the axion mass.</p> + +<p>The BASE researchers were not able to detect any such variations in their measurements that would reveal a possible axion–antiproton interaction. However, the lack of this signal allowed them to put lower limits on the axion–antiproton interaction strength for a range of possible axion masses. These laboratory-based limits range from 0.1 GeV to 0.6 GeV depending on the assumed axion mass. For comparison, the most precise matter-based experiments achieve much more stringent limits, between about 10 000 and 1 000 000 GeV. This shows that today’s experimental sensitivity would require a major violation of established symmetry properties in order to reveal a possible signal.</p> + +<p>If axions were not a dominant component of dark matter, they could nevertheless be directly produced during the collapse and explosion of stars as supernovae, and limits on their interaction strength with protons or antiprotons could be extracted by examining the evolution of such stellar explosions. The observation of the explosion of the famous supernova SN1987A, however, set constraints on the axion–antiproton interaction strength that are about 100 000 times weaker than those obtained by BASE.</p> + +<p>The new measurements by the BASE collaboration, which teamed up with researchers from the Helmholtz Institute Mainz for this study, provide a novel way to probe dark matter and its possible interaction with antimatter. While relying on specific assumptions about the nature of dark matter and on the pattern of the matter–antimatter asymmetry, the experiment’s results are a unique probe of unexpected new phenomena, which could unveil extraordinary modifications to our established understanding of how the universe works.</p> +</div> + ', true, NULL, '2019-11-15 11:30:30.971', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (56, 'proncero', 'ALICE: the journey of a cosmopolitan detector', '<span>ALICE: the journey of a cosmopolitan detector</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Camille Monnin</div> + </div> + <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span> +<span>Thu, 10/31/2019 - 10:04</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p> + +<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p> + +<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p> + +<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p> + +<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p> + +<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p> +</div> + ', true, NULL, '2019-11-15 11:30:30.975', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (57, 'proncero', 'Be seen, be safe', '<span>Be seen, be safe</span> +<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span> +<span>Tue, 11/05/2019 - 12:27</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p> + +<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a> +<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p> + +<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p> +</div> + ', true, NULL, '2019-11-15 11:30:30.975', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (58, 'bsilvade', 'Password of account "Push Service Mailbox (push)" will expire in 5 day(s)', ' Version francaise en fin de ce message +Password Expiration +Dear Push Service Mailbox, + +The password of the account "Push Service Mailbox (push)" will expire in 5 day(s). +Actions Required + + * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * Access to the central services such as Mail, Admin Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password. + +Get Help + + * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch) + * Note: Please do not reply to this message which is generated by a robot, you will not get any answer. + +Best regards, +CERN IT Department. + +Expiration du mot de passe +Cher/Chère Push Service Mailbox, + +Le mot de passe du compte "Push Service Mailbox (push)" va expirer dans 5 jour(s). +Actions requises + + * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * L''accès aux services centraux comme le Mail, les services administratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe. + +Obtenir de l''aide + + * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>) + * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n'' obtiendrez pas de réponse. + +Cordialement, +CERN Département IT +', true, NULL, '2019-11-17 00:00:55.625', NULL, NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (59, 'push', 'Password of account "Push Service Mailbox (push)" will expire in 5 day(s)', ' Version francaise en fin de ce message +Password Expiration +Dear Push Service Mailbox, + +The password of the account "Push Service Mailbox (push)" will expire in 5 day(s). +Actions Required + + * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * Access to the central services such as Mail, Admin Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password. + +Get Help + + * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch) + * Note: Please do not reply to this message which is generated by a robot, you will not get any answer. + +Best regards, +CERN IT Department. + +Expiration du mot de passe +Cher/Chère Push Service Mailbox, + +Le mot de passe du compte "Push Service Mailbox (push)" va expirer dans 5 jour(s). +Actions requises + + * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * L''accès aux services centraux comme le Mail, les services administratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe. + +Obtenir de l''aide + + * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>) + * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n'' obtiendrez pas de réponse. + +Cordialement, +CERN Département IT +', true, NULL, '2019-11-17 00:00:55.625', NULL, NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (61, 'push', 'Password of account "Push Service Mailbox (push)" will expire in 3 day(s)', ' Version francaise en fin de ce message +Password Expiration +Dear Push Service Mailbox, + +The password of the account "Push Service Mailbox (push)" will expire in 3 day(s). +Actions Required + + * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * Access to the central services such as Mail, Admin Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password. + +Get Help + + * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch) + * Note: Please do not reply to this message which is generated by a robot, you will not get any answer. + +Best regards, +CERN IT Department. + +Expiration du mot de passe +Cher/Chère Push Service Mailbox, + +Le mot de passe du compte "Push Service Mailbox (push)" va expirer dans 3 jour(s). +Actions requises + + * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * L''accès aux services centraux comme le Mail, les services administratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe. + +Obtenir de l''aide + + * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>) + * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n'' obtiendrez pas de réponse. + +Cordialement, +CERN Département IT +', true, NULL, '2019-11-19 00:00:40.917', NULL, NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (62, 'bsilvade', 'Password of account "Push Service Mailbox (push)" will expire in 1 day(s)', ' Version francaise en fin de ce message +Password Expiration +Dear Push Service Mailbox, + +The password of the account "Push Service Mailbox (push)" will expire in 1 day(s). +Actions Required + + * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * Access to the central services such as Mail, Admin Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password. + +Get Help + + * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch) + * Note: Please do not reply to this message which is generated by a robot, you will not get any answer. + +Best regards, +CERN IT Department. + +Expiration du mot de passe +Cher/Chère Push Service Mailbox, + +Le mot de passe du compte "Push Service Mailbox (push)" va expirer dans 1 jour(s). +Actions requises + + * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * L''accès aux services centraux comme le Mail, les services administratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe. + +Obtenir de l''aide + + * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>) + * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n'' obtiendrez pas de réponse. + +Cordialement, +CERN Département IT +', true, NULL, '2019-11-21 00:00:39.458', NULL, NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (63, 'push', 'Password of account "Push Service Mailbox (push)" will expire in 1 day(s)', ' Version francaise en fin de ce message +Password Expiration +Dear Push Service Mailbox, + +The password of the account "Push Service Mailbox (push)" will expire in 1 day(s). +Actions Required + + * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * Access to the central services such as Mail, Admin Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password. + +Get Help + + * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch) + * Note: Please do not reply to this message which is generated by a robot, you will not get any answer. + +Best regards, +CERN IT Department. + +Expiration du mot de passe +Cher/Chère Push Service Mailbox, + +Le mot de passe du compte "Push Service Mailbox (push)" va expirer dans 1 jour(s). +Actions requises + + * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * L''accès aux services centraux comme le Mail, les services administratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe. + +Obtenir de l''aide + + * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>) + * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n'' obtiendrez pas de réponse. + +Cordialement, +CERN Département IT +', true, NULL, '2019-11-21 00:00:39.46', NULL, NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (64, 'proncero', 'LS2 report: The PS is rejuvenated for its 60th birthday', '<span>LS2 report: The PS is rejuvenated for its 60th birthday</span> + + <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items"> + <div class="field--item">Corinne Pralavorio</div> + </div> + <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span> +<span>Mon, 11/25/2019 - 15:36</span> + + <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>On 24 November 1959, the Proton Synchotron (PS) accelerated its first beams, making it the most powerful accelerator in the world at the time. Who would have thought that 60 years later, this machine would still be one of the main cogs in the CERN accelerator complex? Incredibly, the PS is still in service. It will even be made more efficient with a bit of tender loving care during this second long shutdown. The <a href="https://home.cern/fr/news/opinion/accelerators/time-lhc-injectors-upgrade-project">LHC Injectors Upgrade (LIU) project</a> includes a long list of <a href="https://home.cern/fr/news/news/accelerators/ls2-report-proton-synchrotrons-magnets-prepare-higher-energies">work to be carried out on the accelerator and its entire infrastructure</a>.</p> + +<p>With the first link in the chain of accelerators being replaced by <a href="https://home.cern/fr/news/news/accelerators/brand-new-linear-accelerator-cern">Linac 4</a>, protons will be injected into the PS Booster at 160 MeV, and then accelerated to 2 GeV (up from 1.4 GeV previously) before being sent to the PS. This is why the PS proton injection line, which is about 20 metres in length, will be entirely replaced. To date, the quadrupole magnets have been installed together with a septum magnet. The equipment will continue to be installed in 2020. The power converters which power the injection line, as well as other LIU equipment, have been replaced and installed in renovated buildings. The cabling is now underway.</p> + +<p>In the 628-metre-long accelerator, half of the main magnets are being renovated. This major project, which entails lengthy handling operations, will soon be finished. “48 of the 100 magnets have been removed and a vast majority have already been reinstalled”, explains Fernando Pedrosa. New equipment such as <a href="https://home.cern/fr/news/news/accelerators/keeping-close-watch-over-beams">beam wire scanners</a> and internal beam dumps will also be installed in the ring. The teams have used the upgrade works as an opportunity to give the accelerator a deep clean, including the cleaning of certain galleries. The cleaning work, as well as the <a href="https://home.cern/fr/news/news/accelerators/ls2-report-linac4-knocking-door-ps-booster">ongoing Linac 4 tests</a>, require part of the PS to be closed making the work more complex to coordinate. Downstream, the extraction line towards the East Area has been entirely dismantled ahead of the new installation in 2020, as part of the <a href="https://home.cern/fr/news/news/accelerators/ls2-report-east-area-version-20">East Experiment Area renovation project</a>.</p> + +<p>In addition to the beam lines, the entire infrastructure is also being renovated. The lighting system has been changed, for example, and major work is being carried out on the cooling system. High luminosity requires more intense beams which entails several changes including increased power for the circuits’ cooling plants. “We have reorganized the entire cooling system to double the flow while also reducing running costs”, explains Serge Delaval, Section Leader for Injectors within the Cooling and Ventilation Group. The two plants that use short cooling towers will therefore be replaced with one central plant, which uses a single cooling tower composed of four units. Two of these units were no longer in use and have been fully upgraded.</p> + +<p>At the same time, all the pumps and heat exchangers have been replaced, together with three kilometres of pipes! “We have used this consolidation as an opportunity to reduce the environmental impact, particularly regarding the products used to prevent Legionnaire’s disease”, says Serge Delaval. Stainless steel has therefore been chosen over steel as it requires much less anti-corrosion treatment. Similarly, demineralised water will also be used for some circuits.</p> + +<p>Work on the cooling system will continue until March and the accelerator upgrade is slated to be finished at the start of next summer.</p> +</div> + ', true, NULL, '2019-11-25 14:37:21.6', 'test-con-dani', NULL, NULL, NULL, NULL, NULL, 'NORMAL'); +INSERT INTO push_test."Notifications" VALUES (60, 'bsilvade', 'Password of account "Push Service Mailbox (push)" will expire in 3 day(s)', ' Version francaise en fin de ce message +Password Expiration +Dear Push Service Mailbox, + +The password of the account "Push Service Mailbox (push)" will expire in 3 day(s). +Actions Required + + * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * Access to the central services such as Mail, Admin Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password. + +Get Help + + * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch) + * Note: Please do not reply to this message which is generated by a robot, you will not get any answer. + +Best regards, +CERN IT Department. + +Expiration du mot de passe +Cher/Chère Push Service Mailbox, + +Le mot de passe du compte "Push Service Mailbox (push)" va expirer dans 3 jour(s). +Actions requises + + * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ). + +Information + + * L''accès aux services centraux comme le Mail, les services administratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe. + +Obtenir de l''aide + + * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>) + * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n'' obtiendrez pas de réponse. + +Cordialement, +CERN Département IT +', true, NULL, '2019-11-19 00:00:40.916', NULL, NULL, NULL, NULL, NULL, NULL, 'NORMAL'); + + +-- +-- Data for Name: Rules; Type: TABLE DATA; Schema: push_test; Owner: admin +-- + +INSERT INTO push_test."Rules" VALUES (1, 'All as push', 'PUSH', 'AllByEmailOrPush', NULL, 'proncero'); + + +-- +-- Data for Name: Services; Type: TABLE DATA; Schema: push_test; Owner: admin +-- + +INSERT INTO push_test."Services" VALUES ('test-con-dani', 'Push Notifications Service', 'push-notifications@cern.ch'); + + +-- +-- Data for Name: UserNotifications; Type: TABLE DATA; Schema: push_test; Owner: admin +-- + +INSERT INTO push_test."UserNotifications" VALUES (5, true, false, false, 'proncero', 5); +INSERT INTO push_test."UserNotifications" VALUES (6, false, false, false, 'proncero', 6); +INSERT INTO push_test."UserNotifications" VALUES (7, false, false, false, 'proncero', 7); +INSERT INTO push_test."UserNotifications" VALUES (9, false, false, false, 'proncero', 12); +INSERT INTO push_test."UserNotifications" VALUES (11, false, false, false, 'proncero', 10); +INSERT INTO push_test."UserNotifications" VALUES (12, false, false, false, 'proncero', 11); +INSERT INTO push_test."UserNotifications" VALUES (13, false, false, false, 'proncero', 8); +INSERT INTO push_test."UserNotifications" VALUES (14, false, false, false, 'proncero', 16); +INSERT INTO push_test."UserNotifications" VALUES (15, false, false, false, 'proncero', 17); +INSERT INTO push_test."UserNotifications" VALUES (16, false, false, false, 'proncero', 14); +INSERT INTO push_test."UserNotifications" VALUES (17, false, false, false, 'proncero', 15); +INSERT INTO push_test."UserNotifications" VALUES (8, true, false, false, 'proncero', 13); +INSERT INTO push_test."UserNotifications" VALUES (10, true, false, false, 'proncero', 9); +INSERT INTO push_test."UserNotifications" VALUES (18, false, false, false, 'proncero', 18); +INSERT INTO push_test."UserNotifications" VALUES (19, false, false, false, 'proncero', 20); +INSERT INTO push_test."UserNotifications" VALUES (20, false, false, false, 'proncero', 24); +INSERT INTO push_test."UserNotifications" VALUES (21, false, false, false, 'proncero', 21); +INSERT INTO push_test."UserNotifications" VALUES (22, false, false, false, 'proncero', 23); +INSERT INTO push_test."UserNotifications" VALUES (23, false, false, false, 'proncero', 22); +INSERT INTO push_test."UserNotifications" VALUES (24, false, false, false, 'proncero', 19); +INSERT INTO push_test."UserNotifications" VALUES (25, false, false, false, 'proncero', 25); +INSERT INTO push_test."UserNotifications" VALUES (26, false, false, false, 'proncero', 26); +INSERT INTO push_test."UserNotifications" VALUES (27, false, false, false, 'proncero', 27); +INSERT INTO push_test."UserNotifications" VALUES (28, false, false, false, 'proncero', 28); +INSERT INTO push_test."UserNotifications" VALUES (29, false, false, false, 'proncero', 29); +INSERT INTO push_test."UserNotifications" VALUES (30, false, false, false, 'proncero', 30); +INSERT INTO push_test."UserNotifications" VALUES (31, false, false, false, 'proncero', 31); +INSERT INTO push_test."UserNotifications" VALUES (32, false, false, false, 'proncero', 32); +INSERT INTO push_test."UserNotifications" VALUES (33, false, false, false, 'proncero', 33); +INSERT INTO push_test."UserNotifications" VALUES (36, false, false, false, 'proncero', 36); +INSERT INTO push_test."UserNotifications" VALUES (37, false, false, false, 'proncero', 37); +INSERT INTO push_test."UserNotifications" VALUES (35, true, false, false, 'proncero', 35); +INSERT INTO push_test."UserNotifications" VALUES (34, true, false, false, 'proncero', 34); +INSERT INTO push_test."UserNotifications" VALUES (38, false, false, false, 'proncero', 39); +INSERT INTO push_test."UserNotifications" VALUES (39, false, false, false, 'proncero', 40); +INSERT INTO push_test."UserNotifications" VALUES (40, false, false, false, 'proncero', 42); +INSERT INTO push_test."UserNotifications" VALUES (41, false, false, false, 'proncero', 41); +INSERT INTO push_test."UserNotifications" VALUES (42, false, false, false, 'proncero', 43); +INSERT INTO push_test."UserNotifications" VALUES (43, false, false, false, 'proncero', 38); +INSERT INTO push_test."UserNotifications" VALUES (44, false, false, false, 'proncero', 44); +INSERT INTO push_test."UserNotifications" VALUES (45, false, false, false, 'proncero', 45); +INSERT INTO push_test."UserNotifications" VALUES (46, false, false, false, 'proncero', 46); +INSERT INTO push_test."UserNotifications" VALUES (47, false, false, false, 'proncero', 47); +INSERT INTO push_test."UserNotifications" VALUES (48, false, false, false, 'proncero', 49); +INSERT INTO push_test."UserNotifications" VALUES (49, false, false, false, 'proncero', 48); +INSERT INTO push_test."UserNotifications" VALUES (50, false, false, false, 'proncero', 50); +INSERT INTO push_test."UserNotifications" VALUES (51, false, false, false, 'proncero', 51); +INSERT INTO push_test."UserNotifications" VALUES (52, false, false, false, 'proncero', 52); +INSERT INTO push_test."UserNotifications" VALUES (53, false, false, false, 'proncero', 53); +INSERT INTO push_test."UserNotifications" VALUES (54, false, false, false, 'proncero', 54); +INSERT INTO push_test."UserNotifications" VALUES (55, false, false, false, 'proncero', 55); +INSERT INTO push_test."UserNotifications" VALUES (56, false, false, false, 'proncero', 56); +INSERT INTO push_test."UserNotifications" VALUES (57, false, false, false, 'proncero', 57); +INSERT INTO push_test."UserNotifications" VALUES (58, false, false, false, 'proncero', 64); + + +-- +-- Data for Name: Users; Type: TABLE DATA; Schema: push_test; Owner: admin +-- + +INSERT INTO push_test."Users" VALUES ('ischuszt', 'cristian.schuszter@cern.ch', 'ey3laSIABxA:APA91bFlSGKhqYNmPmQYGhrgmsWd9zU7mBmL_I3UrN2d7QCvzQF0-7kxifxYT1oTWFIIdymh9J-21DfMuMli3A5rySDSdedCPymmJn94O2Q0F11ociSZzMK6I4iSK6If3-O-vOIq0BqL', true); +INSERT INTO push_test."Users" VALUES ('lolopez', 'lorys.lopez@cern.ch', 'ciPyjjOuHuE:APA91bFFhwXun7PODaf6DJaxab6rc3hj-CPaVwHxcypkLciZdD6-EN5wylBDphREYDEgsvphJnRoYn9s9u_qcb8Uf9HdU9-27-4itO90icF42oc_cGpLJy4ok7WkIKk3pVDHZzfVLXBq', true); +INSERT INTO push_test."Users" VALUES ('proncero', 'pablo.roncero.fernandez@cern.ch', 'cx6RfRePvYs:APA91bH2IEgHD2DoEKAiAHSLO9bMmGSbEU3Vh86UwmvLINQ6bhuG1BMg5ffutIrwAZxhqld146fCaVtl0S1tnstSa0UgyfvIhu-k7p_1l70tr_ZHHTuRXB6pgpWC1j6HqzuooDSkOfoe,dE5-FWr1Aso:APA91bGMtSn6b9SvI_zuNt9xprKEchaatOX6kICrdgw81TI5K8WI4uPcHZJXZYVYIWkoaAdapOOmjsbgZ2wuraMrWZbzc3H8tmSFnte7lWawH3vvmn8JmAVqkRbbPzeMiVuMJcmqE8h6,fX74YVLygho:APA91bERR35zUB7ndBKhNK8JDPwMEsI0sQbp9GTBqgF4A_QT3kWnpby-f61KNJWVZFDyEGHrhGvw62abemL2_QYcYsSkbGubvLN859ywOKHF5zjqF1bg6q8xXbog61U0PXTZayt_SPQR,ebGE9WS41fg:APA91bGATMs56gFxuDB70BZpRBGjl1FSj8hYb8_xvutOTlIXMRNOY_RG-vEVpxy7gU1BkudNXnGq-_K7yg5lvRFPy-66GhDGvwSwlWaYa-7_99EtBH6jR9Y13zTZUwqWeE5TUlroyPrd', true); +INSERT INTO push_test."Users" VALUES ('fernanre', 'rene.fernandez@cern.ch', NULL, true); +INSERT INTO push_test."Users" VALUES ('jalcalap', 'joel.alcala.perez@cern.ch', 'ej1m9KgqUOk:APA91bHjA1wlQ_ZdSKGTGMBaTWk4ub1RoGR_zmRIn3InqkrKP9MnaRkpBn5hQTB8S9fyVYWyTVsKNUKrrQuWGMvVJaA8oY4uk26Jd-JROg9n7NN3ULwYMZGYPTQIIcs-uLkCIYfiVTs_,drANG1NP__o:APA91bG4btX3JMuhkYkjxOUw2rDCDWr-rOZyoGpfj1XY4gNGqBdwphqPvZR2DWxovKL_1MMWvjr6XGY6CBzAHAqIx8_LvYeED3t_YhWgv75EBrC1JM-PZpChMSlau2WKyg1LjNokcf56,f-y7ve-9w1w:APA91bEzviAjngGe4xfdbGB_6l8gVTIllwMWduNG1_j5NCYbCoaRApEPabxXME_uO9u8HwnIkE-SyDePLnJgMrgTDNBxOL4gL99C38r8y9_C2oqnzpFp1yGRhtgRCVMKPvOrUfZGe5fY,fuBXw1nkzZ4:APA91bGE4lH8m3dfWCgAdzD_A6gFZSBq_07HPa7zg9R7ENXOHaxvnwT7Wd8nz_32rWE6dnJ6dvdwK2qzGKfxZhk-giL_H-aCeb3cQSun83h1tc_HD5XIcJ-9PwwmR7uMcfC1p4nrLo2N,fCTqXijsji4:APA91bFh_E4Jo_ym1GWOn_HY3a2M1DCG_4015UCFNJWr2yZwhUzN5h0uqb9DF5ORaDiIc524fWyU_tNVev55T2RbYS2ttZJjq5R_plMNoox05QWuAdwB-AEpgQt9INSoS4CvEousGTp4,e-nbGO176HI:APA91bHIDNgj8nX8vyWIyfnlalapeOQEAUaouAlfiHb5Ip9-AYR_oX0Yu4XmLLwEFou0-8a03hqs2o9BgEHsyia8geYRKK5JBrq7LQMKUUGb4y5jKQVR09ndX6j_Iklitxz-D9TUfdcV,cfLOohDMo8M:APA91bG33rcF6KPrDRjCgnOZVyqaEi0fex69cHiAJCw5WQzIZc0ykXixoFCY_VaBGb5wXa-L_vazPPqR4YMd8rcVvY50-vm6EGcu1td4vcbI_XrloOBolGICMUu1fChDshLaQuqhV3-B,dNFRGEtxZhs:APA91bG7vvCtXSf-kz6JjE_di9CCAzmc-lH1RC_BFO7aBrOKHb7mbjddbZvVFR7vgf2Xu2kp72JmpUqzabx1cXV53oUMWlk_WJJGAMYApJ4jMZ5WlM3PP_clboFGByRPQFBy9njjKg4V', true); + + +-- +-- Data for Name: Notifications; Type: TABLE DATA; Schema: test; Owner: admin +-- + +INSERT INTO test."Notifications" VALUES (470, 'test-push', 'subject', 'body', false, NULL, NULL, 'fakeFrom'); + + +-- +-- Data for Name: Rules; Type: TABLE DATA; Schema: test; Owner: admin +-- + +INSERT INTO test."Rules" VALUES (342, 'EMAIL', 'AllByEmailOrPushRule', NULL, NULL); +INSERT INTO test."Rules" VALUES (343, 'PUSH', 'AllByEmailOrPushRule', NULL, NULL); + + +-- +-- Data for Name: Services; Type: TABLE DATA; Schema: test; Owner: admin +-- + + + +-- +-- Data for Name: Users; Type: TABLE DATA; Schema: test; Owner: admin +-- + +INSERT INTO test."Users" VALUES (1, 'username', 'email@email.com'); + + +-- +-- Data for Name: users_notifications__notifications; Type: TABLE DATA; Schema: test; Owner: admin +-- + + + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE SET; Schema: authorization_service; Owner: admin +-- + +SELECT pg_catalog.setval('authorization_service."Notifications_id_seq"', 1, false); + + +-- +-- Name: Rules_id_seq; Type: SEQUENCE SET; Schema: authorization_service; Owner: admin +-- + +SELECT pg_catalog.setval('authorization_service."Rules_id_seq"', 1, false); + + +-- +-- Name: Services_id_seq; Type: SEQUENCE SET; Schema: authorization_service; Owner: admin +-- + +SELECT pg_catalog.setval('authorization_service."Services_id_seq"', 2, true); + + +-- +-- Name: UserNotifications_id_seq; Type: SEQUENCE SET; Schema: authorization_service; Owner: admin +-- + +SELECT pg_catalog.setval('authorization_service."UserNotifications_id_seq"', 1, false); + + +-- +-- Name: Notfications_id_seq; Type: SEQUENCE SET; Schema: public; Owner: admin +-- + +SELECT pg_catalog.setval('public."Notfications_id_seq"', 36, true); + + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE SET; Schema: public; Owner: admin +-- + +SELECT pg_catalog.setval('public."Notifications_id_seq"', 4, true); + + +-- +-- Name: Users_id_seq; Type: SEQUENCE SET; Schema: public; Owner: admin +-- + +SELECT pg_catalog.setval('public."Users_id_seq"', 1, false); + + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE SET; Schema: push_test; Owner: admin +-- + +SELECT pg_catalog.setval('push_test."Notifications_id_seq"', 64, true); + + +-- +-- Name: Rules_id_seq; Type: SEQUENCE SET; Schema: push_test; Owner: admin +-- + +SELECT pg_catalog.setval('push_test."Rules_id_seq"', 1, true); + + +-- +-- Name: UserNotifications_id_seq; Type: SEQUENCE SET; Schema: push_test; Owner: admin +-- + +SELECT pg_catalog.setval('push_test."UserNotifications_id_seq"', 58, true); + + +-- +-- Name: Notifications_id_seq; Type: SEQUENCE SET; Schema: test; Owner: admin +-- + +SELECT pg_catalog.setval('test."Notifications_id_seq"', 470, true); + + +-- +-- Name: Rules_id_seq; Type: SEQUENCE SET; Schema: test; Owner: admin +-- + +SELECT pg_catalog.setval('test."Rules_id_seq"', 343, true); + + +-- +-- Name: Services_id_seq; Type: SEQUENCE SET; Schema: test; Owner: admin +-- + +SELECT pg_catalog.setval('test."Services_id_seq"', 509, true); + + +-- +-- Name: Rules PK_9966a0656d39b62e1c37ef912ff; Type: CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Rules" + ADD CONSTRAINT "PK_9966a0656d39b62e1c37ef912ff" PRIMARY KEY (id); + + +-- +-- Name: Notifications PK_a8a64c3cdfb69c2b84ea0dc05f9; Type: CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Notifications" + ADD CONSTRAINT "PK_a8a64c3cdfb69c2b84ea0dc05f9" PRIMARY KEY (id); + + +-- +-- Name: Users PK_a8aa2427c1085e957928fdd3809; Type: CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Users" + ADD CONSTRAINT "PK_a8aa2427c1085e957928fdd3809" PRIMARY KEY (id); + + +-- +-- Name: UserNotifications PK_f89dab386c80a39a17ecd1332d8; Type: CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."UserNotifications" + ADD CONSTRAINT "PK_f89dab386c80a39a17ecd1332d8" PRIMARY KEY (id); + + +-- +-- Name: Services PK_fda332019de682bc8e474112b18; Type: CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Services" + ADD CONSTRAINT "PK_fda332019de682bc8e474112b18" PRIMARY KEY (id); + + +-- +-- Name: Services UQ_615bf21e2614a26b3df0aa30ef9; Type: CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Services" + ADD CONSTRAINT "UQ_615bf21e2614a26b3df0aa30ef9" UNIQUE ("apiKey"); + + +-- +-- Name: Services UQ_f2d51af70f67c2dd86657549f26; Type: CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Services" + ADD CONSTRAINT "UQ_f2d51af70f67c2dd86657549f26" UNIQUE (name); + + +-- +-- Name: Users PK_16d4f7d636df336db11d87413e3; Type: CONSTRAINT; Schema: public; Owner: admin +-- + +ALTER TABLE ONLY public."Users" + ADD CONSTRAINT "PK_16d4f7d636df336db11d87413e3" PRIMARY KEY (id); + + +-- +-- Name: Notfications PK_6463423e5cf0ee0261103566099; Type: CONSTRAINT; Schema: public; Owner: admin +-- + +ALTER TABLE ONLY public."Notfications" + ADD CONSTRAINT "PK_6463423e5cf0ee0261103566099" PRIMARY KEY (id); + + +-- +-- Name: Notifications PK_c77268afe7d3c5568da66c5bebe; Type: CONSTRAINT; Schema: public; Owner: admin +-- + +ALTER TABLE ONLY public."Notifications" + ADD CONSTRAINT "PK_c77268afe7d3c5568da66c5bebe" PRIMARY KEY (id); + + +-- +-- Name: Groups PK_1036beb1e2f958e6ffe4af0668c; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Groups" + ADD CONSTRAINT "PK_1036beb1e2f958e6ffe4af0668c" PRIMARY KEY (id); + + +-- +-- Name: preferences_disabled_channels__channels PK_1d577038b06f0c7d5941e6b6d44; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.preferences_disabled_channels__channels + ADD CONSTRAINT "PK_1d577038b06f0c7d5941e6b6d44" PRIMARY KEY ("preferencesId", "channelsId"); + + +-- +-- Name: UserNotifications PK_25b987313e820785e36f789fce9; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."UserNotifications" + ADD CONSTRAINT "PK_25b987313e820785e36f789fce9" PRIMARY KEY (id); + + +-- +-- Name: channels_members__users PK_44aaf4fd010be6d455f0395087d; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.channels_members__users + ADD CONSTRAINT "PK_44aaf4fd010be6d455f0395087d" PRIMARY KEY ("channelsId", "usersId"); + + +-- +-- Name: Notifications PK_4b04b7cc85e5bec41a3e112ab0e; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Notifications" + ADD CONSTRAINT "PK_4b04b7cc85e5bec41a3e112ab0e" PRIMARY KEY (id); + + +-- +-- Name: channels_groups__groups PK_6cfe1ace99c86f42bd1f17976ae; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.channels_groups__groups + ADD CONSTRAINT "PK_6cfe1ace99c86f42bd1f17976ae" PRIMARY KEY ("channelsId", "groupsId"); + + +-- +-- Name: Channels PK_755e126393652c40d8fde456cdc; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Channels" + ADD CONSTRAINT "PK_755e126393652c40d8fde456cdc" PRIMARY KEY (id); + + +-- +-- Name: channels_unsubscribed__users PK_7e89bf0cd584bb1c0452c398031; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.channels_unsubscribed__users + ADD CONSTRAINT "PK_7e89bf0cd584bb1c0452c398031" PRIMARY KEY ("channelsId", "usersId"); + + +-- +-- Name: preferences_devices__devices PK_8b74ee67a4e700ee9f9e3a05150; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.preferences_devices__devices + ADD CONSTRAINT "PK_8b74ee67a4e700ee9f9e3a05150" PRIMARY KEY ("preferencesId", "devicesId"); + + +-- +-- Name: Devices PK_a172be05db88c0a4be502f15c69; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Devices" + ADD CONSTRAINT "PK_a172be05db88c0a4be502f15c69" PRIMARY KEY (id); + + +-- +-- Name: Users PK_a8a84fd043f7210bff4746b62a1; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Users" + ADD CONSTRAINT "PK_a8a84fd043f7210bff4746b62a1" PRIMARY KEY (id); + + +-- +-- Name: UserDailyNotifications PK_be9036b93d1015bc9d51fd217e0; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."UserDailyNotifications" + ADD CONSTRAINT "PK_be9036b93d1015bc9d51fd217e0" PRIMARY KEY (date, "time"); + + +-- +-- Name: Preferences PK_df9d94acb04c3ea85603c634f6b; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Preferences" + ADD CONSTRAINT "PK_df9d94acb04c3ea85603c634f6b" PRIMARY KEY (id); + + +-- +-- Name: Services PK_f7fdeaa9c02e5506593d35a939d; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Services" + ADD CONSTRAINT "PK_f7fdeaa9c02e5506593d35a939d" PRIMARY KEY (id); + + +-- +-- Name: Groups UQ_cbf00aa66f2f7ad0970f73d5ae4; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Groups" + ADD CONSTRAINT "UQ_cbf00aa66f2f7ad0970f73d5ae4" UNIQUE ("groupIdentifier"); + + +-- +-- Name: Services UQ_ef4d2e448dd7b00d8c261787002; Type: CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Services" + ADD CONSTRAINT "UQ_ef4d2e448dd7b00d8c261787002" UNIQUE (name); + + +-- +-- Name: Services PK_166c6340639ab62ac94d78ba7f2; Type: CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."Services" + ADD CONSTRAINT "PK_166c6340639ab62ac94d78ba7f2" PRIMARY KEY (id); + + +-- +-- Name: UserNotifications PK_429928d0e28a02b3277c8e6f7e8; Type: CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."UserNotifications" + ADD CONSTRAINT "PK_429928d0e28a02b3277c8e6f7e8" PRIMARY KEY (id); + + +-- +-- Name: Rules PK_65056b33448fdeed62bb4ac0d42; Type: CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."Rules" + ADD CONSTRAINT "PK_65056b33448fdeed62bb4ac0d42" PRIMARY KEY (id); + + +-- +-- Name: Users PK_a0e1b0c28e14b024f7fd85fdbfe; Type: CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."Users" + ADD CONSTRAINT "PK_a0e1b0c28e14b024f7fd85fdbfe" PRIMARY KEY (username); + + +-- +-- Name: Notifications PK_c305c7e954d1b2c4375911489bd; Type: CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."Notifications" + ADD CONSTRAINT "PK_c305c7e954d1b2c4375911489bd" PRIMARY KEY (id); + + +-- +-- Name: Services UQ_e46db72dd9e489367a9c98dbfd7; Type: CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."Services" + ADD CONSTRAINT "UQ_e46db72dd9e489367a9c98dbfd7" UNIQUE (name); + + +-- +-- Name: users_notifications__notifications PK_142b0d79c7e8ced138efb789357; Type: CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test.users_notifications__notifications + ADD CONSTRAINT "PK_142b0d79c7e8ced138efb789357" PRIMARY KEY ("usersId", "notificationsId"); + + +-- +-- Name: Services PK_7472cc1ebfd534e665360a490c2; Type: CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Services" + ADD CONSTRAINT "PK_7472cc1ebfd534e665360a490c2" PRIMARY KEY (id); + + +-- +-- Name: Rules PK_b4023c95b5e08eaa991cf8b1d29; Type: CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Rules" + ADD CONSTRAINT "PK_b4023c95b5e08eaa991cf8b1d29" PRIMARY KEY (id); + + +-- +-- Name: Users PK_b689c8e952c77a5c49388e7532f; Type: CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Users" + ADD CONSTRAINT "PK_b689c8e952c77a5c49388e7532f" PRIMARY KEY (id); + + +-- +-- Name: Notifications PK_df985fc3cf268e7a9d9eaadb72d; Type: CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Notifications" + ADD CONSTRAINT "PK_df985fc3cf268e7a9d9eaadb72d" PRIMARY KEY (id); + + +-- +-- Name: Services UQ_db452d84cc41f7c8e2ebed2ea25; Type: CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Services" + ADD CONSTRAINT "UQ_db452d84cc41f7c8e2ebed2ea25" UNIQUE (name); + + +-- +-- Name: Services UQ_e36e26e678f6607fed8edffdfb0; Type: CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Services" + ADD CONSTRAINT "UQ_e36e26e678f6607fed8edffdfb0" UNIQUE ("apiKey"); + + +-- +-- Name: IDX_54bdd24814fbfbe635ba1b66e9; Type: INDEX; Schema: authorization_service; Owner: admin +-- + +CREATE INDEX "IDX_54bdd24814fbfbe635ba1b66e9" ON authorization_service."Rules" USING btree (id, type); + + +-- +-- Name: IDX_890c6405f913d40a62f4116674; Type: INDEX; Schema: authorization_service; Owner: admin +-- + +CREATE INDEX "IDX_890c6405f913d40a62f4116674" ON authorization_service."Rules" USING btree (type); + + +-- +-- Name: IDX_d9a995168f69ddf2434d6f3a88; Type: INDEX; Schema: authorization_service; Owner: admin +-- + +CREATE INDEX "IDX_d9a995168f69ddf2434d6f3a88" ON authorization_service."UserNotifications" USING btree ("userId", "notificationId"); + + +-- +-- Name: IDX_27840c586d0da066609ca4434e; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_27840c586d0da066609ca4434e" ON push.channels_unsubscribed__users USING btree ("channelsId"); + + +-- +-- Name: IDX_2acd07b72f49ad4ca8567ce406; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_2acd07b72f49ad4ca8567ce406" ON push.preferences_devices__devices USING btree ("devicesId"); + + +-- +-- Name: IDX_35872830abd309e6fcbe9b1e5c; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_35872830abd309e6fcbe9b1e5c" ON push.preferences_disabled_channels__channels USING btree ("channelsId"); + + +-- +-- Name: IDX_49854fb35cab1068a1b2396c8c; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_49854fb35cab1068a1b2396c8c" ON push.preferences_devices__devices USING btree ("preferencesId"); + + +-- +-- Name: IDX_63d0692973bdb93d0e57ee08e3; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_63d0692973bdb93d0e57ee08e3" ON push.channels_groups__groups USING btree ("groupsId"); + + +-- +-- Name: IDX_6cd3b13bb09aaf62d70ada4fed; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_6cd3b13bb09aaf62d70ada4fed" ON push.channels_members__users USING btree ("usersId"); + + +-- +-- Name: IDX_81c54acb5c0d813a6a9e9c4757; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_81c54acb5c0d813a6a9e9c4757" ON push.channels_unsubscribed__users USING btree ("usersId"); + + +-- +-- Name: IDX_8700bf3fe1dd0fdee82af35b81; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_8700bf3fe1dd0fdee82af35b81" ON push.preferences_disabled_channels__channels USING btree ("preferencesId"); + + +-- +-- Name: IDX_8f468c04ac534b8a2014e6cd93; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_8f468c04ac534b8a2014e6cd93" ON push.channels_groups__groups USING btree ("channelsId"); + + +-- +-- Name: IDX_9081090ad2d7ea6e0b63ad2b9d; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE UNIQUE INDEX "IDX_9081090ad2d7ea6e0b63ad2b9d" ON push."Channels" USING btree (slug, "deleteDate"); + + +-- +-- Name: IDX_c77449f6c8bdd1d0d2135216c7; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE UNIQUE INDEX "IDX_c77449f6c8bdd1d0d2135216c7" ON push."Channels" USING btree (slug); + + +-- +-- Name: IDX_e43debb24060d5c5b6b7d0ddeb; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_e43debb24060d5c5b6b7d0ddeb" ON push."UserDailyNotifications" USING btree ("userId", "notificationId"); + + +-- +-- Name: IDX_ea2669001f79058b012fc1651f; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_ea2669001f79058b012fc1651f" ON push."UserNotifications" USING btree ("userId", "notificationId"); + + +-- +-- Name: IDX_f446f63889a85308fbc5ce0fe0; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE UNIQUE INDEX "IDX_f446f63889a85308fbc5ce0fe0" ON push."Users" USING btree (username); + + +-- +-- Name: IDX_ff62bcfacefb8206dc10dc194f; Type: INDEX; Schema: push; Owner: admin +-- + +CREATE INDEX "IDX_ff62bcfacefb8206dc10dc194f" ON push.channels_members__users USING btree ("channelsId"); + + +-- +-- Name: IDX_8479e16c8f2a9247d6a57ed09a; Type: INDEX; Schema: push_test; Owner: admin +-- + +CREATE INDEX "IDX_8479e16c8f2a9247d6a57ed09a" ON push_test."Rules" USING btree (type); + + +-- +-- Name: IDX_8e2bcc52d13d59d9114dbd6e20; Type: INDEX; Schema: push_test; Owner: admin +-- + +CREATE INDEX "IDX_8e2bcc52d13d59d9114dbd6e20" ON push_test."UserNotifications" USING btree ("userUsername", "notificationId"); + + +-- +-- Name: IDX_8fcccdc5a46e13bb83ee86641b; Type: INDEX; Schema: push_test; Owner: admin +-- + +CREATE INDEX "IDX_8fcccdc5a46e13bb83ee86641b" ON push_test."Rules" USING btree (id, type); + + +-- +-- Name: IDX_54659c03730073cde471d4312c; Type: INDEX; Schema: test; Owner: admin +-- + +CREATE INDEX "IDX_54659c03730073cde471d4312c" ON test."Rules" USING btree (type); + + +-- +-- Name: IDX_f0e7530dea8d4cb6a7c3ac60ed; Type: INDEX; Schema: test; Owner: admin +-- + +CREATE INDEX "IDX_f0e7530dea8d4cb6a7c3ac60ed" ON test."Rules" USING btree (id, type); + + +-- +-- Name: UserNotifications FK_099c9aae30fffd2596c80c2b549; Type: FK CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."UserNotifications" + ADD CONSTRAINT "FK_099c9aae30fffd2596c80c2b549" FOREIGN KEY ("notificationId") REFERENCES authorization_service."Notifications"(id); + + +-- +-- Name: Notifications FK_944d1e34f04d46890758dcfc6fe; Type: FK CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Notifications" + ADD CONSTRAINT "FK_944d1e34f04d46890758dcfc6fe" FOREIGN KEY ("fromId") REFERENCES authorization_service."Services"(id); + + +-- +-- Name: Rules FK_dbf68107a33c0cdd2c1e29d32d5; Type: FK CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."Rules" + ADD CONSTRAINT "FK_dbf68107a33c0cdd2c1e29d32d5" FOREIGN KEY ("userId") REFERENCES authorization_service."Users"(id); + + +-- +-- Name: UserNotifications FK_fa7e9a75ff3922059ac04f642e5; Type: FK CONSTRAINT; Schema: authorization_service; Owner: admin +-- + +ALTER TABLE ONLY authorization_service."UserNotifications" + ADD CONSTRAINT "FK_fa7e9a75ff3922059ac04f642e5" FOREIGN KEY ("userId") REFERENCES authorization_service."Users"(id); + + +-- +-- Name: Notifications FK_166450369eca664db0d44c44fe7; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Notifications" + ADD CONSTRAINT "FK_166450369eca664db0d44c44fe7" FOREIGN KEY ("targetId") REFERENCES push."Channels"(id); + + +-- +-- Name: channels_unsubscribed__users FK_27840c586d0da066609ca4434e9; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.channels_unsubscribed__users + ADD CONSTRAINT "FK_27840c586d0da066609ca4434e9" FOREIGN KEY ("channelsId") REFERENCES push."Channels"(id) ON DELETE CASCADE; + + +-- +-- Name: preferences_devices__devices FK_2acd07b72f49ad4ca8567ce4067; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.preferences_devices__devices + ADD CONSTRAINT "FK_2acd07b72f49ad4ca8567ce4067" FOREIGN KEY ("devicesId") REFERENCES push."Devices"(id) ON DELETE CASCADE; + + +-- +-- Name: Preferences FK_30e4c36856af87f5220f75d3ac0; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Preferences" + ADD CONSTRAINT "FK_30e4c36856af87f5220f75d3ac0" FOREIGN KEY ("userId") REFERENCES push."Users"(id); + + +-- +-- Name: preferences_disabled_channels__channels FK_35872830abd309e6fcbe9b1e5ce; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.preferences_disabled_channels__channels + ADD CONSTRAINT "FK_35872830abd309e6fcbe9b1e5ce" FOREIGN KEY ("channelsId") REFERENCES push."Channels"(id) ON DELETE CASCADE; + + +-- +-- Name: preferences_devices__devices FK_49854fb35cab1068a1b2396c8cf; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.preferences_devices__devices + ADD CONSTRAINT "FK_49854fb35cab1068a1b2396c8cf" FOREIGN KEY ("preferencesId") REFERENCES push."Preferences"(id) ON DELETE CASCADE; + + +-- +-- Name: UserDailyNotifications FK_519b07c613d308d7c5f46b35cd3; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."UserDailyNotifications" + ADD CONSTRAINT "FK_519b07c613d308d7c5f46b35cd3" FOREIGN KEY ("notificationId") REFERENCES push."Notifications"(id); + + +-- +-- Name: channels_groups__groups FK_63d0692973bdb93d0e57ee08e30; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.channels_groups__groups + ADD CONSTRAINT "FK_63d0692973bdb93d0e57ee08e30" FOREIGN KEY ("groupsId") REFERENCES push."Groups"(id) ON DELETE CASCADE; + + +-- +-- Name: channels_members__users FK_6cd3b13bb09aaf62d70ada4fed5; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.channels_members__users + ADD CONSTRAINT "FK_6cd3b13bb09aaf62d70ada4fed5" FOREIGN KEY ("usersId") REFERENCES push."Users"(id) ON DELETE CASCADE; + + +-- +-- Name: UserNotifications FK_779122ce4df611e1a5ea323a5e8; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."UserNotifications" + ADD CONSTRAINT "FK_779122ce4df611e1a5ea323a5e8" FOREIGN KEY ("userId") REFERENCES push."Users"(id); + + +-- +-- Name: channels_unsubscribed__users FK_81c54acb5c0d813a6a9e9c4757d; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.channels_unsubscribed__users + ADD CONSTRAINT "FK_81c54acb5c0d813a6a9e9c4757d" FOREIGN KEY ("usersId") REFERENCES push."Users"(id) ON DELETE CASCADE; + + +-- +-- Name: preferences_disabled_channels__channels FK_8700bf3fe1dd0fdee82af35b812; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.preferences_disabled_channels__channels + ADD CONSTRAINT "FK_8700bf3fe1dd0fdee82af35b812" FOREIGN KEY ("preferencesId") REFERENCES push."Preferences"(id) ON DELETE CASCADE; + + +-- +-- Name: UserDailyNotifications FK_8b87e1326fefe10b83615464615; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."UserDailyNotifications" + ADD CONSTRAINT "FK_8b87e1326fefe10b83615464615" FOREIGN KEY ("userId") REFERENCES push."Users"(id); + + +-- +-- Name: channels_groups__groups FK_8f468c04ac534b8a2014e6cd938; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.channels_groups__groups + ADD CONSTRAINT "FK_8f468c04ac534b8a2014e6cd938" FOREIGN KEY ("channelsId") REFERENCES push."Channels"(id) ON DELETE CASCADE; + + +-- +-- Name: Channels FK_93c37918cc9b8af94a925ca721f; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Channels" + ADD CONSTRAINT "FK_93c37918cc9b8af94a925ca721f" FOREIGN KEY ("ownerId") REFERENCES push."Users"(id); + + +-- +-- Name: UserNotifications FK_b2195eece7faad3fb348b593c80; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."UserNotifications" + ADD CONSTRAINT "FK_b2195eece7faad3fb348b593c80" FOREIGN KEY ("notificationId") REFERENCES push."Notifications"(id); + + +-- +-- Name: Channels FK_b5b061cf5ce6513c090be018e9b; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Channels" + ADD CONSTRAINT "FK_b5b061cf5ce6513c090be018e9b" FOREIGN KEY ("adminGroupId") REFERENCES push."Groups"(id); + + +-- +-- Name: Preferences FK_d31ccc7fa8b6a463152b463f9cf; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Preferences" + ADD CONSTRAINT "FK_d31ccc7fa8b6a463152b463f9cf" FOREIGN KEY ("targetId") REFERENCES push."Channels"(id); + + +-- +-- Name: Devices FK_dfa213fa54e17955b672a7a286b; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push."Devices" + ADD CONSTRAINT "FK_dfa213fa54e17955b672a7a286b" FOREIGN KEY ("userId") REFERENCES push."Users"(id); + + +-- +-- Name: channels_members__users FK_ff62bcfacefb8206dc10dc194f8; Type: FK CONSTRAINT; Schema: push; Owner: admin +-- + +ALTER TABLE ONLY push.channels_members__users + ADD CONSTRAINT "FK_ff62bcfacefb8206dc10dc194f8" FOREIGN KEY ("channelsId") REFERENCES push."Channels"(id) ON DELETE CASCADE; + + +-- +-- Name: UserNotifications FK_9f854dd9ebb621b8e26a8e3845d; Type: FK CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."UserNotifications" + ADD CONSTRAINT "FK_9f854dd9ebb621b8e26a8e3845d" FOREIGN KEY ("userUsername") REFERENCES push_test."Users"(username); + + +-- +-- Name: UserNotifications FK_d3aa6cd0b95e6894c667dc48c9b; Type: FK CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."UserNotifications" + ADD CONSTRAINT "FK_d3aa6cd0b95e6894c667dc48c9b" FOREIGN KEY ("notificationId") REFERENCES push_test."Notifications"(id); + + +-- +-- Name: Notifications FK_d7e72b4a00d9154f9409d8106d3; Type: FK CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."Notifications" + ADD CONSTRAINT "FK_d7e72b4a00d9154f9409d8106d3" FOREIGN KEY ("fromId") REFERENCES push_test."Services"(id); + + +-- +-- Name: Rules FK_dbcef7a35582a45f7550f4010f1; Type: FK CONSTRAINT; Schema: push_test; Owner: admin +-- + +ALTER TABLE ONLY push_test."Rules" + ADD CONSTRAINT "FK_dbcef7a35582a45f7550f4010f1" FOREIGN KEY ("userUsername") REFERENCES push_test."Users"(username); + + +-- +-- Name: users_notifications__notifications FK_6551d57a770d5fc3c3e25659283; Type: FK CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test.users_notifications__notifications + ADD CONSTRAINT "FK_6551d57a770d5fc3c3e25659283" FOREIGN KEY ("usersId") REFERENCES test."Users"(id) ON DELETE CASCADE; + + +-- +-- Name: Rules FK_d47ff4913a611d261e61ceaa446; Type: FK CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test."Rules" + ADD CONSTRAINT "FK_d47ff4913a611d261e61ceaa446" FOREIGN KEY ("userId") REFERENCES test."Users"(id); + + +-- +-- Name: users_notifications__notifications FK_e58f2e1cf4a7e654daab1046d48; Type: FK CONSTRAINT; Schema: test; Owner: admin +-- + +ALTER TABLE ONLY test.users_notifications__notifications + ADD CONSTRAINT "FK_e58f2e1cf4a7e654daab1046d48" FOREIGN KEY ("notificationsId") REFERENCES test."Notifications"(id) ON DELETE CASCADE; + + +-- +-- PostgreSQL database dump complete +-- diff --git a/scripts/push_dev.sql b/scripts/push_dev.sql deleted file mode 100644 index 3d316035c1eb8edfaaf7ea2283df0069381f8dc7..0000000000000000000000000000000000000000 --- a/scripts/push_dev.sql +++ /dev/null @@ -1,2593 +0,0 @@ --- --- PostgreSQL database dump --- - --- Dumped from database version 9.6.16 --- Dumped by pg_dump version 13.0 - --- Started on 2020-12-09 11:36:17 CET - -SET statement_timeout = 0; -SET lock_timeout = 0; -SET idle_in_transaction_session_timeout = 0; -SET client_encoding = 'UTF8'; -SET standard_conforming_strings = on; -SELECT pg_catalog.set_config('search_path', '', false); -SET check_function_bodies = false; -SET xmloption = content; -SET client_min_messages = warning; -SET row_security = off; - --- --- TOC entry 6 (class 2615 OID 258055) --- Name: authorization_service; Type: SCHEMA; Schema: -; Owner: test --- - -CREATE SCHEMA authorization_service; - - -ALTER SCHEMA authorization_service OWNER TO test; - --- --- TOC entry 9 (class 2615 OID 259203) --- Name: push; Type: SCHEMA; Schema: -; Owner: test --- - -CREATE SCHEMA push; - - -ALTER SCHEMA push OWNER TO test; - --- --- TOC entry 10 (class 2615 OID 258555) --- Name: push_test; Type: SCHEMA; Schema: -; Owner: test --- - -CREATE SCHEMA push_test; - - -ALTER SCHEMA push_test OWNER TO test; - --- --- TOC entry 5 (class 2615 OID 257867) --- Name: test; Type: SCHEMA; Schema: -; Owner: test --- - -CREATE SCHEMA test; - - -ALTER SCHEMA test OWNER TO test; - -SET default_tablespace = ''; - --- --- TOC entry 211 (class 1259 OID 258103) --- Name: Notifications; Type: TABLE; Schema: authorization_service; Owner: test --- - -CREATE TABLE authorization_service."Notifications" ( - id integer NOT NULL, - target character varying NOT NULL, - subject character varying NOT NULL, - body character varying NOT NULL, - sent boolean DEFAULT false NOT NULL, - "sendAt" timestamp without time zone, - "sentAt" timestamp without time zone, - "fromId" integer -); - - -ALTER TABLE authorization_service."Notifications" OWNER TO test; - --- --- TOC entry 210 (class 1259 OID 258101) --- Name: Notifications_id_seq; Type: SEQUENCE; Schema: authorization_service; Owner: test --- - -CREATE SEQUENCE authorization_service."Notifications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE authorization_service."Notifications_id_seq" OWNER TO test; - --- --- TOC entry 3367 (class 0 OID 0) --- Dependencies: 210 --- Name: Notifications_id_seq; Type: SEQUENCE OWNED BY; Schema: authorization_service; Owner: test --- - -ALTER SEQUENCE authorization_service."Notifications_id_seq" OWNED BY authorization_service."Notifications".id; - - --- --- TOC entry 206 (class 1259 OID 258073) --- Name: Rules; Type: TABLE; Schema: authorization_service; Owner: test --- - -CREATE TABLE authorization_service."Rules" ( - id integer NOT NULL, - name character varying NOT NULL, - channel character varying NOT NULL, - string character varying, - type character varying NOT NULL, - "userId" integer -); - - -ALTER TABLE authorization_service."Rules" OWNER TO test; - --- --- TOC entry 205 (class 1259 OID 258071) --- Name: Rules_id_seq; Type: SEQUENCE; Schema: authorization_service; Owner: test --- - -CREATE SEQUENCE authorization_service."Rules_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE authorization_service."Rules_id_seq" OWNER TO test; - --- --- TOC entry 3368 (class 0 OID 0) --- Dependencies: 205 --- Name: Rules_id_seq; Type: SEQUENCE OWNED BY; Schema: authorization_service; Owner: test --- - -ALTER SEQUENCE authorization_service."Rules_id_seq" OWNED BY authorization_service."Rules".id; - - --- --- TOC entry 204 (class 1259 OID 258058) --- Name: Services; Type: TABLE; Schema: authorization_service; Owner: test --- - -CREATE TABLE authorization_service."Services" ( - id integer NOT NULL, - name character varying NOT NULL, - "apiKey" character varying -); - - -ALTER TABLE authorization_service."Services" OWNER TO test; - --- --- TOC entry 203 (class 1259 OID 258056) --- Name: Services_id_seq; Type: SEQUENCE; Schema: authorization_service; Owner: test --- - -CREATE SEQUENCE authorization_service."Services_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE authorization_service."Services_id_seq" OWNER TO test; - --- --- TOC entry 3369 (class 0 OID 0) --- Dependencies: 203 --- Name: Services_id_seq; Type: SEQUENCE OWNED BY; Schema: authorization_service; Owner: test --- - -ALTER SEQUENCE authorization_service."Services_id_seq" OWNED BY authorization_service."Services".id; - - --- --- TOC entry 209 (class 1259 OID 258094) --- Name: UserNotifications; Type: TABLE; Schema: authorization_service; Owner: test --- - -CREATE TABLE authorization_service."UserNotifications" ( - id integer NOT NULL, - read boolean NOT NULL, - archived boolean NOT NULL, - "userId" integer, - "notificationId" integer -); - - -ALTER TABLE authorization_service."UserNotifications" OWNER TO test; - --- --- TOC entry 208 (class 1259 OID 258092) --- Name: UserNotifications_id_seq; Type: SEQUENCE; Schema: authorization_service; Owner: test --- - -CREATE SEQUENCE authorization_service."UserNotifications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE authorization_service."UserNotifications_id_seq" OWNER TO test; - --- --- TOC entry 3370 (class 0 OID 0) --- Dependencies: 208 --- Name: UserNotifications_id_seq; Type: SEQUENCE OWNED BY; Schema: authorization_service; Owner: test --- - -ALTER SEQUENCE authorization_service."UserNotifications_id_seq" OWNED BY authorization_service."UserNotifications".id; - - --- --- TOC entry 207 (class 1259 OID 258084) --- Name: Users; Type: TABLE; Schema: authorization_service; Owner: test --- - -CREATE TABLE authorization_service."Users" ( - id integer NOT NULL, - username character varying(50) NOT NULL, - email character varying NOT NULL, - enabled boolean NOT NULL -); - - -ALTER TABLE authorization_service."Users" OWNER TO test; - --- --- TOC entry 192 (class 1259 OID 257759) --- Name: Notfications; Type: TABLE; Schema: public; Owner: test --- - -CREATE TABLE public."Notfications" ( - id integer NOT NULL, - target character varying NOT NULL, - subject character varying NOT NULL, - body character varying NOT NULL, - sent boolean DEFAULT false NOT NULL, - "sendAt" timestamp without time zone, - "sentAt" timestamp without time zone -); - - -ALTER TABLE public."Notfications" OWNER TO test; - --- --- TOC entry 191 (class 1259 OID 257757) --- Name: Notfications_id_seq; Type: SEQUENCE; Schema: public; Owner: test --- - -CREATE SEQUENCE public."Notfications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE public."Notfications_id_seq" OWNER TO test; - --- --- TOC entry 3371 (class 0 OID 0) --- Dependencies: 191 --- Name: Notfications_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: test --- - -ALTER SEQUENCE public."Notfications_id_seq" OWNED BY public."Notfications".id; - - --- --- TOC entry 194 (class 1259 OID 257777) --- Name: Notifications; Type: TABLE; Schema: public; Owner: test --- - -CREATE TABLE public."Notifications" ( - id integer NOT NULL, - target character varying NOT NULL, - subject character varying NOT NULL, - body character varying NOT NULL, - sent boolean DEFAULT false NOT NULL, - "sendAt" timestamp without time zone, - "sentAt" timestamp without time zone -); - - -ALTER TABLE public."Notifications" OWNER TO test; - --- --- TOC entry 193 (class 1259 OID 257775) --- Name: Notifications_id_seq; Type: SEQUENCE; Schema: public; Owner: test --- - -CREATE SEQUENCE public."Notifications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE public."Notifications_id_seq" OWNER TO test; - --- --- TOC entry 3372 (class 0 OID 0) --- Dependencies: 193 --- Name: Notifications_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: test --- - -ALTER SEQUENCE public."Notifications_id_seq" OWNED BY public."Notifications".id; - - --- --- TOC entry 190 (class 1259 OID 257751) --- Name: Users; Type: TABLE; Schema: public; Owner: test --- - -CREATE TABLE public."Users" ( - id integer NOT NULL, - username character varying(50) NOT NULL, - enabled boolean NOT NULL -); - - -ALTER TABLE public."Users" OWNER TO test; - --- --- TOC entry 189 (class 1259 OID 257749) --- Name: Users_id_seq; Type: SEQUENCE; Schema: public; Owner: test --- - -CREATE SEQUENCE public."Users_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE public."Users_id_seq" OWNER TO test; - --- --- TOC entry 3373 (class 0 OID 0) --- Dependencies: 189 --- Name: Users_id_seq; Type: SEQUENCE OWNED BY; Schema: public; Owner: test --- - -ALTER SEQUENCE public."Users_id_seq" OWNED BY public."Users".id; - - --- --- TOC entry 226 (class 1259 OID 259875) --- Name: Channels; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push."Channels" ( - "primaryKey" integer NOT NULL, - id character varying NOT NULL, - name character varying NOT NULL, - description character varying NOT NULL, - visibility character varying DEFAULT 'RESTRICTED'::character varying NOT NULL, - "subscriptionPolicy" character varying DEFAULT 'SELF_SUBSCRIPTION'::character varying NOT NULL, - "creationDate" timestamp without time zone DEFAULT now() NOT NULL, - "lastActivityDate" timestamp without time zone DEFAULT now() NOT NULL, - "deleteDate" timestamp without time zone, - "ownerUsername" character varying(50), - "testGroupId" character varying, - "APIKey" character varying, - "incomingEmail" character varying -); - - -ALTER TABLE push."Channels" OWNER TO test; - --- --- TOC entry 225 (class 1259 OID 259873) --- Name: Channels_primaryKey_seq; Type: SEQUENCE; Schema: push; Owner: test --- - -CREATE SEQUENCE push."Channels_primaryKey_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE push."Channels_primaryKey_seq" OWNER TO test; - --- --- TOC entry 3374 (class 0 OID 0) --- Dependencies: 225 --- Name: Channels_primaryKey_seq; Type: SEQUENCE OWNED BY; Schema: push; Owner: test --- - -ALTER SEQUENCE push."Channels_primaryKey_seq" OWNED BY push."Channels"."primaryKey"; - - --- --- TOC entry 235 (class 1259 OID 260012) --- Name: DailyNotifications; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push."DailyNotifications" ( - id integer NOT NULL, - body character varying NOT NULL, - read boolean NOT NULL, - pinned boolean DEFAULT false NOT NULL, - archived boolean NOT NULL, - "userUsername" character varying(50), - "targetPrimaryKey" integer -); - - -ALTER TABLE push."DailyNotifications" OWNER TO test; - --- --- TOC entry 234 (class 1259 OID 260010) --- Name: DailyNotifications_id_seq; Type: SEQUENCE; Schema: push; Owner: test --- - -CREATE SEQUENCE push."DailyNotifications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE push."DailyNotifications_id_seq" OWNER TO test; - --- --- TOC entry 3375 (class 0 OID 0) --- Dependencies: 234 --- Name: DailyNotifications_id_seq; Type: SEQUENCE OWNED BY; Schema: push; Owner: test --- - -ALTER SEQUENCE push."DailyNotifications_id_seq" OWNED BY push."DailyNotifications".id; - - --- --- TOC entry 224 (class 1259 OID 259863) --- Name: Groups; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push."Groups" ( - id character varying NOT NULL, - "groupIdentifier" character varying NOT NULL -); - - -ALTER TABLE push."Groups" OWNER TO test; - --- --- TOC entry 223 (class 1259 OID 259853) --- Name: Notifications; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push."Notifications" ( - id integer NOT NULL, - body character varying NOT NULL, - "sendAt" timestamp without time zone, - "sentAt" timestamp without time zone, - tags text, - link character varying, - summary character varying, - "contentType" character varying, - "imgUrl" character varying, - priority character varying DEFAULT 'NORMAL'::character varying NOT NULL, - "targetPrimaryKey" integer -); - - -ALTER TABLE push."Notifications" OWNER TO test; - --- --- TOC entry 222 (class 1259 OID 259851) --- Name: Notifications_id_seq; Type: SEQUENCE; Schema: push; Owner: test --- - -CREATE SEQUENCE push."Notifications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE push."Notifications_id_seq" OWNER TO test; - --- --- TOC entry 3376 (class 0 OID 0) --- Dependencies: 222 --- Name: Notifications_id_seq; Type: SEQUENCE OWNED BY; Schema: push; Owner: test --- - -ALTER SEQUENCE push."Notifications_id_seq" OWNED BY push."Notifications".id; - - --- --- TOC entry 228 (class 1259 OID 259892) --- Name: Preferences; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push."Preferences" ( - id integer NOT NULL, - type character varying NOT NULL, - "userUsername" character varying(50), - "targetPrimaryKey" integer, - name character varying, - "notificationPriority" text, - "rangeStart" time without time zone, - "rangeEnd" time without time zone -); - - -ALTER TABLE push."Preferences" OWNER TO test; - --- --- TOC entry 227 (class 1259 OID 259890) --- Name: Preferences_id_seq; Type: SEQUENCE; Schema: push; Owner: test --- - -CREATE SEQUENCE push."Preferences_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE push."Preferences_id_seq" OWNER TO test; - --- --- TOC entry 3377 (class 0 OID 0) --- Dependencies: 227 --- Name: Preferences_id_seq; Type: SEQUENCE OWNED BY; Schema: push; Owner: test --- - -ALTER SEQUENCE push."Preferences_id_seq" OWNED BY push."Preferences".id; - - --- --- TOC entry 230 (class 1259 OID 259910) --- Name: Services; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push."Services" ( - id character varying NOT NULL, - name character varying NOT NULL, - email character varying -); - - -ALTER TABLE push."Services" OWNER TO test; - --- --- TOC entry 221 (class 1259 OID 259843) --- Name: UserNotifications; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push."UserNotifications" ( - id integer NOT NULL, - sent boolean NOT NULL, - read boolean NOT NULL, - pinned boolean DEFAULT false NOT NULL, - archived boolean NOT NULL, - "userUsername" character varying(50), - "notificationId" integer -); - - -ALTER TABLE push."UserNotifications" OWNER TO test; - --- --- TOC entry 220 (class 1259 OID 259841) --- Name: UserNotifications_id_seq; Type: SEQUENCE; Schema: push; Owner: test --- - -CREATE SEQUENCE push."UserNotifications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE push."UserNotifications_id_seq" OWNER TO test; - --- --- TOC entry 3378 (class 0 OID 0) --- Dependencies: 220 --- Name: UserNotifications_id_seq; Type: SEQUENCE OWNED BY; Schema: push; Owner: test --- - -ALTER SEQUENCE push."UserNotifications_id_seq" OWNED BY push."UserNotifications".id; - - --- --- TOC entry 229 (class 1259 OID 259902) --- Name: Users; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push."Users" ( - username character varying(50) NOT NULL, - email character varying NOT NULL, - enabled boolean NOT NULL -); - - -ALTER TABLE push."Users" OWNER TO test; - --- --- TOC entry 233 (class 1259 OID 259934) --- Name: channels_groups__groups; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push.channels_groups__groups ( - "channelsPrimaryKey" integer NOT NULL, - "groupsId" character varying NOT NULL -); - - -ALTER TABLE push.channels_groups__groups OWNER TO test; - --- --- TOC entry 231 (class 1259 OID 259920) --- Name: channels_members__users; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push.channels_members__users ( - "channelsPrimaryKey" integer NOT NULL, - "usersUsername" character varying(50) NOT NULL -); - - -ALTER TABLE push.channels_members__users OWNER TO test; - --- --- TOC entry 232 (class 1259 OID 259927) --- Name: channels_unsubscribed__users; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push.channels_unsubscribed__users ( - "channelsPrimaryKey" integer NOT NULL, - "usersUsername" character varying(50) NOT NULL -); - - -ALTER TABLE push.channels_unsubscribed__users OWNER TO test; - --- --- TOC entry 236 (class 1259 OID 260093) --- Name: preferences_disabled_channels__channels; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push.preferences_disabled_channels__channels ( - "preferencesId" integer NOT NULL, - "channelsPrimaryKey" integer NOT NULL -); - - -ALTER TABLE push.preferences_disabled_channels__channels OWNER TO test; - --- --- TOC entry 217 (class 1259 OID 258948) --- Name: Notifications; Type: TABLE; Schema: push_test; Owner: test --- - -CREATE TABLE push_test."Notifications" ( - id integer NOT NULL, - target character varying NOT NULL, - subject character varying NOT NULL, - body character varying NOT NULL, - sent boolean DEFAULT false NOT NULL, - "sendAt" timestamp without time zone, - "sentAt" timestamp without time zone, - "fromId" character varying, - tags text, - link character varying, - summary character varying, - "contentType" character varying, - "imgUrl" character varying, - priority character varying DEFAULT 'NORMAL'::character varying NOT NULL -); - - -ALTER TABLE push_test."Notifications" OWNER TO test; - --- --- TOC entry 216 (class 1259 OID 258946) --- Name: Notifications_id_seq; Type: SEQUENCE; Schema: push_test; Owner: test --- - -CREATE SEQUENCE push_test."Notifications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE push_test."Notifications_id_seq" OWNER TO test; - --- --- TOC entry 3379 (class 0 OID 0) --- Dependencies: 216 --- Name: Notifications_id_seq; Type: SEQUENCE OWNED BY; Schema: push_test; Owner: test --- - -ALTER SEQUENCE push_test."Notifications_id_seq" OWNED BY push_test."Notifications".id; - - --- --- TOC entry 219 (class 1259 OID 258989) --- Name: Rules; Type: TABLE; Schema: push_test; Owner: test --- - -CREATE TABLE push_test."Rules" ( - id integer NOT NULL, - name character varying NOT NULL, - channels text DEFAULT 'PUSH'::text NOT NULL, - type character varying NOT NULL, - string character varying, - "userUsername" character varying(50) -); - - -ALTER TABLE push_test."Rules" OWNER TO test; - --- --- TOC entry 218 (class 1259 OID 258987) --- Name: Rules_id_seq; Type: SEQUENCE; Schema: push_test; Owner: test --- - -CREATE SEQUENCE push_test."Rules_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE push_test."Rules_id_seq" OWNER TO test; - --- --- TOC entry 3380 (class 0 OID 0) --- Dependencies: 218 --- Name: Rules_id_seq; Type: SEQUENCE OWNED BY; Schema: push_test; Owner: test --- - -ALTER SEQUENCE push_test."Rules_id_seq" OWNED BY push_test."Rules".id; - - --- --- TOC entry 213 (class 1259 OID 258811) --- Name: Services; Type: TABLE; Schema: push_test; Owner: test --- - -CREATE TABLE push_test."Services" ( - id character varying NOT NULL, - name character varying NOT NULL, - email character varying -); - - -ALTER TABLE push_test."Services" OWNER TO test; - --- --- TOC entry 215 (class 1259 OID 258938) --- Name: UserNotifications; Type: TABLE; Schema: push_test; Owner: test --- - -CREATE TABLE push_test."UserNotifications" ( - id integer NOT NULL, - read boolean NOT NULL, - pinned boolean DEFAULT false NOT NULL, - archived boolean NOT NULL, - "userUsername" character varying(50), - "notificationId" integer -); - - -ALTER TABLE push_test."UserNotifications" OWNER TO test; - --- --- TOC entry 214 (class 1259 OID 258936) --- Name: UserNotifications_id_seq; Type: SEQUENCE; Schema: push_test; Owner: test --- - -CREATE SEQUENCE push_test."UserNotifications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE push_test."UserNotifications_id_seq" OWNER TO test; - --- --- TOC entry 3381 (class 0 OID 0) --- Dependencies: 214 --- Name: UserNotifications_id_seq; Type: SEQUENCE OWNED BY; Schema: push_test; Owner: test --- - -ALTER SEQUENCE push_test."UserNotifications_id_seq" OWNED BY push_test."UserNotifications".id; - - --- --- TOC entry 212 (class 1259 OID 258584) --- Name: Users; Type: TABLE; Schema: push_test; Owner: test --- - -CREATE TABLE push_test."Users" ( - username character varying(50) NOT NULL, - email character varying NOT NULL, - enabled boolean NOT NULL -); - - -ALTER TABLE push_test."Users" OWNER TO test; - --- --- TOC entry 199 (class 1259 OID 257891) --- Name: Notifications; Type: TABLE; Schema: test; Owner: test --- - -CREATE TABLE test."Notifications" ( - id integer NOT NULL, - target character varying NOT NULL, - subject character varying NOT NULL, - body character varying NOT NULL, - sent boolean DEFAULT false NOT NULL, - "sendAt" timestamp without time zone, - "sentAt" timestamp without time zone, - "from" character varying NOT NULL -); - - -ALTER TABLE test."Notifications" OWNER TO test; - --- --- TOC entry 198 (class 1259 OID 257889) --- Name: Notifications_id_seq; Type: SEQUENCE; Schema: test; Owner: test --- - -CREATE SEQUENCE test."Notifications_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE test."Notifications_id_seq" OWNER TO test; - --- --- TOC entry 3382 (class 0 OID 0) --- Dependencies: 198 --- Name: Notifications_id_seq; Type: SEQUENCE OWNED BY; Schema: test; Owner: test --- - -ALTER SEQUENCE test."Notifications_id_seq" OWNED BY test."Notifications".id; - - --- --- TOC entry 196 (class 1259 OID 257870) --- Name: Rules; Type: TABLE; Schema: test; Owner: test --- - -CREATE TABLE test."Rules" ( - id integer NOT NULL, - channel character varying NOT NULL, - type character varying NOT NULL, - "userId" integer, - string character varying -); - - -ALTER TABLE test."Rules" OWNER TO test; - --- --- TOC entry 195 (class 1259 OID 257868) --- Name: Rules_id_seq; Type: SEQUENCE; Schema: test; Owner: test --- - -CREATE SEQUENCE test."Rules_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE test."Rules_id_seq" OWNER TO test; - --- --- TOC entry 3383 (class 0 OID 0) --- Dependencies: 195 --- Name: Rules_id_seq; Type: SEQUENCE OWNED BY; Schema: test; Owner: test --- - -ALTER SEQUENCE test."Rules_id_seq" OWNED BY test."Rules".id; - - --- --- TOC entry 201 (class 1259 OID 257903) --- Name: Services; Type: TABLE; Schema: test; Owner: test --- - -CREATE TABLE test."Services" ( - id integer NOT NULL, - name character varying NOT NULL, - "apiKey" character varying -); - - -ALTER TABLE test."Services" OWNER TO test; - --- --- TOC entry 200 (class 1259 OID 257901) --- Name: Services_id_seq; Type: SEQUENCE; Schema: test; Owner: test --- - -CREATE SEQUENCE test."Services_id_seq" - START WITH 1 - INCREMENT BY 1 - NO MINVALUE - NO MAXVALUE - CACHE 1; - - -ALTER TABLE test."Services_id_seq" OWNER TO test; - --- --- TOC entry 3384 (class 0 OID 0) --- Dependencies: 200 --- Name: Services_id_seq; Type: SEQUENCE OWNED BY; Schema: test; Owner: test --- - -ALTER SEQUENCE test."Services_id_seq" OWNED BY test."Services".id; - - --- --- TOC entry 197 (class 1259 OID 257881) --- Name: Users; Type: TABLE; Schema: test; Owner: test --- - -CREATE TABLE test."Users" ( - id integer NOT NULL, - username character varying(50) NOT NULL, - email character varying NOT NULL -); - - -ALTER TABLE test."Users" OWNER TO test; - --- --- TOC entry 202 (class 1259 OID 257916) --- Name: users_notifications__notifications; Type: TABLE; Schema: test; Owner: test --- - -CREATE TABLE test.users_notifications__notifications ( - "usersId" integer NOT NULL, - "notificationsId" integer NOT NULL -); - - -ALTER TABLE test.users_notifications__notifications OWNER TO test; - --- --- TOC entry 3055 (class 2604 OID 258106) --- Name: Notifications id; Type: DEFAULT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Notifications" ALTER COLUMN id SET DEFAULT nextval('authorization_service."Notifications_id_seq"'::regclass); - - --- --- TOC entry 3053 (class 2604 OID 258076) --- Name: Rules id; Type: DEFAULT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Rules" ALTER COLUMN id SET DEFAULT nextval('authorization_service."Rules_id_seq"'::regclass); - - --- --- TOC entry 3052 (class 2604 OID 258061) --- Name: Services id; Type: DEFAULT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Services" ALTER COLUMN id SET DEFAULT nextval('authorization_service."Services_id_seq"'::regclass); - - --- --- TOC entry 3054 (class 2604 OID 258097) --- Name: UserNotifications id; Type: DEFAULT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."UserNotifications" ALTER COLUMN id SET DEFAULT nextval('authorization_service."UserNotifications_id_seq"'::regclass); - - --- --- TOC entry 3044 (class 2604 OID 257762) --- Name: Notfications id; Type: DEFAULT; Schema: public; Owner: test --- - -ALTER TABLE ONLY public."Notfications" ALTER COLUMN id SET DEFAULT nextval('public."Notfications_id_seq"'::regclass); - - --- --- TOC entry 3046 (class 2604 OID 257780) --- Name: Notifications id; Type: DEFAULT; Schema: public; Owner: test --- - -ALTER TABLE ONLY public."Notifications" ALTER COLUMN id SET DEFAULT nextval('public."Notifications_id_seq"'::regclass); - - --- --- TOC entry 3043 (class 2604 OID 257754) --- Name: Users id; Type: DEFAULT; Schema: public; Owner: test --- - -ALTER TABLE ONLY public."Users" ALTER COLUMN id SET DEFAULT nextval('public."Users_id_seq"'::regclass); - - --- --- TOC entry 3068 (class 2604 OID 259878) --- Name: Channels primaryKey; Type: DEFAULT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Channels" ALTER COLUMN "primaryKey" SET DEFAULT nextval('push."Channels_primaryKey_seq"'::regclass); - - --- --- TOC entry 3074 (class 2604 OID 260015) --- Name: DailyNotifications id; Type: DEFAULT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."DailyNotifications" ALTER COLUMN id SET DEFAULT nextval('push."DailyNotifications_id_seq"'::regclass); - - --- --- TOC entry 3066 (class 2604 OID 259856) --- Name: Notifications id; Type: DEFAULT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Notifications" ALTER COLUMN id SET DEFAULT nextval('push."Notifications_id_seq"'::regclass); - - --- --- TOC entry 3073 (class 2604 OID 259895) --- Name: Preferences id; Type: DEFAULT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Preferences" ALTER COLUMN id SET DEFAULT nextval('push."Preferences_id_seq"'::regclass); - - --- --- TOC entry 3064 (class 2604 OID 259846) --- Name: UserNotifications id; Type: DEFAULT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."UserNotifications" ALTER COLUMN id SET DEFAULT nextval('push."UserNotifications_id_seq"'::regclass); - - --- --- TOC entry 3060 (class 2604 OID 258951) --- Name: Notifications id; Type: DEFAULT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."Notifications" ALTER COLUMN id SET DEFAULT nextval('push_test."Notifications_id_seq"'::regclass); - - --- --- TOC entry 3062 (class 2604 OID 258992) --- Name: Rules id; Type: DEFAULT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."Rules" ALTER COLUMN id SET DEFAULT nextval('push_test."Rules_id_seq"'::regclass); - - --- --- TOC entry 3057 (class 2604 OID 258941) --- Name: UserNotifications id; Type: DEFAULT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."UserNotifications" ALTER COLUMN id SET DEFAULT nextval('push_test."UserNotifications_id_seq"'::regclass); - - --- --- TOC entry 3049 (class 2604 OID 257894) --- Name: Notifications id; Type: DEFAULT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Notifications" ALTER COLUMN id SET DEFAULT nextval('test."Notifications_id_seq"'::regclass); - - --- --- TOC entry 3048 (class 2604 OID 257873) --- Name: Rules id; Type: DEFAULT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Rules" ALTER COLUMN id SET DEFAULT nextval('test."Rules_id_seq"'::regclass); - - --- --- TOC entry 3051 (class 2604 OID 257906) --- Name: Services id; Type: DEFAULT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Services" ALTER COLUMN id SET DEFAULT nextval('test."Services_id_seq"'::regclass); - - --- --- TOC entry 3336 (class 0 OID 258103) --- Dependencies: 211 --- Data for Name: Notifications; Type: TABLE DATA; Schema: authorization_service; Owner: test --- - -COPY authorization_service."Notifications" (id, target, subject, body, sent, "sendAt", "sentAt", "fromId") FROM stdin; -\. - - --- --- TOC entry 3331 (class 0 OID 258073) --- Dependencies: 206 --- Data for Name: Rules; Type: TABLE DATA; Schema: authorization_service; Owner: test --- - -COPY authorization_service."Rules" (id, name, channel, string, type, "userId") FROM stdin; -\. - - --- --- TOC entry 3329 (class 0 OID 258058) --- Dependencies: 204 --- Data for Name: Services; Type: TABLE DATA; Schema: authorization_service; Owner: test --- - -COPY authorization_service."Services" (id, name, "apiKey") FROM stdin; -2 authorization-service e9ac78c1a8e1d67360036bd4cefef6ffd7a849c2dd97bbf98ef08817b80cf398 -\. - - --- --- TOC entry 3334 (class 0 OID 258094) --- Dependencies: 209 --- Data for Name: UserNotifications; Type: TABLE DATA; Schema: authorization_service; Owner: test --- - -COPY authorization_service."UserNotifications" (id, read, archived, "userId", "notificationId") FROM stdin; -\. - - --- --- TOC entry 3332 (class 0 OID 258084) --- Dependencies: 207 --- Data for Name: Users; Type: TABLE DATA; Schema: authorization_service; Owner: test --- - -COPY authorization_service."Users" (id, username, email, enabled) FROM stdin; -\. - - --- --- TOC entry 3317 (class 0 OID 257759) --- Dependencies: 192 --- Data for Name: Notfications; Type: TABLE DATA; Schema: public; Owner: test --- - -COPY public."Notfications" (id, target, subject, body, sent, "sendAt", "sentAt") FROM stdin; -1 Me Test Send push notification test f 2018-08-17 00:00:00 \N -2 Me Test Send push notification test f 2018-08-17 00:00:00 \N -3 Me Test Send push notification test f 2018-08-17 00:00:00 \N -4 Me Test Send push notification test f 2018-08-17 00:00:00 \N -5 Me Test Send push notification test f 2018-08-17 00:00:00 \N -6 Me Test Send push notification test f 2018-08-17 00:00:00 \N -7 Me Test Send push notification test f 2018-08-17 00:00:00 \N -8 Me Test Send push notification test f 2018-08-17 00:00:00 \N -9 Me Test Send push notification test f 2018-08-17 00:00:00 \N -10 Test 19 July 2018 Test 19 July 2018 Test 19 July 2018 f 2018-08-17 00:00:00 \N -11 Test 20 July 2018 Test 20 July 2018 Test 20 July 2018 f 2018-08-17 00:00:00 \N -17 target Test This is a test notifications f \N \N -19 all Test This is a test notifications f \N \N -20 all test This is a test notification f \N \N -21 Test 20 July 2018 David [2] Test 20 July 2018 David [2] Test 20 July 2018 David [2] f 2018-08-17 00:00:00 \N -22 Test 20 July 2018 David [3] Test 20 July 2018 David [3] Test 20 July 2018 David [3] f 2018-08-17 00:00:00 \N -23 david.martin.clavo@cern.ch Test 20 July 2018 David [4] Test 20 July 2018 David [4] f 2018-08-17 00:00:00 \N -24 Mario Test This is a test notification f \N \N -28 all test eeey testing material ui f \N \N -29 all test eeey testing material ui f \N \N -30 all test eeey testing material ui f \N \N -31 all test eeey testing material ui f \N \N -32 all test eeey testing material ui f \N \N -36 adsf adsf adsf f \N \N -\. - - --- --- TOC entry 3319 (class 0 OID 257777) --- Dependencies: 194 --- Data for Name: Notifications; Type: TABLE DATA; Schema: public; Owner: test --- - -COPY public."Notifications" (id, target, subject, body, sent, "sendAt", "sentAt") FROM stdin; -1 Panero Test This is a test notification f \N \N -2 Mario Test This is a test notification f \N \N -4 pablo.roncer.fernandez@cern.ch Test This is a test notification f \N \N -\. - - --- --- TOC entry 3315 (class 0 OID 257751) --- Dependencies: 190 --- Data for Name: Users; Type: TABLE DATA; Schema: public; Owner: test --- - -COPY public."Users" (id, username, enabled) FROM stdin; -\. - - --- --- TOC entry 3351 (class 0 OID 259875) --- Dependencies: 226 --- Data for Name: Channels; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push."Channels" ("primaryKey", id, name, description, visibility, "subscriptionPolicy", "creationDate", "lastActivityDate", "deleteDate", "ownerUsername", "testGroupId", "APIKey", "incomingEmail") FROM stdin; -2 it-cda-wf IT CDA Web Frameworks Notification channel for Web Frameworks section RESTRICTED DYNAMIC 2020-06-30 11:55:30.158239 2020-06-30 10:05:10.991 \N eduardoa 08d7dbce-549f-45f4-8444-ffccb0163367 \N \N -5 drupal-alarms Drupal Service Alarms Drupal service alarms notification system RESTRICTED DYNAMIC 2020-06-30 16:20:37.927472 2020-06-30 16:20:37.927472 \N eduardoa 08d779a9-85f8-5d52-af48-8b02a8b84c24 \N \N -6 cern-entraces CERN Entrances Notification channel for the CERN Entrances, A-B-C-D-E.\nIssues with entrances will be posted here. INTERNAL SELF_SUBSCRIPTION 2020-06-30 16:22:44.411337 2020-06-30 16:22:44.411337 \N eduardoa 08d779a9-85f8-5d52-af48-8b02a8b84c24 \N \N -9 roncero-test Roncero test channel Channel for testing RESTRICTED DYNAMIC 2020-09-07 14:33:03.634664 2020-09-07 14:33:03.634664 \N proncero 08d7b3c6-cecf-4cea-8cbb-a153cb017900 \N \N -11 test carina test carina test carina RESTRICTED DYNAMIC 2020-11-05 19:47:11.477322 2020-11-05 19:47:11.477322 2020-11-05 20:20:48.292231 crdeoliv 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N \N -10 monit monit monit test carina RESTRICTED DYNAMIC 2020-09-09 10:14:24.935476 2020-09-09 10:14:24.935476 2020-11-13 13:54:09.067564 crdeoliv 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N \N -12 test-carina test carina test RESTRICTED DYNAMIC 2020-11-05 20:19:43.127002 2020-11-05 20:19:43.127002 2020-11-13 13:54:17.375642 crdeoliv 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N \N -20 test-email test test email validation RESTRICTED DYNAMIC 2020-11-30 17:41:30.819376 2020-11-30 17:41:30.819376 2020-11-30 17:56:46.275076 dchatzic 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N test@cern.ch -14 dchatzic-channel test-channel test PUBLIC DYNAMIC 2020-11-26 19:09:51.343799 2020-11-26 19:09:51.343799 2020-11-26 20:14:01.83612 dchatzic 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N mail@cern.ch -13 test test test RESTRICTED DYNAMIC 2020-11-17 13:51:58.448306 2020-11-17 13:51:58.448306 2020-11-26 20:14:56.78527 crdeoliv 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N \N -19 test-dimi test test RESTRICTED DYNAMIC 2020-11-30 17:04:52.938951 2020-11-30 17:04:52.938951 2020-11-30 17:57:03.868754 dchatzic 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N test@cern.ch -3 it-security IT Security IT Security official notification channel PUBLIC SELF_SUBSCRIPTION 2020-06-30 16:18:11.265963 2020-06-30 16:18:11.265963 \N eduardoa 08d779a9-85f8-5d52-af48-8b02a8b84c24 \N \N -4 gitlab-cern Gitlab Service Communication channel for Gitlab service PUBLIC SELF_SUBSCRIPTION 2020-06-30 16:19:26.519146 2020-06-30 16:19:26.519146 \N eduardoa 0c68daed-d01d-4adb-a0ba-023ed5b0225f \N \N -21 test-email-val test test RESTRICTED DYNAMIC 2020-11-30 17:45:35.629433 2020-11-30 17:45:35.629433 2020-11-30 17:57:21.210927 dchatzic 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N test@cern.ch -1 cern-news CERN News Find the latest CERN related news in this channel PUBLIC SELF_SUBSCRIPTION 2020-06-29 16:46:15.326891 2020-06-30 09:46:32.635 \N proncero 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N noreply@cern.ch -15 dchatzic channel dchatzic channel test description RESTRICTED DYNAMIC 2020-11-26 20:18:29.073659 2020-11-26 20:18:29.073659 2020-11-26 21:05:24.824673 dchatzic 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N username@cern.ch -16 test dimi test test RESTRICTED DYNAMIC 2020-11-26 20:57:03.619587 2020-11-26 20:57:03.619587 2020-11-26 21:05:44.639975 dchatzic 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N test3@cern.ch -18 test test test RESTRICTED DYNAMIC 2020-11-27 09:52:47.240682 2020-11-27 09:52:47.240682 2020-11-27 09:53:13.685357 dchatzic 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N test@test.com -17 dchatz test test test RESTRICTED DYNAMIC 2020-11-27 09:50:12.796781 2020-11-27 09:50:12.796781 2020-11-27 09:54:10.253364 dchatzic 186d8dfc-2774-43a8-91b5-a887fcb6ba4a \N test@cern.ch -\. - - --- --- TOC entry 3360 (class 0 OID 260012) --- Dependencies: 235 --- Data for Name: DailyNotifications; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push."DailyNotifications" (id, body, read, pinned, archived, "userUsername", "targetPrimaryKey") FROM stdin; -\. - - --- --- TOC entry 3349 (class 0 OID 259863) --- Dependencies: 224 --- Data for Name: Groups; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push."Groups" (id, "groupIdentifier") FROM stdin; -186d8dfc-2774-43a8-91b5-a887fcb6ba4a it-dep-cda-wf -08d7b3c6-cecf-4cea-8cbb-a153cb017900 test-roncero -08d779a9-85f8-5d52-af48-8b02a8b84c24 drupal-tests -08d779a7-4bf3-5e57-cee5-46cae1512fc0 test-eduardo98 -08d7dbce-549f-45f4-8444-ffccb0163367 it-dep-cda-wf-plus-tests -0c68daed-d01d-4adb-a0ba-023ed5b0225f it-service-vcs -2d6e20e9-c2e9-41b9-82a2-970025708e85 it-dep-cda -\. - - --- --- TOC entry 3348 (class 0 OID 259853) --- Dependencies: 223 --- Data for Name: Notifications; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push."Notifications" (id, body, "sendAt", "sentAt", tags, link, summary, "contentType", "imgUrl", priority, "targetPrimaryKey") FROM stdin; -1 <h1>White Rabbit, a CERN-born technology sets new global standard empowering world innovators</h1>\n\n<p>The Institute of Electrical and Electronics Engineers incorporated the White Rabbit technology into its industry-standard, thus maximising its adoption by industry and other partners in their pursuit to build innovative solutions for world challenges</p>\n\n<p>26 JUNE, 2020 </p>\n\n<p>| </p>\n\n<p>By <a href="https://home.cern/authors/marzena-lapka">Marzena Lapka</a></p>\n\n<p><a href="https://cds.cern.ch/images/OPEN-PHO-TECH-2020-002-15"><img alt="White Rabbit photos" src="https://cds.cern.ch/images/OPEN-PHO-TECH-2020-002-15/file?size=large" style="height:200px; width:300px" /></a></p>\n\n<p>Photos of the White Rabbit team and equipment (Image: CERN)</p>\n\n<p>White Rabbit (WR) is a technology developed at CERN to provide sub-nanosecond accuracy and picosecond precision of synchronisation for the LHC accelerator chain. First used in 2012, the technology has since then expanded its applications outside the field of particle physics and is now deployed in numerous scientific infrastructures worldwide. It has shown its innovative potential by being commercialised and introduced into different industries, including telecommunications, financial markets, smart grids, space industry and quantum computing.</p>\n\n<p>CERN developed White Rabbit (WR) as an open-source hardware, with primary adoption by other research infrastructures with similar challenges in highly accurate synchronization of distributed electronic devices. The R&D process and all knowledge gained throughout the development has been made available through CERN's Open Hardware Repository. This gives other organisations and companies the freedom to use and modify existing information. Through proactive engagement of CERN's Knowledge Transfer and Beam Controls groups, a larger group of companies and organisations connected to the development of hardware, software, and gateware for WR switches and nodes. The WR ecosystem quickly grew to include several organisations, developing open hardware for widespread benefit. This collaborative approach brought improvements to the original concept, allowing CERN to also benefit from the new developments.</p>\n\n<p>On 16 June, the WR technology was recognised as a worldwide industry-standard, called Precision Time Protocol (PTP), governed by the IEEE, the world's largest technical professional organisation dedicated to advancing technology for the benefit of humanity. The WR addition to the PTP standard, referred to as High Accuracy, allow to increase PTP's synchronisation performance by a few orders of magnitude, from sub-microseconds to sub-nanoseconds.</p>\n\n<p>“PTP is the first IEEE standard to incorporate a CERN-born technology. This is a major step for White Rabbit. It is already widely used in large scientific facilities and its adoption in industry is gaining momentum. Its incorporation into the PTP standard will allow hardware vendors world-wide to produce WR equipment compliant with the PTP standard and consequently accelerate its dissemination on a larger scale," says Maciej Lipinski, Electronics Engineer at CERN, who led the WR standardisation effort.</p>\n \N 2020-06-29 15:05:36.416 \N \N White Rabbit, a CERN-born technology sets new global standard empowering world innovators \N \N NORMAL 1 -2 <h1>Electricity transmission reaches even higher intensities</h1>\n\n<p>A superconducting electrical transmission line developed for the High-Luminosity LHC has set a new intensity record</p>\n\n<p>24 JUNE, 2020 </p>\n\n<p>| </p>\n\n<p>By <a href="https://home.cern/authors/corinne-pralavorio">Corinne Pralavorio</a></p>\n\n<p><a href="https://cds.cern.ch/images/CERN-HOMEWEB-PHO-2020-070-1"><img alt="Superconducting link prototype for the High-Luminosity LHC in SM18" src="https://cds.cern.ch/images/CERN-HOMEWEB-PHO-2020-070-1/file?size=large" style="height:208px; width:300px" /></a></p>\n\n<p>The innovative electrical transmission line, designed for the HL-LHC, has been undergoing tests since mid-June (Image: CERN)</p>\n\n<p>Intensity is rising at CERN. In the superconducting equipment testing hall, an innovative transmission line has set a new record for the transport of electricity. The link, which is 60 metres long, has transported a total of 54 000 amperes (54 kA, or 27 kA in either direction). “It is the most powerful electrical transmission line built and operated to date!” says Amalia Ballarino, the designer and project leader.</p>\n\n<p>The line has been developed for the <a href="https://home.cern/science/accelerators/high-luminosity-lhc">High-Luminosity LHC (HL-LHC)</a>, the accelerator that will succeed the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider (LHC)</a> and is scheduled to start up at the end of 2027. Links like this one will connect the HL-LHC’s magnets to the power converters that supply them.</p>\n\n<p>Interview with Amalia Ballarino, the superconducting link project leader, during the insertion of the line into its cryostat in February 2020 (Video: CERN)</p>\n\n<p>The secret to the new line’s power can be summarised in one word: <a href="https://home.cern/science/engineering/superconductivity">superconductivity</a>.</p>\n\n<p>The line is composed of cables made of magnesium diboride (MgB2), which is a superconductor and therefore presents no resistance to the flow of the current and can transmit much higher intensities than traditional non-superconducting cables. On this occasion, the line transmitted an intensity 25 times greater than could have been achieved with copper cables of a similar diameter. Magnesium diboride has the added benefit that it can be used at 25 kelvins (-248 °C), a higher temperature than is needed for conventional superconductors. This superconductor is more stable and requires less cryogenic power. The superconducting cables that make up the innovative line are inserted into a flexible cryostat, in which helium gas circulates.</p>\n\n<p>The strands of magnesium diboride of which the cables are made were developed by industry, under CERN’s supervision. The cable manufacturing process was designed at CERN, before industrial production began. As the strands of magnesium diboride are fragile, manufacturing the cables requires considerable expertise. The current is transmitted from the power supply at room temperature to the flexible link by ReBCO high-temperature superconducting (HTS) cables.</p>\n\n<p><a href="https://cds.cern.ch/images/CERN-HOMEWEB-PHO-2020-070-2"><img alt="home.cern,Accelerators" src="https://cds.cern.ch/images/CERN-HOMEWEB-PHO-2020-070-2/file?size=large" style="height:400px; width:300px" /></a></p>\n\n<p>A team member connects the superconducting link cables before the electrical transmission tests begin (Image: CERN)</p>\n \N 2020-06-29 15:09:21.584 \N \N Electricity transmission reaches even higher intensities \N \N NORMAL 1 -3 <h1>Blood donation: an essential act of solidarity</h1>\n\n<p>CERN’s next blood donation session, originally scheduled for 14 and 15 July 2020, will not be able to take place, but other options are available if you wish to give blood</p>\n\n<p>24 JUNE, 2020 </p>\n\n<p>| </p>\n\n<p>By <a href="https://home.cern/authors/medical-service">The Medical Service</a></p>\n\n<p>Every year, CERN hosts several blood donation sessions. Unfortunately, due to the COVID-19 pandemic, the next session, which was scheduled for 14 and 15 July, will not be able to take place.</p>\n\n<p>However, please note that other options are available to blood donors: remember that giving blood save lives!</p>\n\n<p>Before donating blood, you must make sure:</p>\n\n<ul>\n\t<li>that you are in good health and have no COVID-19 symptoms (fever, cough, cold, breathing difficulties);</li>\n\t<li>that you meet the conditions required to give blood. The following questionnaires are designed to allow you to determine whether you can do so in principle, but only the pre-donation conversation with the nurse or doctor on the day can confirm your eligibility:</li>\n</ul>\n\n<p>- In Switzerland: <a href="https://www.hug-ge.ch/sites/interhug/files/structures/don_du_sang/fra-qmed-0220-41fo0210v4_0.pdf">https://www.hug-ge.ch/sites/interhug/files/structures/don_du_sang/fra-qmed-0220-41fo0210v4_0.pdf</a><br />\n- In France: <a href="https://dondesang.efs.sante.fr/puis-je-donner">https://dondesang.efs.sante.fr/puis-je-donner</a></p>\n\n<p> </p>\n\n<p>Where can I donate blood over the summer?</p>\n\n<p><strong>If you live in Switzerland:</strong></p>\n\n<ul>\n\t<li><strong>HUG Blood Transfusion Centre</strong><br />\n\tMondays, Tuesdays, Wednesdays and Fridays from 7.30 a.m. to 3.00 p.m. Thursdays from 11 a.m. to 7 p.m.<br />\n\tThe first and third Saturday of each month from 8.30 a.m. to 12 noon<br />\n\tRue Gabrielle-Perret-Gentil, 6<br />\n\t1205 Geneva<br />\n\tFifth floor<br />\n\t<br />\n\tAppointments can be made by telephone on +41 (0)22 372 39 01 or online: <a href="https://www.hug-ge.ch/don-du-sang/rendez-vous-ligne">https://www.hug-ge.ch/don-du-sang/rendez-vous-ligne</a>.</li>\n</ul>\n\n<p>If you have more questions about blood donation in Switzerland, see this website: <a href="https://www.hug-ge.ch/don-du-sang">https://www.hug-ge.ch/don-du-sang</a>.</p>\n\n<p><strong>If you live in France, you can attend the following sessions without an appointment:</strong></p>\n\n<ul>\n\t<li><strong><em>Salle des fêtes</em> in Thoiry</strong><br />\n\tRue des Cyprès, 01710 Thoiry<br />\n\tWednesday, 1 July from 4 p.m. to 7 p.m.<br />\n\t </li>\n\t<li><strong><em>Salle du levant</em> in Ferney-Voltaire</strong><br />\n\tChemin de Collex, 01210 Ferney-Voltaire<br />\n\tThursday, 2 July from 2.30 p.m. to 7.30 p.m.<br />\n\t </li>\n\t<li><strong>The Vidolet sports centre in Cessy</strong><br />\n\tChemin des écoliers, 01170 Cessy<br />\n\tMonday, 6 July from 3.00 p.m. to 7.00 p.m.<br />\n\t </li>\n\t<li><strong><em>Salle des fêtes</em> in St-Nizier-le-Bouchoux</strong><br />\n\t136, Route de Saint-Julien, 01560 St-Nizier-le-Bouchoux<br />\n\tFriday, 3 July from 3.30 p.m. to 6.30 p.m.<br />\n\t </li>\n\t<li><strong><em>L'Arande</em> in St-Julien en Genevois</strong><br />\n\t24, Grande rue, 74160 St-Julien en Genevois<br />\n\tThursday, 23 July from 4.00 p.m. to 7.30 p.m.<br />\n\t </li>\n\t<li><strong><em>L’Ellipse</em> cultural centre in Viry</strong><br />\n\t140, Rue Villa Mary, 74580 Viry<br />\n\tWednesday, 29 July from 4.30 p.m. to 7.30 p.m.<br />\n\t </li>\n\t<li><strong><em>Maison du don</em> in Annemasse</strong><br />\n\t1, route de Taninges<br />\n\tMondays from 8.30 a.m. to 12.30 p.m.<br />\n\tTuesdays from 12.30 p.m. to 6.00 p.m.<br />\n\t </li>\n\t<li><strong><em>Maison du don</em> in Metz-Tessy</strong><br />\n\t2, chemin des Croiselets<br />\n\tMondays from 8.00 a.m. to 7.00 p.m.<br />\n\tTuesdays, Wednesdays and Fridays from 8.00 a.m. to 1.00 p.m.<br />\n\tThursdays from 2.00 p.m. to 7.00 p.m.<br />\n\tSaturdays from 8.00 a.m. to 12 noon</li>\n</ul>\n\n<p>If you have more questions about blood donation in France (e.g. about where donation sessions are taking place in August), see this website: <a href="https://dondesang.efs.sante.fr/">https://dondesang.efs.sante.fr/</a>.</p>\n\n<p><strong>Special measures have been implemented to ensure that the necessary protective measures are respected and to guarantee the safety of donors, volunteers and staff during the COVID-19 pandemic.</strong></p>\n \N 2020-06-29 15:12:41.204 \N \N Blood donation: an essential act of solidarity \N \N NORMAL 1 -4 <h1>LS2 Report: A new schedule</h1>\n\n<p>As a result of the shutdown caused by the COVID-19 crisis, the injectors will restart at the end of the year and the LHC will restart in autumn 2021</p>\n\n<p>24 JUNE, 2020 </p>\n\n<p>| </p>\n\n<p>By <a href="https://home.cern/authors/anais-schaeffer">Anaïs Schaeffer</a></p>\n\n<p><a href="https://cds.cern.ch/images/CERN-HOMEWEB-PHO-2020-069-4"><img alt="LS2 report: a new schedule" src="https://cds.cern.ch/images/CERN-HOMEWEB-PHO-2020-069-4/file?size=large" style="height:200px; width:300px" /></a></p>\n\n<p>The vacuum team in the SPS after the restart of LS2 activities (Image: CERN)</p>\n\n<p>On 12 June, the new schedule for the activities of Long Shutdown 2 (LS2) was unveiled. The first test beams will circulate in the LHC at the end of September 2021, <a href="https://home.cern/news/news/accelerators/new-schedule-lhc-and-its-successor">four months after the date planned before the COVID-19 crisis</a>.</p>\n\n<p>The rest of CERN’s accelerator complex will restart gradually from December 2020 onwards. The various ISOLDE experiments and the experiments at the PS-SPS complex will therefore be able to start data taking as of summer 2021.</p>\n\n<p>The COVID-19 lockdown phase, which resulted in a shutdown of activities on the CERN site and the closure of many partner institutes, is now being followed by a gradual restart, all of which has naturally had an impact on the LS2 schedule. For example, it is now impossible for several activities to take place simultaneously in the same location, which is causing delays to the schedule. The main LHC experiments, which are international collaborations, are facing particular difficulties, since they are waiting for equipment and collaborators to arrive from all over the world.</p>\n\n<p><a href="https://cds.cern.ch/images/CERN-HOMEWEB-PHO-2020-069-1"><img alt="home.cern,Accelerators" src="https://cds.cern.ch/images/CERN-HOMEWEB-PHO-2020-069-1/file?size=large" style="height:400px; width:300px" /></a></p>\n\n<p>Restart of the activities of the DISMAC (Diode Insulation and Superconducting Magnets Consolidation) project in the LHC tunnel (Image: CERN)</p>\n\n<p>To allow them to complete their upgrade programmes, Run 3 of the LHC will therefore start in March 2022, provided that the current plan, which includes the installation of the second small wheel of ATLAS, is confirmed. If this is not the case, physics running will instead be brought forward to November 2021. “Initially, <a href="https://home.cern/news/news/experiments/ls2-report-atlas-upgrades-are-full-swing">ATLAS had planned to install its second small wheel during the 2021-2022 year-end technical stop</a> (YETS),” recalls José Miguel Jiménez, head of CERN’s Technology department. “But, under the new schedule, it might be possible – if the assembly process proceeds without any issues – to install it during LS2.” The schedule will be confirmed by the ATLAS collaboration in November.</p>\n\n<p>In order to keep to the schedule, around 500 additional people – mainly those involved in LS2 – have been returning to their activities on the CERN site every week since the start of Phase I of the <a href="https://home.cern/news/news/cern/gradual-and-safe-restart-plan-cerns-site-activities">restart plan</a> on 18 May. “We have been able to plan the restart precisely and optimally thanks to the excellent documentation work done by all the teams before the machines were put into safe mode in March,” emphasises Jiménez. This has made it possible to resume activities rapidly since May, although often in a different order: “It hasn’t always been possible to simply pick up where we left off,” he adds. “Many institutes are still closed, not to mention the fact that many of our collaborators and contractors are unable to come to CERN.”</p>\n\n<p>No changes have been made to the schedule beyond 2022. Provided that ATLAS completes its upgrades during LS2, the 2023/2024 YETS will be a normal shutdown. LS3 will start at the beginning of 2025.</p>\n\n<p><br />\n<strong>Closure of accelerators – current schedule:</strong></p>\n\n<p>The commissioning of the accelerators will begin this summer, starting with gradual hardware commissioning. The first beams from Linac 4 are expected in December this year.</p>\n\n<ul>\n\t<li>Closure of the PS Booster: 3 July 2020</li>\n\t<li>Closure of Linac 4: 3 July 2020</li>\n\t<li>Closure of the PS injection area: 28 August 2020</li>\n\t<li>Closure of Linac 3: 9 October 2020</li>\n\t<li>Closure of the PS extraction area: 23 October 2020</li>\n\t<li>Closure of the SPS: 4 December 2020</li>\n\t<li>Closure of the LHC: 19 February 2021</li>\n\t<li>Closure of LEIR: 21 May 2021</li>\n</ul>\n\n<p>Between now and the end of 2020, seven of the LHC’s eight sectors will be cooled down. Electrical quality tests, powering tests and a long campaign of quench training for the magnets will follow.</p>\n\n<p>A week of tests with low intensity beams will take place at the LHC at the end of September 2021.</p>\n\n<p><strong>Restart of physics runs – current schedule:</strong></p>\n\n<ul>\n\t<li>ISOLDE: end of June 2021</li>\n\t<li>North Area and HIE-ISOLDE: July 2021</li>\n\t<li>AD/ELENA: end of August 2021</li>\n\t<li>n_TOF: end of September 2021</li>\n\t<li>East Area: October 2021</li>\n\t<li>LHC: February 2022</li>\n</ul>\n\n<p>According to the new schedule, all of the LHC experiment halls will be closed on 1 February 2022.</p>\n\n<p><strong>________</strong></p>\n\n<p><strong>Special COVID-19 occupational health and safety measures</strong></p>\n\n<p>Special health and safety measures have been put in place at CERN to help in the fight against COVID-19 (see full details <a href="https://hse.cern/content/hse-related-questions-covid-19">on the HSE unit website</a>).</p>\n\n<p>In particular, we remind you that:</p>\n\n<ul>\n\t<li>It is compulsory to wear a mask indoors when other people are present (shared workspaces) or might be encountered (public areas). It is also compulsory to wear a mask outdoors if physical distancing of two metres cannot be observed. <strong>The mask must cover your mouth AND nose</strong> (we remind you that <a href="https://www.nature.com/articles/s41591-020-0868-6">infection occurs principally via the nasal mucous membrane</a>).</li>\n\t<li>Physical distancing of at least two metres must be observed.</li>\n\t<li>You should wash your hands regularly, in particular after the use of sanitary facilities or other communal facilities (cash machines, vending machines, access control devices, etc.), before and after handling a mask, and after coughing or sneezing.</li>\n\t<li>Tools, workstations and CERN vehicles must be cleaned regularly by the person who uses them, in accordance with the instructions provided.</li>\n\t<li>PPE (mask, protective face visor, gloves) must be worn and the applicable work procedures and instructions for use must be followed.</li>\n</ul>\n\n<p>We invite you to consult all the special COVID-19 occupational health and safety measures <a href="https://hse.cern/content/hse-related-questions-covid-19">on the HSE unit website</a>.</p>\n\n<p><strong>These exceptional measures must be followed in addition to the usual safety and radiation protection rules, which remain in force come what may.</strong></p>\n \N 2020-06-29 15:14:05.069 \N \N LS2 Report: A new schedule \N \N NORMAL 1 -5 <h1>Natalio Grueso, condenado a ocho años de prisión por el 'caso Niemeyer'</h1>\n\n<p><img alt="Natalio Grueso, Judit Pereiro y José María Vigil, durante el juicio del 'caso Niemeyer'." src="https://static.elcomercio.es/www/multimedia/202006/30/media/cortadas/natalio-grueso-judit-pereriro-jose-luis-vigil-sentencia-niemeyer-kZdB-U110658993823VzF-624x385@El%20Comercio.jpg" /></p>\n\n<p>Natalio Grueso, Judit Pereiro y José María Vigil, durante el juicio del 'caso Niemeyer'.</p>\n\n<h2>La Audiencia le considera culpable de un delito de malversación de caudales públicos y otro societario | Al agente de viajes José Luis Vigil le impone siete años y medio y al abogado José Luis Rebollo dos años mientras absuelve a la exmujer de Grueso, Judit Pereiro</h2>\n\n<p><img alt="Ruth Arias" src="https://static1.elcomercio.es/comun/img/2014/autor/autor-735-foto-2.jpeg" /></p>\n\n<p><a href="https://www.elcomercio.es/autor/ruth-arias-735.html">RUTH ARIAS </a> Martes, 30 junio 2020, 10:59</p>\n\n<p>11</p>\n\n<p>El que fuera <strong>director-gerente de la Fundación Niemeyer</strong> en su primera época, <a href="https://www.elcomercio.es/temas/personajes/natalio-grueso.html" target="_blank">Natalio Grueso</a>, ha sido condenado por la <strong>Audiencia Provincial de </strong></p>\n \N 2020-06-30 09:18:57.929 \N \N Horray! more text \N \N NORMAL 1 -6 <h1>Natalio Grueso, condenado a ocho años de prisión por el 'caso Niemeyer'</h1>\n\n<p><img alt="Natalio Grueso, Judit Pereiro y José María Vigil, durante el juicio del 'caso Niemeyer'." src="https://static.elcomercio.es/www/multimedia/202006/30/media/cortadas/natalio-grueso-judit-pereriro-jose-luis-vigil-sentencia-niemeyer-kZdB-U110658993823VzF-624x385@El%20Comercio.jpg" /></p>\n\n<p>Natalio Grueso, Judit Pereiro y José María Vigil, durante el juicio del 'caso Niemeyer'.</p>\n\n<h2>La Audiencia le considera culpable de un delito de malversación de caudales públicos y otro societario | Al agente de viajes José Luis Vigil le impone siete años y medio y al abogado José Luis Rebollo dos años mientras absuelve a la exmujer de Grueso, Judit Pereiro</h2>\n\n<p><img alt="Ruth Arias" src="https://static1.elcomercio.es/comun/img/2014/autor/autor-735-foto-2.jpeg" /></p>\n\n<p><a href="https://www.elcomercio.es/autor/ruth-arias-735.html">RUTH ARIAS </a> Martes, 30 junio 2020, 10:59</p>\n\n<p>11</p>\n\n<p>El que fuera <strong>director-gerente de la Fundación Niemeyer</strong> en su primera época, <a href="https://www.elcomercio.es/temas/personajes/natalio-grueso.html" target="_blank">Natalio Grueso</a>, ha sido condenado por la <strong>Audiencia Provincial de </strong></p>\n \N 2020-06-30 09:36:58.563 \N \N Horray! more text \N \N NORMAL 1 -7 <h1>Building Singularity Containers on GitLab-CI</h1>\n\n<p>Nov 18, 2018</p>\n\n<p>Today I’m happy to announce a Thanksgiving special treat for Singularity and GitLab users!</p>\n\n<p><img src="https://vsoch.github.io/assets/images/posts/gitlab/sregistry-gitlab.png" /></p>\n\n<p> </p>\n\n<p>The robots and I have listened to your requests for a GitLab CI template, and had a fun weekend exploring using GitLab for the first time. We are very excited about what we’ve found. GitLab has its own Continuous Integration service built in, which means that you can (from a single repository):</p>\n\n<ul>\n\t<li>build a container using the built in continuous integration</li>\n\t<li>store it as an artifact</li>\n\t<li>retrieve the artifact for use!</li>\n</ul>\n\n<p> </p>\n\n<p>What did we make for you? For the first step, I’ve added a new GitLab template to the <a href="https://github.com/singularityhub/singularity-ci">singularityhub/singularity-ci</a> repository. The template itself is served on GitLab as <a href="https://gitlab.com/singularityhub/gitlab-ci/">singularityhub/gitlab-ci</a>. You can find a complete tutorial for using the template in the README there, or continue reading for a quick rundown. But this wasn’t good enough, because it didn’t seem easy enough to retrieve the artifacts. So in addition to the template, I’ve added a <a href="https://singularityhub.github.io/sregistry-cli/client-gitlab">GitLab endpoint</a> to the Singularity Registry Client too. Yes, I was very busy this weekend! However the inspiration comes from <a href="https://github.com/tamasgal">@tamasgal</a>, who <a href="https://github.com/singularityhub/singularity-ci/issues/6">posted an issue</a> that he wanted it. And you know what Shrek says about Github issues…</p>\n\n<p><img src="https://vsoch.github.io/assets/images/posts/gitlab/issue-away.png" /></p>\n\n<p> </p>\n\n<p>I will again note that you don’t need to use the client to retrieve the artifacts, and you don’t even need to use the artifacts as your primary deployment spot. GitLab CI, along with other <a href="https://github.com/singularityhub/singularity-ci">other builders</a> are excellent choices for maintaining version controlled, reproducible builds. Once the build is done, you are free to deploy it to your heart’s content. Today we will cover the following set of steps:</p>\n\n<ol>\n\t<li>We will <strong>build</strong> a container recipe from a GitLab repository</li>\n\t<li>The container is saved as an <strong>artifact</strong>.</li>\n\t<li>We will <strong>pull</strong> the artifact using the Singularity Registry Client</li>\n</ol>\n\n<p>It seems fairly simple when you think about it, but in the above we have both version control for the recipes, an external build service, and programmatic access. It’s also free. If you are a scrappy developer like me, it’s time to celebrate and make some pancakes.</p>\n \N 2020-06-30 09:46:25.517 \N \N sdfkjasdklfjas \N \N NORMAL 1 -8 <h1>Building Singularity Containers on GitLab-CI</h1>\n\n<p>Nov 18, 2018</p>\n\n<p>Today I’m happy to announce a Thanksgiving special treat for Singularity and GitLab users!</p>\n\n<p><img src="https://vsoch.github.io/assets/images/posts/gitlab/sregistry-gitlab.png" /></p>\n\n<p> </p>\n\n<p>The robots and I have listened to your requests for a GitLab CI template, and had a fun weekend exploring using GitLab for the first time. We are very excited about what we’ve found. GitLab has its own Continuous Integration service built in, which means that you can (from a single repository):</p>\n\n<ul>\n\t<li>build a container using the built in continuous integration</li>\n\t<li>store it as an artifact</li>\n\t<li>retrieve the artifact for use!</li>\n</ul>\n\n<p> </p>\n\n<p>What did we make for you? For the first step, I’ve added a new GitLab template to the <a href="https://github.com/singularityhub/singularity-ci">singularityhub/singularity-ci</a> repository. The template itself is served on GitLab as <a href="https://gitlab.com/singularityhub/gitlab-ci/">singularityhub/gitlab-ci</a>. You can find a complete tutorial for using the template in the README there, or continue reading for a quick rundown. But this wasn’t good enough, because it didn’t seem easy enough to retrieve the artifacts. So in addition to the template, I’ve added a <a href="https://singularityhub.github.io/sregistry-cli/client-gitlab">GitLab endpoint</a> to the Singularity Registry Client too. Yes, I was very busy this weekend! However the inspiration comes from <a href="https://github.com/tamasgal">@tamasgal</a>, who <a href="https://github.com/singularityhub/singularity-ci/issues/6">posted an issue</a> that he wanted it. And you know what Shrek says about Github issues…</p>\n\n<p><img src="https://vsoch.github.io/assets/images/posts/gitlab/issue-away.png" /></p>\n\n<p> </p>\n\n<p>I will again note that you don’t need to use the client to retrieve the artifacts, and you don’t even need to use the artifacts as your primary deployment spot. GitLab CI, along with other <a href="https://github.com/singularityhub/singularity-ci">other builders</a> are excellent choices for maintaining version controlled, reproducible builds. Once the build is done, you are free to deploy it to your heart’s content. Today we will cover the following set of steps:</p>\n\n<ol>\n\t<li>We will <strong>build</strong> a container recipe from a GitLab repository</li>\n\t<li>The container is saved as an <strong>artifact</strong>.</li>\n\t<li>We will <strong>pull</strong> the artifact using the Singularity Registry Client</li>\n</ol>\n\n<p>It seems fairly simple when you think about it, but in the above we have both version control for the recipes, an external build service, and programmatic access. It’s also free. If you are a scrappy developer like me, it’s time to celebrate and make some pancakes.</p>\n \N 2020-06-30 09:46:32.635 \N \N notification 2 \N \N NORMAL 1 -9 <p>We're happy to announce the new Notification channel on Push notification service.</p>\n\n<p>Please access it on <a href="https://test-notifications-service.web.cern.ch">https://test-notifications-service.web.cern.ch</a> (Only accessible within CERN network)</p>\n\n<p><em><strong>Disclaimer: Just a test in preparation of the ASDF demo, channel will be deleted soon</strong></em></p>\n\n<p><img alt="" src="https://storage.googleapis.com/website-dev-images/sites/default/files/postman.jpg" style="height:204px; width:370px" /></p>\n\n<p> </p>\n\n<p> </p>\n \N 2020-06-30 10:05:10.991 \N \N New WebFrameworks Notification channel \N \N NORMAL 2 -10 <p>test</p>\n \N 2020-09-08 07:42:18.323 \N \N test \N \N NORMAL 9 -11 <p>est</p>\n \N 2020-09-08 08:00:16.182 \N \N stt \N \N NORMAL 9 -12 <p>test</p>\n \N 2020-09-08 09:14:10.231 \N \N test \N \N NORMAL 9 -13 <p>test</p>\n \N 2020-09-08 09:28:06.641 \N \N test \N \N NORMAL 9 -14 <p>test</p>\n \N 2020-09-08 09:33:35.255 \N \N test \N \N NORMAL 9 -15 <p><strong>Hi,</strong></p>\n\n<p>Just testing here.</p>\n\n<p> </p>\n\n<p>Cheers,</p>\n\n<p>Carina</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-04 14:40:30.455 \N \N Test Carina \N \N NORMAL 10 -16 <p>Test Carina</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-04 14:46:29.331 \N \N Test 2 \N \N NORMAL 9 -17 <p><strong>Topic 1</strong></p>\n\n<p> </p>\n\n<p>test test test</p>\n\n<p> </p>\n\n<p><img alt="" src="https://codimd.web.cern.ch/uploads/upload_9dad2b06960c16a7e778b03d96c8038a.png" style="height:580px; width:504px" /></p>\n\n<p> </p>\n\n<p> </p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 18:44:45.852 \N \N Test Carina \N \N NORMAL 9 -18 <p>test</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 18:46:13.439 \N \N \N \N NORMAL 1 -19 <p>test carina</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 18:47:35.981 \N \N test carina \N \N NORMAL 11 -20 <p><strong>Woohoooo!</strong></p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 19:09:44.854 \N \N First working notification \N \N NORMAL 11 -21 <p>t</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 19:11:40.794 \N \N testing \N \N NORMAL 11 -22 <p>test</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 19:14:28.172 \N \N test \N \N NORMAL 11 -23 <p>oi</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 19:15:19.52 \N \N oi \N \N NORMAL 11 -24 <p>test</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 19:21:54.628 \N \N test \N \N NORMAL 9 -25 <p>test</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 19:22:30.393 \N \N test \N \N NORMAL 1 -26 <p>test</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-05 19:23:43.964 \N \N test \N \N NORMAL 12 -27 <p>Dear subscribers,</p>\n\n<p>This week news follows. </p>\n\n<p><strong>Topic 1</strong></p>\n\n<ul>\n\t<li>Lorem</li>\n\t<li>ipsum</li>\n</ul>\n\n<p><strong>Topic 2</strong></p>\n\n<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. </p>\n\n<p>See you next week,</p>\n\n<p>Myself.</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-09 13:37:22.695 \N \N This week news! \N \N NORMAL 1 -28 <p>Dear subscribers,</p>\n\n<p>This week news follows. </p>\n\n<p><strong>Topic 1</strong></p>\n\n<ul>\n\t<li>Lorem</li>\n\t<li>ipsum</li>\n</ul>\n\n<p><strong>Topic 2</strong></p>\n\n<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. </p>\n\n<p>See you next week,</p>\n\n<p>Myself.</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-09 13:40:57.227 \N \N test \N \N NORMAL 1 -29 <p>Dear subscribers,</p>\n\n<p>This week news follows. </p>\n\n<p> </p>\n\n<p><strong>Topic 1</strong></p>\n\n<ul>\n\t<li>bla </li>\n\t<li>bla</li>\n\t<li>bla</li>\n</ul>\n\n<p> </p>\n\n<p><strong>Topic 2</strong></p>\n\n<p>Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.</p>\n\n<p> </p>\n\n<p>See you next week,</p>\n\n<p>Myself.</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-09 13:55:12.19 \N \N test \N \N NORMAL 1 -30 <p>Carina</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-13 13:05:38.409 \N \N Test \N \N NORMAL 9 -31 <p>carina</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-16 10:12:15.769 \N \N test \N \N NORMAL 9 -32 <p>test</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-16 10:18:23.686 \N \N test \N \N NORMAL 9 -33 <p>test</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-16 11:27:51.502 \N \N test \N \N NORMAL 9 -34 <p>test</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-16 11:27:53.98 \N \N test \N \N NORMAL 9 -35 <p>test</p>\n\n<div id="vidyowebrtcscreenshare_is_installed"> </div>\n \N 2020-11-17 12:54:26.59 \N \N test \N \N NORMAL 13 -36 <p>test</p>\n \N 2020-12-03 09:14:46.791 \N \N test \N \N NORMAL 1 -37 <p>test</p>\n \N 2020-12-03 12:23:56.434 \N \N test \N \N NORMAL 1 -\. - - --- --- TOC entry 3353 (class 0 OID 259892) --- Dependencies: 228 --- Data for Name: Preferences; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push."Preferences" (id, type, "userUsername", "targetPrimaryKey", name, "notificationPriority", "rangeStart", "rangeEnd") FROM stdin; -1 DAILY eduardoa 1 \N \N \N \N -2 LIVE proncero 2 Send daily feed with normal notifications \N \N \N -4 DAILY proncero 2 test \N \N \N -6 DAILY crdeoliv 10 only once \N \N \N -3 DAILY proncero \N Daily feed with all normal notifications \N \N \N -9 LIVE dchatzic \N Default preference Low,Normal,Important \N \N -10 LIVE dchatzic 2 Test \N \N -12 LIVE crdeoliv 12 test-carina important,normal,low 00:00:00 23:45:00 -15 LIVE crdeoliv 2 WF-LOW low 00:00:00 23:45:00 -21 LIVE dchatzic \N Morning notifications important 09:15:00 14:00:00 -\. - - --- --- TOC entry 3355 (class 0 OID 259910) --- Dependencies: 230 --- Data for Name: Services; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push."Services" (id, name, email) FROM stdin; -\. - - --- --- TOC entry 3346 (class 0 OID 259843) --- Dependencies: 221 --- Data for Name: UserNotifications; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push."UserNotifications" (id, sent, read, pinned, archived, "userUsername", "notificationId") FROM stdin; -\. - - --- --- TOC entry 3354 (class 0 OID 259902) --- Dependencies: 229 --- Data for Name: Users; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push."Users" (username, email, enabled) FROM stdin; -proncero pablo.roncero.fernandez@cern.ch t -eduardoa eduardo.alvarez.fernandez@cern.ch t -ijakovlj igor.jakovljevic@cern.ch t -crdeoliv carina.oliveira.antunes@cern.ch t -awagner andreas.wagner@cern.ch t -dchatzic dimitra.chatzichrysou@cern.ch t -kolodzie michal.kolodziejski@cern.ch t -ctojeiro caetan.tojeiro.carpente@cern.ch t -ormancey emmanuel.ormancey@cern.ch t -\. - - --- --- TOC entry 3358 (class 0 OID 259934) --- Dependencies: 233 --- Data for Name: channels_groups__groups; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push.channels_groups__groups ("channelsPrimaryKey", "groupsId") FROM stdin; -1 08d779a7-4bf3-5e57-cee5-46cae1512fc0 -2 186d8dfc-2774-43a8-91b5-a887fcb6ba4a -\. - - --- --- TOC entry 3356 (class 0 OID 259920) --- Dependencies: 231 --- Data for Name: channels_members__users; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push.channels_members__users ("channelsPrimaryKey", "usersUsername") FROM stdin; -6 proncero -10 crdeoliv -2 eduardoa -2 proncero -12 crdeoliv -9 crdeoliv -\. - - --- --- TOC entry 3357 (class 0 OID 259927) --- Dependencies: 232 --- Data for Name: channels_unsubscribed__users; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push.channels_unsubscribed__users ("channelsPrimaryKey", "usersUsername") FROM stdin; -1 proncero -11 crdeoliv -9 dchatzic -\. - - --- --- TOC entry 3361 (class 0 OID 260093) --- Dependencies: 236 --- Data for Name: preferences_disabled_channels__channels; Type: TABLE DATA; Schema: push; Owner: test --- - -COPY push.preferences_disabled_channels__channels ("preferencesId", "channelsPrimaryKey") FROM stdin; -\. - - --- --- TOC entry 3342 (class 0 OID 258948) --- Dependencies: 217 --- Data for Name: Notifications; Type: TABLE DATA; Schema: push_test; Owner: test --- - -COPY push_test."Notifications" (id, target, subject, body, sent, "sendAt", "sentAt", "fromId", tags, link, summary, "contentType", "imgUrl", priority) FROM stdin; -5 proncero test test t \N 2019-10-24 12:59:02.644 test-con-dani \N \N \N \N \N NORMAL -6 proncero test test t \N 2019-11-05 14:16:15.384 test-con-dani \N \N \N \N \N NORMAL -7 proncero test test t \N 2019-11-05 15:12:13.049 test-con-dani \N \N \N \N \N NORMAL -9 proncero How to build beautiful CERN websites <span>How to build beautiful CERN websites </span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Kate Kahle</div>\n </div>\n <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span>\n<span>Tue, 11/05/2019 - 14:19</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p>\n\n<p>Last year, when D8 was launched at CERN, it was accompanied by a <a href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p>\n\n<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p>\n\n<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p>\n\n<p>If you would like to join the Drupal community to find out the latest news and improvements, <a href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p>\n</div>\n t \N 2019-11-11 16:39:03.673 test-con-dani \N \N \N \N \N NORMAL -12 proncero Be seen, be safe <span>Be seen, be safe</span>\n<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 11/05/2019 - 12:27</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a>\n<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p>\n\n<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p>\n</div>\n t \N 2019-11-11 16:39:03.648 test-con-dani \N \N \N \N \N NORMAL -13 proncero Halfway towards LHC consolidation <span>Halfway towards LHC consolidation</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Corinne Pralavorio</div>\n </div>\n <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span>\n<span>Fri, 10/18/2019 - 11:18</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The Large Hadron Collider is such a huge and sophisticated machine that the slightest alteration requires an enormous amount of work. During the second long shutdown (LS2), teams are hard at work <a href="https://home.cern/news/news/accelerators/more-spring-clean-lhc-magnets">reinforcing the electrical insulation of the accelerator’s superconducting dipole diodes</a>. The LHC contains not one, not two, but 1232 superconducting dipole magnets, each with a diode system to upgrade. That’s why no fewer than 150 people are needed to carry out the 70 000 tasks involved in this work.</p>\n\n<p>The project is now halfway to completion. One of the machine’s eight sectors, containing 154 magnets, is now closed and the final leak tests are under way. Work is ongoing in the seven other sectors and the teams are working at a rate of ten interconnections consolidated per day.</p>\n\n<p>The work is part of a broader project called DISMAC (“Diodes Insulation and Superconducting Magnets Consolidation”), which also includes the replacement of magnets and maintenance operations on the current leads, the devices that supply the LHC with electricity. Twenty-two magnets have already been replaced and two others have been removed from the machine in order to replace their beam screens, which are components located in the vacuum chamber.</p>\n\n<p>A plethora of upgrade and maintenance work is also being carried out in the tunnel on all the equipment, from the cryogenics system to the vacuum, beam instrumentation and technical infrastructures.</p>\n\n<figure><img alt="magnet,LHC,LS2,tunnel,TI2,Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201906-163-1/file?size=large" /><figcaption>Replacement of one of the LHC superconducting dipole magnets during the accelerator consolidation campaign. (Image: Maximilien Brice and Julien Ordan/CERN)</figcaption></figure><hr /></div>\n t \N 2019-11-11 16:39:03.58 test-con-dani \N \N \N \N \N NORMAL -10 proncero Beamline for Schools 2019 participants present results <span>Beamline for Schools 2019 participants present results</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Joseph Piergrossi</div>\n </div>\n <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 11/08/2019 - 13:58</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS">\n <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a>\n <figcaption>\n The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p>\n\n<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p>\n\n<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p>\n\n<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p>\n\n<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p>\n\n<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p>\n\n<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p>\n\n<p>Want to join? Preregistration for BL4S 2020 is <a href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p>\n\n<hr /><p>More photos <a href="https://cds.cern.ch/record/2698994">on CDS</a>:</p>\n\n<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p>\n</div>\n t \N 2019-11-11 16:39:03.579 test-con-dani \N \N \N \N \N NORMAL -11 proncero Medipix: Two decades of turning technology into applications <span>Medipix: Two decades of turning technology into applications</span>\n<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 10/18/2019 - 10:11</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2253263" data-filename="studio%2000051" id="CERN-PHOTO-201702-048-3"><a href="//cds.cern.ch/images/CERN-PHOTO-201702-048-3" title="View on CDS">\n <img alt="Knowledge Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201702-048-3/file?size=medium" /></a>\n <figcaption><span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>How could microchips developed for detectors at the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC) be used beyond high-energy physics? This was a question that led to the <a href="https://cern.ch/medipix">Medipix</a> and Timepix families of pixel-sensor chips. Researchers saw many possible applications for this technology, and for the last 20 years these chips have been used in medical imaging, in spotting forgeries in the art world, in detecting radioactive material and more. A <a href="https://indico.cern.ch/event/782801/timetable/">recent CERN symposium</a> commemorated the two decades since the Medipix2 collaboration was established, in 1999.</p>\n\n<p>Pixel-sensor chips are used in detectors at the LHC to trace the paths of electrically charged particles. When a particle hits the sensor, it deposits a charge that is processed by the electronics. This is similar to light hitting pixels in a digital camera, but instead they register particles up to 40 million times a second.</p>\n\n<p>In the late 1990s, engineers and physicists at CERN were developing integrated circuits for pixel technologies. They realised that adding a counter to each pixel and counting the number of particles hitting the sensors could allow the chips to be used for medical imaging. The Medipix2 chip was born. Later, the Timepix chip added the ability to record either the arrival time of the particles or the energy deposited within a pixel.</p>\n\n<p>As the chips evolved from Medipix2 to Medipix3, their growing use in medical imaging led to the <a href="https://home.cern/news/news/knowledge-sharing/first-3d-colour-x-ray-human-using-cern-technology">first colour X-ray of parts of the human body</a> in 2018, with the first clinical trials now beginning in New Zealand. In addition, the versatile chips have gone beyond medicine, for example, a start-up called InsightART allows researchers to use Medipix3 chips to <a href="https://home.cern/news/news/knowledge-sharing/particle-detectors-meet-canvas">peer through the layers of works of art</a> and study the composition of materials to determine the authenticity of pieces attributed to renowned artists.</p>\n\n<p>The team behind InsightART, based in Prague, <a href="https://insightart.eu/2018/06/08/is-this-a-newly-discovered-van-gogh/">recently scanned an alleged Van Gogh</a>, concluding that the work was most likely to have been produced by the Dutch master, having observed an underlying sketch very similar to other figures Van Gogh painted at the time. The work will be sent to the Van Gogh Museum to be vetted with this evidence, and it might be that not one but two Van Goghs have been found in the same piece.</p>\n\n<p><a href="https://medipix.web.cern.ch/news/nasa-cern-timepix-technology-advances-miniaturized-radiation-detection">Timepix-based detectors have been aboard the International Space Station since 2012</a> to measure the radiation dose to which astronauts and equipment are exposed, and in 2015, high-school students from the UK <a href="https://home.cern/news/news/knowledge-sharing/tim-peakes-timpix-launch-space">sent </a><a href="https://home.cern/news/news/knowledge-sharing/tim-peakes-timpix-launch-space">their own</a> Timepix-based detector to the ISS with astronaut Tim Peake. The ability of the chips to detect gamma rays has been exploited to help with the decommissioning of nuclear reactors and is being evaluated for the detection of thyroid cancer with greater resolution than before and with a lower radiation dose to the patient.</p>\n\n<p>The Medipix and Timepix chips, developed by three collaborations involving 32 institutes in total, have been remarkable examples of <a href="https://kt.cern/">knowledge transfer from CERN</a> to wider society. You can learn more about the history of Medipix and their many applications <a class="bulletin" href="https://cds.cern.ch/video/2678560?showTitle=true">in this talk</a> by Medipix spokesperson Michael Campbell, given in June 2019.</p>\n\n<p><iframe allowfullscreen="" frameborder="0" height="360" src="https://cds.cern.ch/video/2678560?showTitle=true" width="640"></iframe></p>\n</div>\n t \N 2019-11-11 16:39:03.672 test-con-dani \N \N \N \N \N NORMAL -8 proncero Broadening tunnel vision for future accelerators <span>Broadening tunnel vision for future accelerators</span>\n<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Wed, 10/23/2019 - 10:20</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692937" data-filename="201910-334_08" id="CERN-PHOTO-201910-334-8"><a href="//cds.cern.ch/images/CERN-PHOTO-201910-334-8" title="View on CDS">\n <img alt="HL-LHC Underground civil engineering galleries progress" src="//cds.cern.ch/images/CERN-PHOTO-201910-334-8/file?size=medium" /></a>\n <figcaption>\n HL-LHC Underground civil engineering galleries\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>What could the next generation of particle accelerators look like? With current technology, the bigger an accelerator, the higher the energy of the collisions it produces and the greater the likelihood of discovering new physics phenomena. Particle physicists and accelerator engineers therefore dream of machines that are even bigger than the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC), with its 27-km circumference.</p>\n\n<p>For CERN’s civil engineers, a new accelerator requires a bespoke deep-underground tunnel, and the tunnel’s shape, depth and orientation as well as its access shafts are largely constrained by the local geography. Such an accelerator built at CERN would be bound by mountains, and, if circular, would need to go under Lake Geneva and completely enclose the Salève mountain of the Prealps.</p>\n\n<figure class="cds-image breakout-right" id="OPEN-PHO-CIVIL-2019-001-1"><a href="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1" title="View on CDS"><img alt="home.cern,Civil Engineering and Infrastructure" src="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1/file?size=medium" /></a>\n<figcaption>Two proposed post-LHC accelerators – CLIC and the FCC – present unique challenges to CERN’s civil engineers<span> (Image: CERN)</span></figcaption></figure><p>The two largest projects under consideration for a post-LHC collider at CERN are the <a href="https://home.cern/science/accelerators/compact-linear-collider">Compact Linear Collider</a> (CLIC) and the <a href="https://home.cern/science/accelerators/future-circular-collider">Future Circular Collider</a> (FCC). Their scale would dwarf CERN’s existing infrastructure, making them some of the largest tunnelling projects in the world. Civil engineers therefore need to survey the geological, environmental and technical constraints of these machines.</p>\n\n<p>A <a href="https://indico.cern.ch/event/823271/">tunnelling workshop</a> that took place last week at CERN brought together civil-engineering experts from industry and academia to examine how new technologies and methods could optimise tunnel design and asset management. It is part of ongoing collaborations that have already seen CERN and the engineering consultancy Arup develop a first-of-its-kind tunnel optimisation tool to provide the best design when fed all the required parameters. The tool has already shown the feasibility of tunnels for either the FCC or CLIC in the local area, to help support the ongoing update for the European Strategy of Particle Physics that will guide the direction of particle physics and related fields to the mid-2020s and beyond.</p>\n\n<p>Find out more about the tunnelling challenges of CERN’s civil engineers for the next-generation of particle accelerators in “<a href="https://cerncourier.com/a/tunnelling-for-physics/">Tunnelling for Physics</a>” on the <em>CERN Courier</em>’s website.</p>\n</div>\n t \N 2019-11-11 16:39:03.576 test-con-dani \N \N \N \N \N NORMAL -16 proncero ALICE: the journey of a cosmopolitan detector <span>ALICE: the journey of a cosmopolitan detector</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Camille Monnin</div>\n </div>\n <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span>\n<span>Thu, 10/31/2019 - 10:04</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p>\n\n<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p>\n\n<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p>\n\n<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p>\n\n<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p>\n\n<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-128-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1/file?size=large" /></a>\n<figcaption>A detector piece from Berkeley Lab, on its way to CERN.<span> (Image: Lawrence Berkeley National Laboratory)</span></figcaption></figure><p> </p>\n</div>\n t \N 2019-11-11 16:39:03.671 test-con-dani \N \N \N \N \N NORMAL -14 proncero LHCf gears up to probe birth of cosmic-ray showers <span>LHCf gears up to probe birth of cosmic-ray showers</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Ana Lopes</div>\n </div>\n <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span>\n<span>Fri, 11/08/2019 - 13:48</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS">\n <img alt="One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a>\n <figcaption>\n One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p>\n\n<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p>\n\n<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p>\n\n<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p>\n\n<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p>\n\n<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p>\n\n<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p>\n\n<p> </p>\n</div>\n t \N 2019-11-11 16:39:03.65 test-con-dani \N \N \N \N \N NORMAL -15 proncero LS2 Report: Linac4 knocking at the door of the PS Booster <span>LS2 Report: Linac4 knocking at the door of the PS Booster</span>\n<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 10/29/2019 - 14:05</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Busy activity has returned to the CERN Control Centre (CCC), where the Operation group coordinates the current <a href="https://home.cern/science/accelerators/linear-accelerator-4">Linac4</a> test run, supported by the Accelerators and Beam Physics (ABP) group and all the involved equipment groups. As we write, the nominal 160 MeV beam has already reached the Linac4 dump.</p>\n\n<p>After the ongoing second long shutdown of CERN’s accelerator complex (LS2), Linac4 will replace the retired Linac2 to provide protons to the LHC and all the CERN experiments that are served by CERN’s proton-accelerator chain. “For this purpose, Linac4 has by now been connected to the LHC injector chain through its new transfer line to the PS tunnel and the existing transfer lines to the PS Booster (PSB),” says Bettina Mikulec, who coordinates the test run.</p>\n\n<p>In order to prepare Linac4 for the challenge of delivering reliably high-quality beam to the PSB from its first day of post-LS2 operation in 2020, a special beam run started on 30 September to measure its beam parameters in the completely renovated 15-m-long emittance-measurement line (LBE), only 50 m away from the PSB injection point. “In this line, we can of course measure the emittance of the beam – the transverse dimensions of the beam and its energy spread – but also its longitudinal parameters in the transfer line,” adds Bettina Mikulec. “The LBE line is also very close to the PSB entrance, so everything we measure there should not be far off from the final characteristics at the PSB injection point.”</p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-127-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1/file?size=large" /></a>\n<figcaption>The new LBE line. At the end of this line, we can see the LBE dump (green shielding blocks) located just at the wall of the PSB<span> (Image: CERN)</span></figcaption></figure><p>Until 6 December, negative hydrogen ions* will cover the 86 m of the Linac4 to be sent along the new and renovated transfer lines (160 m in total) into the new LBE line, before terminating their flight in a dump located just at the wall of the PSB.</p>\n\n<p>“During this run, hardware and software changes deployed since <a href="https://home.cern/news/news/accelerators/long-road-linac4">the last Linac4 reliability run</a>, which took place in 2018, will be commissioned, with the aim of solving some remaining issues and enhance the beam quality,” says Alessandra Lombardi, Linac4 project leader in the ABP group.</p>\n\n<p>In addition, the required operational beam configurations for the 2020 start-up will be prepared as much as possible in advance to allow a rapid Linac4 start in April 2020, when various beams will be set up for the PSB, so that the PSB can restart with beam under optimum conditions in September 2020.</p>\n\n<p> </p>\n\n<p><em>* Hydrogen atoms with an additional electron, giving it a net negative charge. Both electrons are stripped during injection from Linac4 into the PS Booster to leave only protons. </em></p>\n\n<p>________</p>\n\n<p><em>Follow the progress of the LBE run on <a class="bulletin" href="https://op-webtools.web.cern.ch/vistar/vistars.php?usr=Linac4">the online Vistar</a>.</em></p>\n</div>\n t \N 2019-11-11 16:39:03.675 test-con-dani \N \N \N \N \N NORMAL -17 proncero CMS measures Higgs boson’s mass with unprecedented precision <span>CMS measures Higgs boson’s mass with unprecedented precision</span>\n<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 10/25/2019 - 10:37</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692545" data-filename="HtoGammaGamma_v1" id="CMS-PHO-EVENTS-2019-008-4"><a href="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4" title="View on CDS">\n <img alt="Measurement of the Higgs boson mass: candidate two-photon and four-lepton events" src="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4/file?size=medium" /></a>\n <figcaption>\n Event in which a candidate SM Higgs boson decays into two photons indicated by the green towers representing energy deposited in the electromagnetic calorimeter.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The <a href="https://home.cern/science/physics/higgs-boson">Higgs boson</a> is a special particle. It is the manifestation of a field that gives mass to elementary particles. But this field also gives mass to the Higgs boson itself. A precise measurement of the Higgs boson’s mass not only furthers our knowledge of physics but also sheds new light on searches planned at future colliders.</p>\n\n<p>Since discovering this unique particle in 2012, the <a href="https://home.cern/science/experiments/atlas">ATLAS</a> and <a href="https://home.cern/science/experiments/cms">CMS</a> collaborations at CERN’s <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> have been busy determining its properties. In the <a href="https://home.cern/science/physics/standard-model">Standard Model of particle physics</a>, the Higgs boson’s mass is closely related to the strength of the particle’s interaction with itself. Comparing precise measurements of these two properties is a crucial means of testing the predictions of the Standard Model and helps search for physics beyond the predictions of this theory. In addition to probing its “self-interaction” strength, the researchers have also paid careful attention to the exact mass of the Higgs boson.</p>\n\n<p>When it was first discovered, the particle’s mass was measured to be around 125 gigaelectronvolts (GeV) but it wasn’t known with high precision. Analysis of much more data was needed before reducing the errors in such a measurement. Indeed, ATLAS and CMS have been improving this precision with their respective measurements over the years. Last year, ATLAS measured the Higgs mass to be 124.97 GeV with a precision of 0.24 GeV or 0.19%. Now, the CMS collaboration has announced the most precise measurement so far of this property: 125.35 GeV with a precision of 0.15 GeV, or 0.12%.</p>\n\n<p>Like most members of the zoo of known particles, the Higgs boson is unstable and transforms – or “decays” – nearly instantaneously into lighter particles. The mass measurement was based on two very different transformations of the Higgs boson, namely decays to four leptons via two intermediate Z bosons and decays to pairs of photons. To arrive at the mass value, the scientists combined CMS results of these two decays from two datasets: the first was recorded in 2011 and 2012 while the second came from 2016.</p>\n\n<p>This measurement adds another piece to the puzzle of the exciting world of subatomic particles.</p>\n\n<p><em>More details on the <a href="https://cms.cern/news/cms-precisely-measures-mass-higgs-boson">CMS website</a>.</em></p>\n</div>\n t \N 2019-11-11 16:39:03.676 test-con-dani \N \N \N \N \N NORMAL -18 proncero ALICE: the journey of a cosmopolitan detector <span>ALICE: the journey of a cosmopolitan detector</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Camille Monnin</div>\n </div>\n <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span>\n<span>Thu, 10/31/2019 - 10:04</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p>\n\n<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p>\n\n<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p>\n\n<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p>\n\n<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p>\n\n<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-128-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1/file?size=large" /></a>\n<figcaption>A detector piece from Berkeley Lab, on its way to CERN.<span> (Image: Lawrence Berkeley National Laboratory)</span></figcaption></figure><p> </p>\n</div>\n t \N 2019-11-12 09:39:46.793 test-con-dani \N \N \N \N \N NORMAL -20 proncero Broadening tunnel vision for future accelerators <span>Broadening tunnel vision for future accelerators</span>\n<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Wed, 10/23/2019 - 10:20</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692937" data-filename="201910-334_08" id="CERN-PHOTO-201910-334-8"><a href="//cds.cern.ch/images/CERN-PHOTO-201910-334-8" title="View on CDS">\n <img alt="HL-LHC Underground civil engineering galleries progress" src="//cds.cern.ch/images/CERN-PHOTO-201910-334-8/file?size=medium" /></a>\n <figcaption>\n HL-LHC Underground civil engineering galleries\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>What could the next generation of particle accelerators look like? With current technology, the bigger an accelerator, the higher the energy of the collisions it produces and the greater the likelihood of discovering new physics phenomena. Particle physicists and accelerator engineers therefore dream of machines that are even bigger than the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC), with its 27-km circumference.</p>\n\n<p>For CERN’s civil engineers, a new accelerator requires a bespoke deep-underground tunnel, and the tunnel’s shape, depth and orientation as well as its access shafts are largely constrained by the local geography. Such an accelerator built at CERN would be bound by mountains, and, if circular, would need to go under Lake Geneva and completely enclose the Salève mountain of the Prealps.</p>\n\n<figure class="cds-image breakout-right" id="OPEN-PHO-CIVIL-2019-001-1"><a href="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1" title="View on CDS"><img alt="home.cern,Civil Engineering and Infrastructure" src="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1/file?size=medium" /></a>\n<figcaption>Two proposed post-LHC accelerators – CLIC and the FCC – present unique challenges to CERN’s civil engineers<span> (Image: CERN)</span></figcaption></figure><p>The two largest projects under consideration for a post-LHC collider at CERN are the <a href="https://home.cern/science/accelerators/compact-linear-collider">Compact Linear Collider</a> (CLIC) and the <a href="https://home.cern/science/accelerators/future-circular-collider">Future Circular Collider</a> (FCC). Their scale would dwarf CERN’s existing infrastructure, making them some of the largest tunnelling projects in the world. Civil engineers therefore need to survey the geological, environmental and technical constraints of these machines.</p>\n\n<p>A <a href="https://indico.cern.ch/event/823271/">tunnelling workshop</a> that took place last week at CERN brought together civil-engineering experts from industry and academia to examine how new technologies and methods could optimise tunnel design and asset management. It is part of ongoing collaborations that have already seen CERN and the engineering consultancy Arup develop a first-of-its-kind tunnel optimisation tool to provide the best design when fed all the required parameters. The tool has already shown the feasibility of tunnels for either the FCC or CLIC in the local area, to help support the ongoing update for the European Strategy of Particle Physics that will guide the direction of particle physics and related fields to the mid-2020s and beyond.</p>\n\n<p>Find out more about the tunnelling challenges of CERN’s civil engineers for the next-generation of particle accelerators in “<a href="https://cerncourier.com/a/tunnelling-for-physics/">Tunnelling for Physics</a>” on the <em>CERN Courier</em>’s website.</p>\n</div>\n t \N 2019-11-12 09:39:46.966 test-con-dani \N \N \N \N \N NORMAL -21 proncero Beamline for Schools 2019 participants present results <span>Beamline for Schools 2019 participants present results</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Joseph Piergrossi</div>\n </div>\n <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 11/08/2019 - 13:58</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS">\n <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a>\n <figcaption>\n The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p>\n\n<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p>\n\n<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p>\n\n<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p>\n\n<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p>\n\n<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p>\n\n<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p>\n\n<p>Want to join? Preregistration for BL4S 2020 is <a href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p>\n\n<hr /><p>More photos <a href="https://cds.cern.ch/record/2698994">on CDS</a>:</p>\n\n<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p>\n</div>\n t \N 2019-11-12 09:39:46.796 test-con-dani \N \N \N \N \N NORMAL -22 proncero LHCf gears up to probe birth of cosmic-ray showers <span>LHCf gears up to probe birth of cosmic-ray showers</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Ana Lopes</div>\n </div>\n <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span>\n<span>Fri, 11/08/2019 - 13:48</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS">\n <img alt="One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a>\n <figcaption>\n One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p>\n\n<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p>\n\n<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p>\n\n<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p>\n\n<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p>\n\n<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p>\n\n<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p>\n\n<p> </p>\n</div>\n t \N 2019-11-12 09:39:46.795 test-con-dani \N \N \N \N \N NORMAL -23 proncero Medipix: Two decades of turning technology into applications <span>Medipix: Two decades of turning technology into applications</span>\n<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 10/18/2019 - 10:11</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2253263" data-filename="studio%2000051" id="CERN-PHOTO-201702-048-3"><a href="//cds.cern.ch/images/CERN-PHOTO-201702-048-3" title="View on CDS">\n <img alt="Knowledge Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201702-048-3/file?size=medium" /></a>\n <figcaption><span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>How could microchips developed for detectors at the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC) be used beyond high-energy physics? This was a question that led to the <a href="https://cern.ch/medipix">Medipix</a> and Timepix families of pixel-sensor chips. Researchers saw many possible applications for this technology, and for the last 20 years these chips have been used in medical imaging, in spotting forgeries in the art world, in detecting radioactive material and more. A <a href="https://indico.cern.ch/event/782801/timetable/">recent CERN symposium</a> commemorated the two decades since the Medipix2 collaboration was established, in 1999.</p>\n\n<p>Pixel-sensor chips are used in detectors at the LHC to trace the paths of electrically charged particles. When a particle hits the sensor, it deposits a charge that is processed by the electronics. This is similar to light hitting pixels in a digital camera, but instead they register particles up to 40 million times a second.</p>\n\n<p>In the late 1990s, engineers and physicists at CERN were developing integrated circuits for pixel technologies. They realised that adding a counter to each pixel and counting the number of particles hitting the sensors could allow the chips to be used for medical imaging. The Medipix2 chip was born. Later, the Timepix chip added the ability to record either the arrival time of the particles or the energy deposited within a pixel.</p>\n\n<p>As the chips evolved from Medipix2 to Medipix3, their growing use in medical imaging led to the <a href="https://home.cern/news/news/knowledge-sharing/first-3d-colour-x-ray-human-using-cern-technology">first colour X-ray of parts of the human body</a> in 2018, with the first clinical trials now beginning in New Zealand. In addition, the versatile chips have gone beyond medicine, for example, a start-up called InsightART allows researchers to use Medipix3 chips to <a href="https://home.cern/news/news/knowledge-sharing/particle-detectors-meet-canvas">peer through the layers of works of art</a> and study the composition of materials to determine the authenticity of pieces attributed to renowned artists.</p>\n\n<p>The team behind InsightART, based in Prague, <a href="https://insightart.eu/2018/06/08/is-this-a-newly-discovered-van-gogh/">recently scanned an alleged Van Gogh</a>, concluding that the work was most likely to have been produced by the Dutch master, having observed an underlying sketch very similar to other figures Van Gogh painted at the time. The work will be sent to the Van Gogh Museum to be vetted with this evidence, and it might be that not one but two Van Goghs have been found in the same piece.</p>\n\n<p><a href="https://medipix.web.cern.ch/news/nasa-cern-timepix-technology-advances-miniaturized-radiation-detection">Timepix-based detectors have been aboard the International Space Station since 2012</a> to measure the radiation dose to which astronauts and equipment are exposed, and in 2015, high-school students from the UK <a href="https://home.cern/news/news/knowledge-sharing/tim-peakes-timpix-launch-space">sent </a><a href="https://home.cern/news/news/knowledge-sharing/tim-peakes-timpix-launch-space">their own</a> Timepix-based detector to the ISS with astronaut Tim Peake. The ability of the chips to detect gamma rays has been exploited to help with the decommissioning of nuclear reactors and is being evaluated for the detection of thyroid cancer with greater resolution than before and with a lower radiation dose to the patient.</p>\n\n<p>The Medipix and Timepix chips, developed by three collaborations involving 32 institutes in total, have been remarkable examples of <a href="https://kt.cern/">knowledge transfer from CERN</a> to wider society. You can learn more about the history of Medipix and their many applications <a class="bulletin" href="https://cds.cern.ch/video/2678560?showTitle=true">in this talk</a> by Medipix spokesperson Michael Campbell, given in June 2019.</p>\n\n<p><iframe allowfullscreen="" frameborder="0" height="360" src="https://cds.cern.ch/video/2678560?showTitle=true" width="640"></iframe></p>\n</div>\n t \N 2019-11-12 09:39:46.964 test-con-dani \N \N \N \N \N NORMAL -47 proncero LHCf gears up to probe birth of cosmic-ray showers <span>LHCf gears up to probe birth of cosmic-ray showers</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Ana Lopes</div>\n </div>\n <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span>\n<span>Fri, 11/08/2019 - 13:48</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS">\n <img alt="One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a>\n <figcaption>\n One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p>\n\n<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p>\n\n<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p>\n\n<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p>\n\n<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p>\n\n<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p>\n\n<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p>\n\n<p> </p>\n</div>\n t \N 2019-11-15 11:21:33.627 test-con-dani \N \N \N \N \N NORMAL -48 proncero LS2 Report: LHCb looks to the future with SciFi detector <span>LS2 Report: LHCb looks to the future with SciFi detector</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Achintya Rao</div>\n </div>\n <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Tue, 11/12/2019 - 08:53</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2701306" data-filename="201911-373_04" id="CERN-PHOTO-201911-373-4"><a href="//cds.cern.ch/images/CERN-PHOTO-201911-373-4" title="View on CDS">\n <img alt="LHCb's new scintillating-fibre (SciFi) tracker" src="//cds.cern.ch/images/CERN-PHOTO-201911-373-4/file?size=medium" /></a>\n <figcaption>\n The new tracker is made of over 10,000 kilometres of polystyrene-based scintillating fibres and will help LHCb record data at a higher luminosity and rate from Run 3 onwards\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the <a href="https://home.cern/science/experiments/lhcb">LHCb detector</a> at the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a>, the ongoing <a href="https://home.cern/tags/long-shutdown-2">second long shutdown (LS2)</a> of CERN’s accelerator complex will be a period of metamorphosis. After two successful data-collection runs, the detector is being upgraded to improve the precision of its physics measurements, many of which are the best in the world. There will therefore be five times more collisions every time proton bunches cross within the detector after LS2 and the LHCb collaboration plans on increasing the data-readout rate from 1 MHz to the LHC’s maximum interaction frequency of 40 MHz (or every 25 nanoseconds).</p>\n\n<p>In addition to replacing nearly all of the electronics and data-acquisition systems to handle the enormous increase in data production, LHCb is replacing its tracking detectors with new ones, such as the scintillating-fibre tracker, or SciFi. It is the first time such a large tracker, with a small granularity and high spatial resolution, has been made using this technology. The SciFi will be placed behind the dipole magnet of LHCb.</p>\n\n<p>Scintillating fibres, as the name suggests, are optical fibres – with a polystyrene base, in this case – that emit tens of photons in the blue-green wavelength when a particle interacts with them. Secondary scintillator dyes have been added to the polystyrene to amplify the light and shift it to longer wavelengths so it can reach custom-made silicon photomultipliers (SiPM) that convert optical light to electrical signals. The technology has been well tested at other high-energy-physics experiments. The fibres themselves are lightweight, they can produce and transmit light within the 25-nanosecond window and they are suitably tolerant to the ionising radiation expected in the future.</p>\n\n<p>Each scintillating fibre making up the sub-detector is 0.25 mm in diameter and nearly 2.5 m in length. The fibres will be packed into modules that will reside in three stations within LHCb, each made of four so-called “detection planes”, with the photomultipliers located at the top and bottom of each plane. “The fibres have been painstakingly examined, wound into multi-layer ribbons, assembled into detector modules and thoroughly tested,” explains Blake Leverington, who is coordinating part of the SciFi project for LHCb. “The fibres provide a single-hit precision better than 100 microns and the single-hit efficiency over the area of the detector is better than 99%.” In total, over 10 000 km of precision-made scintillating fibres will adorn LHCb.</p>\n\n<p>Unlike the other LHC detectors, LHCb is asymmetric in design and studies particles that fly very close to the beam pipe after being produced in proton–proton collisions. However, operating a sensitive detector this close to the beam pipe brings its own problems. Simulations show that radiation damage from collision debris would darken the fibres closest to the beam pipe by up to 40% over the lifetime of LHCb. This would make it harder for the produced light to be transmitted through the fibres, but the detector is expected to remain efficient despite this.</p>\n\n<p>The photomultipliers located at the top and bottom of each SciFi detection plane will be bombarded by neutrons produced in the calorimeters that sit further downstream. The radiation damage results in so-called “dark noise”, where thermally excited electrons cause the SiPMs to produce a signal that mimics the signal coming from individual photons. In addition to shielding placed between the SciFi and the calorimeters, a complex cooling system has been developed to chill the SiPMs. “Measurements have shown that the rate of dark noise can be reduced by a factor of two for every 10 °C drop in temperature,” points out Leverington. The SiPMs have been mounted on special 3D-printed titanium cold-bars that are cooled to −40 °C.</p>\n\n<p>“The project has had contributions from more than a hundred scientists, students, engineers and technicians from 17 partner institutes in 10 countries,” says Leverington. “We have worked together for seven years to bring SciFi to life.” Currently, the SciFi modules, services and electronics are being assembled and installed in the 12 mechanical frames in the assembly hall at the LHCb site at Point 8 of the LHC ring. The first SciFi components are planned to be installed in spring next year.</p>\n</div>\n t \N 2019-11-15 11:30:30.955 test-con-dani \N \N \N \N \N NORMAL -49 proncero Beamline for Schools 2019 participants present results <span>Beamline for Schools 2019 participants present results</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Joseph Piergrossi</div>\n </div>\n <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 11/08/2019 - 13:58</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS">\n <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a>\n <figcaption>\n The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p>\n\n<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p>\n\n<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p>\n\n<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p>\n\n<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p>\n\n<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p>\n\n<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p>\n\n<p>Want to join? Preregistration for BL4S 2020 is <a class="bulletin" href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p>\n\n<hr /><p>More photos <a class="bulletin" href="https://cds.cern.ch/record/2698994">on CDS</a></p>\n\n<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p>\n</div>\n t \N 2019-11-15 11:30:30.955 test-con-dani \N \N \N \N \N NORMAL -51 proncero Spacewalk for AMS: Watch live with CERN and ESA <span>Spacewalk for AMS: Watch live with CERN and ESA</span>\n<span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span>\n<span>Thu, 11/14/2019 - 12:33</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>On Friday 15 November, European Space Agency (ESA) astronaut Luca Parmitano and NASA astronaut Andrew Morgan will begin the first of a series of complex spacewalks to service the <a href="https://home.cern/science/experiments/ams">Alpha Magnetic Spectrometer (AMS-02)</a>. The spacewalk will be streamed live via <a href="http://www.esa.int/ESA_Multimedia/ESA_Web_TV">ESA Web TV</a> from 12.50 p.m. CET and will include commentaries from CERN and ESA.</p>\n\n<p>This series of spacewalks is expected to be the most challenging since those to repair the <a href="https://www.nasa.gov/mission_pages/hubble/servicing/index.html">Hubble Space Telescope</a>. AMS was originally intended to run for three years, after its installation on the International Space Station in 2011, and was not designed to be maintained in orbit. However, the success of its results to date have meant that its mission has been extended.</p>\n\n<figure><iframe allowfullscreen="" frameborder="0" height="360" id="ls_embed_1573808401" scrolling="no" src="https://livestream.com/accounts/362/events/8890996/player?width=640&height=360&enableInfoAndActivity=true&defaultDrawer=&autoPlay=true&mute=false" width="640"></iframe>\n<figcaption>Watch the spacewalk live on <a href="https://livestream.com/ESA/SpacewalkforAMS">ESA Web TV</a></figcaption></figure><p>AMS-02 is a particle-physics detector that uses the unique environment of space to study the universe and its origin. It searches for antimatter and dark matter while precisely measuring cosmic-ray particles – more than 140 billion particles to date. The detector, which measures 60 cubic metres and weighs 7.5 tonnes, was assembled by an international team at CERN, and researchers, astronauts and operations teams have had to develop new procedures and more than 20 custom tools to extend the instrument’s life.</p>\n\n<p>A key task for the astronauts is to replace the AMS-02 cooling system and to fix a coolant leak, and the pair have trained extensively for this intricate operation on the ground. It will involve cutting and splicing eight cooling tubes, connecting them to the new system and reconnecting a myriad of power and data cables. It is the first time that astronauts will cut and reconnect cooling lines in orbit.</p>\n\n<p>The first AMS spacewalk on Friday is expected to last about six hours and sets the scene for at least three more. It will be streamed live on <a href="http://www.esa.int/ESA_Multimedia/ESA_Web_TV">ESA Web TV</a> and the first two hours will feature commentary from scientists at the AMS Payload Operations Control Centre (POCC) at CERN as well as astronaut and operation experts at ESA’s astronaut centre in Germany.</p>\n\n<p>CERN’s contributions will include a tour of the POCC by AMS Experiment and Operations Coordinator Mike Capell, from Massachusetts Institute of Technology (MIT). Here, AMS physicists take 24-hour shifts to operate and control the various components of AMS from the ground. Zhan Zhang, also from MIT, is the lead engineer of the Upgraded Tracker Thermal System, which is being installed during the spacewalks. She will show the laboratory at CERN where an identical spare of the system is kept in space conditions and will explain how the system works and what the astronauts will have to do to install it on the AMS detector in space. AMS scientists Mercedes Paniccia from the University of Geneva, Alberto Oliva from INFN Bologna and Andrei Kounine, from MIT, will explain the science of AMS as the spacewalk takes place and can answer your questions.</p>\n\n<p>You can already tweet questions ahead of the live broadcast to <a href="https://twitter.com/esaspaceflight">@esaspaceflight</a> or <a href="https://twitter.com/CERN">@CERN</a> using the hashtag <a href="https://twitter.com/hashtag/SpacewalkForAMS">#SpacewalkForAMS</a>.</p>\n</div>\n t \N 2019-11-15 11:30:30.956 test-con-dani \N \N \N \N \N NORMAL -19 proncero Be seen, be safe <span>Be seen, be safe</span>\n<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 11/05/2019 - 12:27</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a>\n<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p>\n\n<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p>\n</div>\n t \N 2019-11-12 09:39:46.795 test-con-dani \N \N \N \N \N NORMAL -24 proncero How to build beautiful CERN websites <span>How to build beautiful CERN websites </span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Kate Kahle</div>\n </div>\n <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span>\n<span>Tue, 11/05/2019 - 14:19</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p>\n\n<p>Last year, when D8 was launched at CERN, it was accompanied by a <a href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p>\n\n<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p>\n\n<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p>\n\n<p>If you would like to join the Drupal community to find out the latest news and improvements, <a href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p>\n</div>\n t \N 2019-11-12 09:39:46.997 test-con-dani \N \N \N \N \N NORMAL -25 proncero Halfway towards LHC consolidation <span>Halfway towards LHC consolidation</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Corinne Pralavorio</div>\n </div>\n <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span>\n<span>Fri, 10/18/2019 - 11:18</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The Large Hadron Collider is such a huge and sophisticated machine that the slightest alteration requires an enormous amount of work. During the second long shutdown (LS2), teams are hard at work <a href="https://home.cern/news/news/accelerators/more-spring-clean-lhc-magnets">reinforcing the electrical insulation of the accelerator’s superconducting dipole diodes</a>. The LHC contains not one, not two, but 1232 superconducting dipole magnets, each with a diode system to upgrade. That’s why no fewer than 150 people are needed to carry out the 70 000 tasks involved in this work.</p>\n\n<p>The project is now halfway to completion. One of the machine’s eight sectors, containing 154 magnets, is now closed and the final leak tests are under way. Work is ongoing in the seven other sectors and the teams are working at a rate of ten interconnections consolidated per day.</p>\n\n<p>The work is part of a broader project called DISMAC (“Diodes Insulation and Superconducting Magnets Consolidation”), which also includes the replacement of magnets and maintenance operations on the current leads, the devices that supply the LHC with electricity. Twenty-two magnets have already been replaced and two others have been removed from the machine in order to replace their beam screens, which are components located in the vacuum chamber.</p>\n\n<p>A plethora of upgrade and maintenance work is also being carried out in the tunnel on all the equipment, from the cryogenics system to the vacuum, beam instrumentation and technical infrastructures.</p>\n\n<figure><img alt="magnet,LHC,LS2,tunnel,TI2,Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201906-163-1/file?size=large" /><figcaption>Replacement of one of the LHC superconducting dipole magnets during the accelerator consolidation campaign. (Image: Maximilien Brice and Julien Ordan/CERN)</figcaption></figure><hr /></div>\n t \N 2019-11-12 09:39:46.998 test-con-dani \N \N \N \N \N NORMAL -26 proncero CMS measures Higgs boson’s mass with unprecedented precision <span>CMS measures Higgs boson’s mass with unprecedented precision</span>\n<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 10/25/2019 - 10:37</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692545" data-filename="HtoGammaGamma_v1" id="CMS-PHO-EVENTS-2019-008-4"><a href="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4" title="View on CDS">\n <img alt="Measurement of the Higgs boson mass: candidate two-photon and four-lepton events" src="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4/file?size=medium" /></a>\n <figcaption>\n Event in which a candidate SM Higgs boson decays into two photons indicated by the green towers representing energy deposited in the electromagnetic calorimeter.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The <a href="https://home.cern/science/physics/higgs-boson">Higgs boson</a> is a special particle. It is the manifestation of a field that gives mass to elementary particles. But this field also gives mass to the Higgs boson itself. A precise measurement of the Higgs boson’s mass not only furthers our knowledge of physics but also sheds new light on searches planned at future colliders.</p>\n\n<p>Since discovering this unique particle in 2012, the <a href="https://home.cern/science/experiments/atlas">ATLAS</a> and <a href="https://home.cern/science/experiments/cms">CMS</a> collaborations at CERN’s <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> have been busy determining its properties. In the <a href="https://home.cern/science/physics/standard-model">Standard Model of particle physics</a>, the Higgs boson’s mass is closely related to the strength of the particle’s interaction with itself. Comparing precise measurements of these two properties is a crucial means of testing the predictions of the Standard Model and helps search for physics beyond the predictions of this theory. In addition to probing its “self-interaction” strength, the researchers have also paid careful attention to the exact mass of the Higgs boson.</p>\n\n<p>When it was first discovered, the particle’s mass was measured to be around 125 gigaelectronvolts (GeV) but it wasn’t known with high precision. Analysis of much more data was needed before reducing the errors in such a measurement. Indeed, ATLAS and CMS have been improving this precision with their respective measurements over the years. Last year, ATLAS measured the Higgs mass to be 124.97 GeV with a precision of 0.24 GeV or 0.19%. Now, the CMS collaboration has announced the most precise measurement so far of this property: 125.35 GeV with a precision of 0.15 GeV, or 0.12%.</p>\n\n<p>Like most members of the zoo of known particles, the Higgs boson is unstable and transforms – or “decays” – nearly instantaneously into lighter particles. The mass measurement was based on two very different transformations of the Higgs boson, namely decays to four leptons via two intermediate Z bosons and decays to pairs of photons. To arrive at the mass value, the scientists combined CMS results of these two decays from two datasets: the first was recorded in 2011 and 2012 while the second came from 2016.</p>\n\n<p>This measurement adds another piece to the puzzle of the exciting world of subatomic particles.</p>\n\n<p><em>More details on the <a href="https://cms.cern/news/cms-precisely-measures-mass-higgs-boson">CMS website</a>.</em></p>\n</div>\n t \N 2019-11-12 09:39:46.994 test-con-dani \N \N \N \N \N NORMAL -27 proncero LS2 Report: Linac4 knocking at the door of the PS Booster <span>LS2 Report: Linac4 knocking at the door of the PS Booster</span>\n<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 10/29/2019 - 14:05</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Busy activity has returned to the CERN Control Centre (CCC), where the Operation group coordinates the current <a href="https://home.cern/science/accelerators/linear-accelerator-4">Linac4</a> test run, supported by the Accelerators and Beam Physics (ABP) group and all the involved equipment groups. As we write, the nominal 160 MeV beam has already reached the Linac4 dump.</p>\n\n<p>After the ongoing second long shutdown of CERN’s accelerator complex (LS2), Linac4 will replace the retired Linac2 to provide protons to the LHC and all the CERN experiments that are served by CERN’s proton-accelerator chain. “For this purpose, Linac4 has by now been connected to the LHC injector chain through its new transfer line to the PS tunnel and the existing transfer lines to the PS Booster (PSB),” says Bettina Mikulec, who coordinates the test run.</p>\n\n<p>In order to prepare Linac4 for the challenge of delivering reliably high-quality beam to the PSB from its first day of post-LS2 operation in 2020, a special beam run started on 30 September to measure its beam parameters in the completely renovated 15-m-long emittance-measurement line (LBE), only 50 m away from the PSB injection point. “In this line, we can of course measure the emittance of the beam – the transverse dimensions of the beam and its energy spread – but also its longitudinal parameters in the transfer line,” adds Bettina Mikulec. “The LBE line is also very close to the PSB entrance, so everything we measure there should not be far off from the final characteristics at the PSB injection point.”</p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-127-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1/file?size=large" /></a>\n<figcaption>The new LBE line. At the end of this line, we can see the LBE dump (green shielding blocks) located just at the wall of the PSB<span> (Image: CERN)</span></figcaption></figure><p>Until 6 December, negative hydrogen ions* will cover the 86 m of the Linac4 to be sent along the new and renovated transfer lines (160 m in total) into the new LBE line, before terminating their flight in a dump located just at the wall of the PSB.</p>\n\n<p>“During this run, hardware and software changes deployed since <a href="https://home.cern/news/news/accelerators/long-road-linac4">the last Linac4 reliability run</a>, which took place in 2018, will be commissioned, with the aim of solving some remaining issues and enhance the beam quality,” says Alessandra Lombardi, Linac4 project leader in the ABP group.</p>\n\n<p>In addition, the required operational beam configurations for the 2020 start-up will be prepared as much as possible in advance to allow a rapid Linac4 start in April 2020, when various beams will be set up for the PSB, so that the PSB can restart with beam under optimum conditions in September 2020.</p>\n\n<p> </p>\n\n<p><em>* Hydrogen atoms with an additional electron, giving it a net negative charge. Both electrons are stripped during injection from Linac4 into the PS Booster to leave only protons. </em></p>\n\n<p>________</p>\n\n<p><em>Follow the progress of the LBE run on <a class="bulletin" href="https://op-webtools.web.cern.ch/vistar/vistars.php?usr=Linac4">the online Vistar</a>.</em></p>\n</div>\n t \N 2019-11-12 09:39:46.996 test-con-dani \N \N \N \N \N NORMAL -28 proncero Broadening tunnel vision for future accelerators <span>Broadening tunnel vision for future accelerators</span>\n<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Wed, 10/23/2019 - 10:20</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692937" data-filename="201910-334_08" id="CERN-PHOTO-201910-334-8"><a href="//cds.cern.ch/images/CERN-PHOTO-201910-334-8" title="View on CDS">\n <img alt="HL-LHC Underground civil engineering galleries progress" src="//cds.cern.ch/images/CERN-PHOTO-201910-334-8/file?size=medium" /></a>\n <figcaption>\n HL-LHC Underground civil engineering galleries\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>What could the next generation of particle accelerators look like? With current technology, the bigger an accelerator, the higher the energy of the collisions it produces and the greater the likelihood of discovering new physics phenomena. Particle physicists and accelerator engineers therefore dream of machines that are even bigger than the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> (LHC), with its 27-km circumference.</p>\n\n<p>For CERN’s civil engineers, a new accelerator requires a bespoke deep-underground tunnel, and the tunnel’s shape, depth and orientation as well as its access shafts are largely constrained by the local geography. Such an accelerator built at CERN would be bound by mountains, and, if circular, would need to go under Lake Geneva and completely enclose the Salève mountain of the Prealps.</p>\n\n<figure class="cds-image breakout-right" id="OPEN-PHO-CIVIL-2019-001-1"><a href="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1" title="View on CDS"><img alt="home.cern,Civil Engineering and Infrastructure" src="//cds.cern.ch/images/OPEN-PHO-CIVIL-2019-001-1/file?size=medium" /></a>\n<figcaption>Two proposed post-LHC accelerators – CLIC and the FCC – present unique challenges to CERN’s civil engineers<span> (Image: CERN)</span></figcaption></figure><p>The two largest projects under consideration for a post-LHC collider at CERN are the <a href="https://home.cern/science/accelerators/compact-linear-collider">Compact Linear Collider</a> (CLIC) and the <a href="https://home.cern/science/accelerators/future-circular-collider">Future Circular Collider</a> (FCC). Their scale would dwarf CERN’s existing infrastructure, making them some of the largest tunnelling projects in the world. Civil engineers therefore need to survey the geological, environmental and technical constraints of these machines.</p>\n\n<p>A <a href="https://indico.cern.ch/event/823271/">tunnelling workshop</a> that took place last week at CERN brought together civil-engineering experts from industry and academia to examine how new technologies and methods could optimise tunnel design and asset management. It is part of ongoing collaborations that have already seen CERN and the engineering consultancy Arup develop a first-of-its-kind tunnel optimisation tool to provide the best design when fed all the required parameters. The tool has already shown the feasibility of tunnels for either the FCC or CLIC in the local area, to help support the ongoing update for the European Strategy of Particle Physics that will guide the direction of particle physics and related fields to the mid-2020s and beyond.</p>\n\n<p>Find out more about the tunnelling challenges of CERN’s civil engineers for the next-generation of particle accelerators in “<a href="https://cerncourier.com/a/tunnelling-for-physics/">Tunnelling for Physics</a>” on the <em>CERN Courier</em>’s website.</p>\n</div>\n t \N 2019-11-12 11:16:29.71 test-con-dani \N \N \N \N \N NORMAL -29 proncero ALICE: the journey of a cosmopolitan detector <span>ALICE: the journey of a cosmopolitan detector</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Camille Monnin</div>\n </div>\n <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span>\n<span>Thu, 10/31/2019 - 10:04</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p>\n\n<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p>\n\n<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p>\n\n<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p>\n\n<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p>\n\n<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-128-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-128-1/file?size=large" /></a>\n<figcaption>A detector piece from Berkeley Lab, on its way to CERN.<span> (Image: Lawrence Berkeley National Laboratory)</span></figcaption></figure><p> </p>\n</div>\n t \N 2019-11-12 11:16:29.71 test-con-dani \N \N \N \N \N NORMAL -30 proncero LS2 Report: Linac4 knocking at the door of the PS Booster <span>LS2 Report: Linac4 knocking at the door of the PS Booster</span>\n<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 10/29/2019 - 14:05</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Busy activity has returned to the CERN Control Centre (CCC), where the Operation group coordinates the current <a href="https://home.cern/science/accelerators/linear-accelerator-4">Linac4</a> test run, supported by the Accelerators and Beam Physics (ABP) group and all the involved equipment groups. As we write, the nominal 160 MeV beam has already reached the Linac4 dump.</p>\n\n<p>After the ongoing second long shutdown of CERN’s accelerator complex (LS2), Linac4 will replace the retired Linac2 to provide protons to the LHC and all the CERN experiments that are served by CERN’s proton-accelerator chain. “For this purpose, Linac4 has by now been connected to the LHC injector chain through its new transfer line to the PS tunnel and the existing transfer lines to the PS Booster (PSB),” says Bettina Mikulec, who coordinates the test run.</p>\n\n<p>In order to prepare Linac4 for the challenge of delivering reliably high-quality beam to the PSB from its first day of post-LS2 operation in 2020, a special beam run started on 30 September to measure its beam parameters in the completely renovated 15-m-long emittance-measurement line (LBE), only 50 m away from the PSB injection point. “In this line, we can of course measure the emittance of the beam – the transverse dimensions of the beam and its energy spread – but also its longitudinal parameters in the transfer line,” adds Bettina Mikulec. “The LBE line is also very close to the PSB entrance, so everything we measure there should not be far off from the final characteristics at the PSB injection point.”</p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-127-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1" title="View on CDS"><img alt="home.cern,Accelerators" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-127-1/file?size=large" /></a>\n<figcaption>The new LBE line. At the end of this line, we can see the LBE dump (green shielding blocks) located just at the wall of the PSB<span> (Image: CERN)</span></figcaption></figure><p>Until 6 December, negative hydrogen ions* will cover the 86 m of the Linac4 to be sent along the new and renovated transfer lines (160 m in total) into the new LBE line, before terminating their flight in a dump located just at the wall of the PSB.</p>\n\n<p>“During this run, hardware and software changes deployed since <a href="https://home.cern/news/news/accelerators/long-road-linac4">the last Linac4 reliability run</a>, which took place in 2018, will be commissioned, with the aim of solving some remaining issues and enhance the beam quality,” says Alessandra Lombardi, Linac4 project leader in the ABP group.</p>\n\n<p>In addition, the required operational beam configurations for the 2020 start-up will be prepared as much as possible in advance to allow a rapid Linac4 start in April 2020, when various beams will be set up for the PSB, so that the PSB can restart with beam under optimum conditions in September 2020.</p>\n\n<p> </p>\n\n<p><em>* Hydrogen atoms with an additional electron, giving it a net negative charge. Both electrons are stripped during injection from Linac4 into the PS Booster to leave only protons. </em></p>\n\n<p>________</p>\n\n<p><em>Follow the progress of the LBE run on <a class="bulletin" href="https://op-webtools.web.cern.ch/vistar/vistars.php?usr=Linac4">the online Vistar</a>.</em></p>\n</div>\n t \N 2019-11-12 11:16:29.879 test-con-dani \N \N \N \N \N NORMAL -31 proncero Beamline for Schools 2019 participants present results <span>Beamline for Schools 2019 participants present results</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Joseph Piergrossi</div>\n </div>\n <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 11/08/2019 - 13:58</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS">\n <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a>\n <figcaption>\n The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p>\n\n<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p>\n\n<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p>\n\n<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p>\n\n<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p>\n\n<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p>\n\n<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p>\n\n<p>Want to join? Preregistration for BL4S 2020 is <a href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p>\n\n<hr /><p>More photos <a href="https://cds.cern.ch/record/2698994">on CDS</a>:</p>\n\n<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p>\n</div>\n t \N 2019-11-12 11:16:29.81 test-con-dani \N \N \N \N \N NORMAL -32 proncero Computer Security: When CERN.CH is not CERN… <span>Computer Security: When CERN.CH is not CERN…</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">The Computer Security Team</div>\n </div>\n <span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 11/12/2019 - 11:34</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>We recently received an e-mail from a colleague who was astonished to learn that an e-mail that appears to be sent from “CERN.CH” does not necessarily really come from someone at CERN… Indeed, everything is not always what it seems. Therefore, let us explain to you when CERN.CH is CERN and when it isn’t.</p>\n\n<p>For e-mail, the sender address can be anything. Just like on the envelope of a normal hand-written letter, any sender address can be specified. “CERN.CH” can easily be spoofed so that an e-mail looks like it comes from someone at CERN, but actually doesn’t<sup>1</sup>. The ancient e-mail protocol cannot do better and any technical means to improve on this break other functions when sending e-mails (like posting to mailing lists...) – see our <em>Bulletin</em> article “<a href="https://cds.cern.ch/record/2215901?ln=en">E-mail is broken and there is nothing we can do</a>”. There is no good protection apart from CERN’s SPAM filters. Once an e-mail has passed those filters, the second line of defence is you... So, just hold on a second and think about whether each e-mail is really intended for you. See our recommendations on how to identify malicious e-mails on <a href="https://cern.ch/security/recommendations/en/malicious_email.shtml">the Computer Security Team’s homepage</a>. If you’re really in doubt, just ask us to check by e-mailing Computer.Security@cern.ch.</p>\n\n<p>And since we are already on the subject: no, similar domains with different endings (so-called top-level domains like .CH) are definitely not CERN’s! For example, browsing to CERN.CA gives you “…a non-profit organisation in Canada striving to promote the Francophone culture throughout the country”. CERN.BE points to a neuropsychologist. And CERN.SK is the webpage of a Slovak central register for work-related accidents… Moreover, there are also many other domains that look like CERN’s but aren’t: CERM.CH, CERN.ORG, CERN.CG, XERN.CH, CEM.CH (this one is more difficult to detect in lowercase as “cem.ch” – “r” and “n” look quite like “m”, don’t they?). These are usually called typo-squatting or Doppelgänger domains, i.e. domains whose name is just one character away from CERN’s. Attackers love them as they can be used to trick us into clicking on the wrong link: “cem.ch”, anyone?</p>\n\n<p>For your protection, since adversaries might try to use them for their malicious deeds, we have blocked a series of these typo-squatting domains within CERN’s domain name servers. That means that you should be redirected to a warning page instead of arriving at the adversary’s malicious one. However, this only protects you when browsing to those domains from within CERN. For a more holistic approach, we also tried to buy some of these domains in order to prevent any abuse, but didn’t succeed in all cases...</p>\n\n<p>Therefore, once more, we have to count on you: security is not complete without you! Be vigilant!!! CERN is CERN.CH and dotCERN. Any other domain does not belong to the Organization<sup>2</sup> and should be accessed with care. The best thing is just to ignore these domains and go somewhere else. Or ping us at Computer.Security@cern.ch and we will check for you whether or not a domain is benign.</p>\n\n<p> </p>\n\n<p><em><sup>1</sup>For the technically-minded among you: checking the so-called header information does reveal the real origin of an e-mail unless this has also been heavily tampered with. If that information points to the CERN e-mail servers, it is most likely that the mail has been sent from a real CERN e-mail address. Still, there is no guarantee that the sender is the person behind the name in that e-mail address. His or her account might have been compromised. But that’s another story. </em></p>\n\n<p><em><sup>2</sup>For the pettifoggers among you: CERN does indeed own a series of other domains: e.g. CERN.EU, CERN.JOBS and CERN.ORG, but also CIXP.CH, INDICO.GLOBAL, OHWR.COM, REANA.IO, ZENODO.COM. But mentioning all of those would double the length of this article…</em></p>\n\n<p>_________</p>\n\n<p><em>Do you want to learn more about computer security incidents and issues at CERN? Follow our <a href="https://cern.ch/security/reports/en/monthly_reports.shtml">Monthly Report</a>. For further information, questions or help, check <a href="https://cern.ch/Computer.Security">our website</a> or contact us at Computer.Security@cern.ch.</em></p>\n</div>\n t \N 2019-11-12 11:16:29.709 test-con-dani \N \N \N \N \N NORMAL -33 proncero Be seen, be safe <span>Be seen, be safe</span>\n<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 11/05/2019 - 12:27</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a>\n<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p>\n\n<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p>\n</div>\n t \N 2019-11-12 11:16:29.706 test-con-dani \N \N \N \N \N NORMAL -50 proncero Aligning the HL-LHC magnets with interferometry <span>Aligning the HL-LHC magnets with interferometry</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Anaïs Schaeffer</div>\n </div>\n <span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 11/12/2019 - 09:35</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>CERN surveyors have just finalised a system that can determine, in real time, the position of certain components inside the (sealed) cryostats of the future <a href="https://home.cern/science/accelerators/high-luminosity-lhc">High-Luminosity LHC</a> (HL-LHC). Currently, only the position of the cryostats themselves can be measured, using sensors that perform continuous measurements. “This new system has been specially developed for the HL-LHC, to be able directly to determine the position of cold masses at the level of the inner triplets, located on either side of the ATLAS and CMS experiments, and the position of the crab cavities inside their cryostat,” says Hélène Mainaud Durand, in charge of alignment in the High-Luminosity LHC upgrade. “It will be a real plus to be able to monitor the alignment of these components continuously, especially during the accelerator’s cycles of heating and cooling.”</p>\n\n<p>The new procedure is based on frequency sweeping interferometry (FSI), a distance-measurement method that simultaneously performs several absolute distance measurements between a measuring head and targets, and relates them to a common benchmark measurement. “Thanks to this technique, it will be possible to deduce the position of the cold mass to within a few micrometres relative to the cryostat by making 12 distance measurements between the cryostat and the cold mass,” says Mainaud Durand. Each cold mass will therefore be equipped with 12 targets, which are reflective glass spheres that have been specially designed for this procedure. Opposite the targets are 12 laser heads, which are attached to the cryostat and connected by optical fibres to a laser acquisition system.</p>\n\n<p>Even though FSI is commonly used in metrology, adapting it for use in a cryogenic environment has not been completely straightforward: “We have had to overcome several challenges posed by the extreme conditions inside the accelerators,” says Mateusz Sosin, the mechatronic engineer in charge of this development. “The first problem became apparent during a test carried out at the cryogenic temperature of 1.9 K (–271.3 °C) on one of the LHC dipoles fitted with the system. At this temperature, the cold masses contract and lose up to 12 mm, taking our interferometry targets with them, meaning the targets are no longer aligned with the laser heads.” To get around the problem, a divergent, or conical, laser beam has been developed, such that the source remains “in the spotlight” despite the movements caused by contraction and expansion.</p>\n\n<p>The second problem is caused by condensation. At 1.9 K, the targets are covered by a fine layer of frost caused by the condensation of residual gases, which make them impervious to the laser beams. “Following the advice of our colleagues in the cryostat section, we decided to use the thermal radiation emitted by the vacuum vessel to heat up the targets,” explains Mateusz Sosin. “The radiation is ‘absorbed’ by an aluminium plate located under the target, keeping it at just the right temperature to avoid condensation. The plate is attached to an epoxy insulating support, which is in turn attached to the cold mass.”</p>\n\n<p>Several tests have already been carried out, including on <a href="https://home.cern/news/news/engineering/crabs-settled-tunnel">a crab cavity prototype installed in the SPS</a>, as well as on an LHC dipole. The final tests, currently in progress, look very promising, and surveyors from other laboratories, notably DESY and Fermilab, have already shown great interest.</p>\n</div>\n t \N 2019-11-15 11:30:30.956 test-con-dani \N \N \N \N \N NORMAL -34 proncero Halfway towards LHC consolidation <span>Halfway towards LHC consolidation</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Corinne Pralavorio</div>\n </div>\n <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span>\n<span>Fri, 10/18/2019 - 11:18</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The Large Hadron Collider is such a huge and sophisticated machine that the slightest alteration requires an enormous amount of work. During the second long shutdown (LS2), teams are hard at work <a href="https://home.cern/news/news/accelerators/more-spring-clean-lhc-magnets">reinforcing the electrical insulation of the accelerator’s superconducting dipole diodes</a>. The LHC contains not one, not two, but 1232 superconducting dipole magnets, each with a diode system to upgrade. That’s why no fewer than 150 people are needed to carry out the 70 000 tasks involved in this work.</p>\n\n<p>The project is now halfway to completion. One of the machine’s eight sectors, containing 154 magnets, is now closed and the final leak tests are under way. Work is ongoing in the seven other sectors and the teams are working at a rate of ten interconnections consolidated per day.</p>\n\n<p>The work is part of a broader project called DISMAC (“Diodes Insulation and Superconducting Magnets Consolidation”), which also includes the replacement of magnets and maintenance operations on the current leads, the devices that supply the LHC with electricity. Twenty-two magnets have already been replaced and two others have been removed from the machine in order to replace their beam screens, which are components located in the vacuum chamber.</p>\n\n<p>A plethora of upgrade and maintenance work is also being carried out in the tunnel on all the equipment, from the cryogenics system to the vacuum, beam instrumentation and technical infrastructures.</p>\n\n<figure><img alt="magnet,LHC,LS2,tunnel,TI2,Transfer" src="//cds.cern.ch/images/CERN-PHOTO-201906-163-1/file?size=large" /><figcaption>Replacement of one of the LHC superconducting dipole magnets during the accelerator consolidation campaign. (Image: Maximilien Brice and Julien Ordan/CERN)</figcaption></figure><hr /></div>\n t \N 2019-11-12 11:16:29.816 test-con-dani \N \N \N \N \N NORMAL -35 proncero How to build beautiful CERN websites <span>How to build beautiful CERN websites </span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Kate Kahle</div>\n </div>\n <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span>\n<span>Tue, 11/05/2019 - 14:19</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p>\n\n<p>Last year, when D8 was launched at CERN, it was accompanied by a <a href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p>\n\n<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p>\n\n<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p>\n\n<p>If you would like to join the Drupal community to find out the latest news and improvements, <a class="bulletin" href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p>\n</div>\n t \N 2019-11-12 11:16:29.864 test-con-dani \N \N \N \N \N NORMAL -36 proncero CMS measures Higgs boson’s mass with unprecedented precision <span>CMS measures Higgs boson’s mass with unprecedented precision</span>\n<span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 10/25/2019 - 10:37</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2692545" data-filename="HtoGammaGamma_v1" id="CMS-PHO-EVENTS-2019-008-4"><a href="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4" title="View on CDS">\n <img alt="Measurement of the Higgs boson mass: candidate two-photon and four-lepton events" src="//cds.cern.ch/images/CMS-PHO-EVENTS-2019-008-4/file?size=medium" /></a>\n <figcaption>\n Event in which a candidate SM Higgs boson decays into two photons indicated by the green towers representing energy deposited in the electromagnetic calorimeter.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>The <a href="https://home.cern/science/physics/higgs-boson">Higgs boson</a> is a special particle. It is the manifestation of a field that gives mass to elementary particles. But this field also gives mass to the Higgs boson itself. A precise measurement of the Higgs boson’s mass not only furthers our knowledge of physics but also sheds new light on searches planned at future colliders.</p>\n\n<p>Since discovering this unique particle in 2012, the <a href="https://home.cern/science/experiments/atlas">ATLAS</a> and <a href="https://home.cern/science/experiments/cms">CMS</a> collaborations at CERN’s <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a> have been busy determining its properties. In the <a href="https://home.cern/science/physics/standard-model">Standard Model of particle physics</a>, the Higgs boson’s mass is closely related to the strength of the particle’s interaction with itself. Comparing precise measurements of these two properties is a crucial means of testing the predictions of the Standard Model and helps search for physics beyond the predictions of this theory. In addition to probing its “self-interaction” strength, the researchers have also paid careful attention to the exact mass of the Higgs boson.</p>\n\n<p>When it was first discovered, the particle’s mass was measured to be around 125 gigaelectronvolts (GeV) but it wasn’t known with high precision. Analysis of much more data was needed before reducing the errors in such a measurement. Indeed, ATLAS and CMS have been improving this precision with their respective measurements over the years. Last year, ATLAS measured the Higgs mass to be 124.97 GeV with a precision of 0.24 GeV or 0.19%. Now, the CMS collaboration has announced the most precise measurement so far of this property: 125.35 GeV with a precision of 0.15 GeV, or 0.12%.</p>\n\n<p>Like most members of the zoo of known particles, the Higgs boson is unstable and transforms – or “decays” – nearly instantaneously into lighter particles. The mass measurement was based on two very different transformations of the Higgs boson, namely decays to four leptons via two intermediate Z bosons and decays to pairs of photons. To arrive at the mass value, the scientists combined CMS results of these two decays from two datasets: the first was recorded in 2011 and 2012 while the second came from 2016.</p>\n\n<p>This measurement adds another piece to the puzzle of the exciting world of subatomic particles.</p>\n\n<p><em>More details on the <a href="https://cms.cern/news/cms-precisely-measures-mass-higgs-boson">CMS website</a>.</em></p>\n</div>\n t \N 2019-11-12 11:16:29.877 test-con-dani \N \N \N \N \N NORMAL -37 proncero LHCf gears up to probe birth of cosmic-ray showers <span>LHCf gears up to probe birth of cosmic-ray showers</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Ana Lopes</div>\n </div>\n <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span>\n<span>Fri, 11/08/2019 - 13:48</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS">\n <img alt="One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a>\n <figcaption>\n One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p>\n\n<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p>\n\n<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p>\n\n<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p>\n\n<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p>\n\n<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p>\n\n<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p>\n\n<p> </p>\n</div>\n t \N 2019-11-12 11:16:29.818 test-con-dani \N \N \N \N \N NORMAL -39 proncero Spacewalk for AMS: Watch live with CERN and ESA <span>Spacewalk for AMS: Watch live with CERN and ESA</span>\n<span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span>\n<span>Thu, 11/14/2019 - 12:33</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>On Friday 15 November, European Space Agency (ESA) astronaut Luca Parmitano and NASA astronaut Andrew Morgan will begin the first of a series of complex spacewalks to service the <a href="https://home.cern/science/experiments/ams">Alpha Magnetic Spectrometer (AMS-02)</a>. The spacewalk will be streamed live via <a href="http://www.esa.int/ESA_Multimedia/ESA_Web_TV">ESA Web TV</a> from 12.50 p.m. CET and will include commentaries from CERN and ESA.</p>\n\n<p>This series of spacewalks is expected to be the most challenging since those to repair the <a href="https://www.nasa.gov/mission_pages/hubble/servicing/index.html">Hubble Space Telescope</a>. AMS was originally intended to run for three years, after its installation on the International Space Station in 2011, and was not designed to be maintained in orbit. However, the success of its results to date have meant that its mission has been extended.</p>\n\n<figure><iframe allowfullscreen="" frameborder="0" height="360" id="ls_embed_1573808401" scrolling="no" src="https://livestream.com/accounts/362/events/8890996/player?width=640&height=360&enableInfoAndActivity=true&defaultDrawer=&autoPlay=true&mute=false" width="640"></iframe>\n<figcaption>Watch the spacewalk live on <a href="https://livestream.com/ESA/SpacewalkforAMS">ESA Web TV</a></figcaption></figure><p>AMS-02 is a particle-physics detector that uses the unique environment of space to study the universe and its origin. It searches for antimatter and dark matter while precisely measuring cosmic-ray particles – more than 140 billion particles to date. The detector, which measures 60 cubic metres and weighs 7.5 tonnes, was assembled by an international team at CERN, and researchers, astronauts and operations teams have had to develop new procedures and more than 20 custom tools to extend the instrument’s life.</p>\n\n<p>A key task for the astronauts is to replace the AMS-02 cooling system and to fix a coolant leak, and the pair have trained extensively for this intricate operation on the ground. It will involve cutting and splicing eight cooling tubes, connecting them to the new system and reconnecting a myriad of power and data cables. It is the first time that astronauts will cut and reconnect cooling lines in orbit.</p>\n\n<p>The first AMS spacewalk on Friday is expected to last about six hours and sets the scene for at least three more. It will be streamed live on <a href="http://www.esa.int/ESA_Multimedia/ESA_Web_TV">ESA Web TV</a> and the first two hours will feature commentary from scientists at the AMS Payload Operations Control Centre (POCC) at CERN as well as astronaut and operation experts at ESA’s astronaut centre in Germany.</p>\n\n<p>CERN’s contributions will include a tour of the POCC by AMS Experiment and Operations Coordinator Mike Capell, from Massachusetts Institute of Technology (MIT). Here, AMS physicists take 24-hour shifts to operate and control the various components of AMS from the ground. Zhan Zhang, also from MIT, is the lead engineer of the Upgraded Tracker Thermal System, which is being installed during the spacewalks. She will show the laboratory at CERN where an identical spare of the system is kept in space conditions and will explain how the system works and what the astronauts will have to do to install it on the AMS detector in space. AMS scientists Mercedes Paniccia from the University of Geneva, Alberto Oliva from INFN Bologna and Andrei Kounine, from MIT, will explain the science of AMS as the spacewalk takes place and can answer your questions.</p>\n\n<p>You can already tweet questions ahead of the live broadcast to <a href="https://twitter.com/esaspaceflight">@esaspaceflight</a> or <a href="https://twitter.com/CERN">@CERN</a> using the hashtag <a href="https://twitter.com/hashtag/SpacewalkForAMS">#SpacewalkForAMS</a>.</p>\n</div>\n t \N 2019-11-15 11:21:33.553 test-con-dani \N \N \N \N \N NORMAL -38 proncero Probing dark matter using antimatter <span>Probing dark matter using antimatter</span>\n<span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span>\n<span>Tue, 11/12/2019 - 10:11</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p><a href="https://home.cern/science/physics/dark-matter">Dark matter</a> and the <a href="https://home.cern/science/physics/matter-antimatter-asymmetry-problem">imbalance between matter and antimatter</a> are two of the biggest mysteries of the universe. Astronomical observations tell us that dark matter makes up most of the matter in the cosmos but we do not know what it is made of. On the other hand, theories of the early universe predict that both antimatter and matter should have been produced in equal amounts, yet for some reason matter prevailed. Could there be a relation between this matter–antimatter asymmetry and dark matter?</p>\n\n<p>In a <a href="https://www.nature.com/articles/s41586-019-1727-9">paper</a> published today in the journal Nature, the <a href="https://home.cern/science/experiments/base">BASE </a>collaboration reports the first laboratory search for an interaction between antimatter and a dark-matter candidate, the hypothetical axion. A possible interaction would not only establish the origin of dark matter, but would also revolutionise long-established certainties about the symmetry properties of nature. Working at <a href="http://visit.cern/ad">CERN’s antimatter factory</a>, the BASE team obtained the first laboratory-based limits on the existence of dark-matter axions, assuming that they prefer to interact with antimatter rather than with matter.</p>\n\n<p>Axions were originally introduced to explain the symmetry properties of the strong force, which binds quarks into protons and neutrons, and protons and neutrons into nuclei. Their existence is also predicted by many theories beyond the <a href="https://home.cern/science/physics/standard-model">Standard Model</a>, notably superstring theories. They would be light and interact very weakly with other particles. Being stable, axions produced during the Big Bang would still be present throughout the universe, possibly accounting for observed dark matter. The so-called wave–particle duality of quantum mechanics would cause the dark-matter axion’s field to oscillate, at a frequency proportional to the axion’s mass. This oscillation would vary the intensity of this field’s interactions with matter and antimatter in the laboratory, inducing periodic variations in their properties.</p>\n\n<p>Laboratory experiments made with ordinary matter have so far shown no evidence of these oscillations, setting stringent limits on the existence of cosmic axions. The established laws of physics predict that axions interact in the same way with protons and antiprotons (the antiparticles of protons), but it is the role of experiments to challenge such wisdom, in this particular case by directly probing the existence of dark-matter axions using antiprotons.</p>\n\n<p>In their study, the BASE researchers searched for the oscillations in the rotational motion of the antiproton’s magnetic moment or “spin” – think of the wobbling motion of a spinning top just before it stops spinning; it spins around its rotational axis and “precesses” around a vertical axis. An unexpectedly large axion–antiproton interaction strength would lead to variations in the frequency of this precession.</p>\n\n<p>To look for the oscillations, the researchers first took antiprotons from CERN’s antimatter factory, the only place in the world where antiprotons are created on a daily basis. They then confined them in a device called a Penning trap to avoid their coming into contact with ordinary matter and annihilating. Next, they fed a single antiproton into a high-precision multi-Penning trap to measure and flip its spin state. By performing these measurements almost a thousand times over the course of about three months, they were able to determine a time-averaged frequency of the antiproton’s precession of around 80 megahertz with an uncertainty of 120 millihertz. By looking for regular time variations of the individual measurements over their three-month-long experimental campaign, they were able to probe any possible axion–antiproton interaction for many values of the axion mass.</p>\n\n<p>The BASE researchers were not able to detect any such variations in their measurements that would reveal a possible axion–antiproton interaction. However, the lack of this signal allowed them to put lower limits on the axion–antiproton interaction strength for a range of possible axion masses. These laboratory-based limits range from 0.1 GeV to 0.6 GeV depending on the assumed axion mass. For comparison, the most precise matter-based experiments achieve much more stringent limits, between about 10 000 and 1 000 000 GeV. This shows that today’s experimental sensitivity would require a major violation of established symmetry properties in order to reveal a possible signal.</p>\n\n<p>If axions were not a dominant component of dark matter, they could nevertheless be directly produced during the collapse and explosion of stars as supernovae, and limits on their interaction strength with protons or antiprotons could be extracted by examining the evolution of such stellar explosions. The observation of the explosion of the famous supernova SN1987A, however, set constraints on the axion–antiproton interaction strength that are about 100 000 times weaker than those obtained by BASE.</p>\n\n<p>The new measurements by the BASE collaboration, which teamed up with researchers from the Helmholtz Institute Mainz for this study, provide a novel way to probe dark matter and its possible interaction with antimatter. While relying on specific assumptions about the nature of dark matter and on the pattern of the matter–antimatter asymmetry, the experiment’s results are a unique probe of unexpected new phenomena, which could unveil extraordinary modifications to our established understanding of how the universe works.</p>\n</div>\n t \N 2019-11-15 11:21:33.555 test-con-dani \N \N \N \N \N NORMAL -40 proncero ALICE: the journey of a cosmopolitan detector <span>ALICE: the journey of a cosmopolitan detector</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Camille Monnin</div>\n </div>\n <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span>\n<span>Thu, 10/31/2019 - 10:04</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p>\n\n<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p>\n\n<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p>\n\n<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p>\n\n<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p>\n\n<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p>\n</div>\n t \N 2019-11-15 11:21:33.623 test-con-dani \N \N \N \N \N NORMAL -42 proncero How to build beautiful CERN websites <span>How to build beautiful CERN websites </span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Kate Kahle</div>\n </div>\n <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span>\n<span>Tue, 11/05/2019 - 14:19</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a class="bulletin" href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p>\n\n<p>Last year, when D8 was launched at CERN, it was accompanied by a <a class="bulletin" href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a class="bulletin" href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p>\n\n<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p>\n\n<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p>\n\n<p>If you would like to join the Drupal community to find out the latest news and improvements, <a class="bulletin" href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p>\n</div>\n t \N 2019-11-15 11:21:33.623 test-con-dani \N \N \N \N \N NORMAL -41 proncero LS2 Report: LHCb looks to the future with SciFi detector <span>LS2 Report: LHCb looks to the future with SciFi detector</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Achintya Rao</div>\n </div>\n <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Tue, 11/12/2019 - 08:53</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2701306" data-filename="201911-373_04" id="CERN-PHOTO-201911-373-4"><a href="//cds.cern.ch/images/CERN-PHOTO-201911-373-4" title="View on CDS">\n <img alt="LHCb's new scintillating-fibre (SciFi) tracker" src="//cds.cern.ch/images/CERN-PHOTO-201911-373-4/file?size=medium" /></a>\n <figcaption>\n The new tracker is made of over 10,000 kilometres of polystyrene-based scintillating fibres and will help LHCb record data at a higher luminosity and rate from Run 3 onwards\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the <a href="https://home.cern/science/experiments/lhcb">LHCb detector</a> at the <a href="https://home.cern/science/accelerators/large-hadron-collider">Large Hadron Collider</a>, the ongoing <a href="https://home.cern/tags/long-shutdown-2">second long shutdown (LS2)</a> of CERN’s accelerator complex will be a period of metamorphosis. After two successful data-collection runs, the detector is being upgraded to improve the precision of its physics measurements, many of which are the best in the world. There will therefore be five times more collisions every time proton bunches cross within the detector after LS2 and the LHCb collaboration plans on increasing the data-readout rate from 1 MHz to the LHC’s maximum interaction frequency of 40 MHz (or every 25 nanoseconds).</p>\n\n<p>In addition to replacing nearly all of the electronics and data-acquisition systems to handle the enormous increase in data production, LHCb is replacing its tracking detectors with new ones, such as the scintillating-fibre tracker, or SciFi. It is the first time such a large tracker, with a small granularity and high spatial resolution, has been made using this technology. The SciFi will be placed behind the dipole magnet of LHCb.</p>\n\n<p>Scintillating fibres, as the name suggests, are optical fibres – with a polystyrene base, in this case – that emit tens of photons in the blue-green wavelength when a particle interacts with them. Secondary scintillator dyes have been added to the polystyrene to amplify the light and shift it to longer wavelengths so it can reach custom-made silicon photomultipliers (SiPM) that convert optical light to electrical signals. The technology has been well tested at other high-energy-physics experiments. The fibres themselves are lightweight, they can produce and transmit light within the 25-nanosecond window and they are suitably tolerant to the ionising radiation expected in the future.</p>\n\n<p>Each scintillating fibre making up the sub-detector is 0.25 mm in diameter and nearly 2.5 m in length. The fibres will be packed into modules that will reside in three stations within LHCb, each made of four so-called “detection planes”, with the photomultipliers located at the top and bottom of each plane. “The fibres have been painstakingly examined, wound into multi-layer ribbons, assembled into detector modules and thoroughly tested,” explains Blake Leverington, who is coordinating part of the SciFi project for LHCb. “The fibres provide a single-hit precision better than 100 microns and the single-hit efficiency over the area of the detector is better than 99%.” In total, over 10 000 km of precision-made scintillating fibres will adorn LHCb.</p>\n\n<p>Unlike the other LHC detectors, LHCb is asymmetric in design and studies particles that fly very close to the beam pipe after being produced in proton–proton collisions. However, operating a sensitive detector this close to the beam pipe brings its own problems. Simulations show that radiation damage from collision debris would darken the fibres closest to the beam pipe by up to 40% over the lifetime of LHCb. This would make it harder for the produced light to be transmitted through the fibres, but the detector is expected to remain efficient despite this.</p>\n\n<p>The photomultipliers located at the top and bottom of each SciFi detection plane will be bombarded by neutrons produced in the calorimeters that sit further downstream. The radiation damage results in so-called “dark noise”, where thermally excited electrons cause the SiPMs to produce a signal that mimics the signal coming from individual photons. In addition to shielding placed between the SciFi and the calorimeters, a complex cooling system has been developed to chill the SiPMs. “Measurements have shown that the rate of dark noise can be reduced by a factor of two for every 10 °C drop in temperature,” points out Leverington. The SiPMs have been mounted on special 3D-printed titanium cold-bars that are cooled to −40 °C.</p>\n\n<p>“The project has had contributions from more than a hundred scientists, students, engineers and technicians from 17 partner institutes in 10 countries,” says Leverington. “We have worked together for seven years to bring SciFi to life.” Currently, the SciFi modules, services and electronics are being assembled and installed in the 12 mechanical frames in the assembly hall at the LHCb site at Point 8 of the LHC ring. The first SciFi components are planned to be installed in spring next year.</p>\n</div>\n t \N 2019-11-15 11:21:33.591 test-con-dani \N \N \N \N \N NORMAL -43 proncero Around the LHC in 252 days <span>Around the LHC in 252 days </span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Corinne Pralavorio</div>\n </div>\n <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span>\n<span>Tue, 11/12/2019 - 14:26</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the teams involved in the <a href="https://home.cern/news/news/accelerators/ls2-report-insulation-lhc-diodes-has-begun">DISMAC (Diode Insulation and Superconducting Magnets Consolidation)</a> project, the LHC tour is a long adventure. On 7 November, they opened the last and 1360th LHC magnet interconnection, 252 days after having opened the first. The electrical insulation work of the magnets’ diodes is done in sequence: opening of the interconnection, cleaning, installation of the insulation, electrical and quality tests, welding, and so on. The teams work sequentially, and the diode insulation is scheduled to be completed next summer.</p>\n</div>\n t \N 2019-11-15 11:21:33.572 test-con-dani \N \N \N \N \N NORMAL -44 proncero Be seen, be safe <span>Be seen, be safe</span>\n<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 11/05/2019 - 12:27</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a>\n<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p>\n\n<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p>\n</div>\n t \N 2019-11-15 11:21:33.643 test-con-dani \N \N \N \N \N NORMAL -45 proncero Beamline for Schools 2019 participants present results <span>Beamline for Schools 2019 participants present results</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Joseph Piergrossi</div>\n </div>\n <span><span lang="" about="https://home.cern/user/34" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">achintya</span></span>\n<span>Fri, 11/08/2019 - 13:58</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2698994" data-filename="H61A9329" id="OPEN-PHO-MISC-2019-016-4"><a href="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4" title="View on CDS">\n <img alt="Beamline for Schools 2019" src="//cds.cern.ch/images/OPEN-PHO-MISC-2019-016-4/file?size=medium" /></a>\n <figcaption>\n The two winning teams from the 2019 Beamline for Schools competition – DESY Chain from Salt Lake City, Utah, USA and Particle Peers from Groningen, Netherlands – work on their projects at DESY Hamburg.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Monday, 28 October, marked the completion of data collection for the 2019 <a href="https://beamlineforschools.cern/">Beamline for Schools (BL4S)</a> winning teams on the Hamburg campus of the German physics research centre <a href="http://www.desy.de/index_eng.html">DESY</a>. Two teams – from Salt Lake City, Utah, in the USA and Groningen in the Netherlands – won the CERN-organised international competition, wherein high-school students propose their own particle physics experiments and perform them if they win.</p>\n\n<p>The teams <a href="https://home.cern/news/press-release/cern/dutch-and-us-students-win-2019-cern-beamline-schools-competition">“DESY Chain” from the USA and “Particle Peers” from the Netherlands</a> also presented their preliminary results last Monday. DESY Chain experimented with scintillator sensitivity using electrons and positrons. “In our data, we’re definitely seeing interesting energy losses in the scintillators,” says Charles Bonkowsky, a member of the DESY Chain team. “It’s going to take a little bit of time to put it all together and see what the energy loss is, and see how it corresponds to the rest of the data.”</p>\n\n<p>Particle Peers investigated differences in particle showers between matter and antimatter. “We didn’t expect to have such big datasets, and so many different datasets,” said Isabelle Koster from Particle Peers. “That was a real bonus. We did everything we wanted to do. And we made so many friends along the way!”</p>\n\n<p>The two teams collaborated closely during their experiment runs, sharing materials and data-processing techniques. Both teams aim to publish their results.</p>\n\n<p>“Knowing how you can come from thinking about an experiment to actually performing it – what detectors to use, what kind of set-up to have – was really helpful,” says Frederiek de Bruine from Particle Peers.</p>\n\n<p>“We have all this data we have to process, but it’s sad that our data-collection journey at DESY has come to an end,” says Derek Che from DESY Chain. “It was an amazing experience. I made new friends and experienced things that will definitely shape my future.”</p>\n\n<p>The two Beamline for Schools winning teams had been selected from 178 entries, and the organisers are hoping for an even stronger showing for next year. Although the DESY and CERN scientists and staff who supported the students are sad to see them go home, they are now gearing up for next year’s competition. In 2020, CERN will once again invite DESY-Hamburg to host two of the winning teams, and discussions are under way to invite a third winning team to a different laboratory in Europe.</p>\n\n<p>Want to join? Preregistration for BL4S 2020 is <a class="bulletin" href="https://beamlineforschools.cern/bl4s-competition/how-take-part">just a click away</a>.</p>\n\n<hr /><p>More photos <a class="bulletin" href="https://cds.cern.ch/record/2698994">on CDS</a></p>\n\n<p><iframe allowfullscreen="" frameborder="0" height="360" scrolling="no" src="https://cds.cern.ch/images/OPEN-PHO-MISC-2019-016/export?format=sspp&ln=en&captions=true" width="480"></iframe></p>\n</div>\n t \N 2019-11-15 11:21:33.572 test-con-dani \N \N \N \N \N NORMAL -46 proncero Aligning the HL-LHC magnets with interferometry <span>Aligning the HL-LHC magnets with interferometry</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Anaïs Schaeffer</div>\n </div>\n <span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 11/12/2019 - 09:35</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>CERN surveyors have just finalised a system that can determine, in real time, the position of certain components inside the (sealed) cryostats of the future <a href="https://home.cern/science/accelerators/high-luminosity-lhc">High-Luminosity LHC</a> (HL-LHC). Currently, only the position of the cryostats themselves can be measured, using sensors that perform continuous measurements. “This new system has been specially developed for the HL-LHC, to be able directly to determine the position of cold masses at the level of the inner triplets, located on either side of the ATLAS and CMS experiments, and the position of the crab cavities inside their cryostat,” says Hélène Mainaud Durand, in charge of alignment in the High-Luminosity LHC upgrade. “It will be a real plus to be able to monitor the alignment of these components continuously, especially during the accelerator’s cycles of heating and cooling.”</p>\n\n<p>The new procedure is based on frequency sweeping interferometry (FSI), a distance-measurement method that simultaneously performs several absolute distance measurements between a measuring head and targets, and relates them to a common benchmark measurement. “Thanks to this technique, it will be possible to deduce the position of the cold mass to within a few micrometres relative to the cryostat by making 12 distance measurements between the cryostat and the cold mass,” says Mainaud Durand. Each cold mass will therefore be equipped with 12 targets, which are reflective glass spheres that have been specially designed for this procedure. Opposite the targets are 12 laser heads, which are attached to the cryostat and connected by optical fibres to a laser acquisition system.</p>\n\n<p>Even though FSI is commonly used in metrology, adapting it for use in a cryogenic environment has not been completely straightforward: “We have had to overcome several challenges posed by the extreme conditions inside the accelerators,” says Mateusz Sosin, the mechatronic engineer in charge of this development. “The first problem became apparent during a test carried out at the cryogenic temperature of 1.9 K (–271.3 °C) on one of the LHC dipoles fitted with the system. At this temperature, the cold masses contract and lose up to 12 mm, taking our interferometry targets with them, meaning the targets are no longer aligned with the laser heads.” To get around the problem, a divergent, or conical, laser beam has been developed, such that the source remains “in the spotlight” despite the movements caused by contraction and expansion.</p>\n\n<p>The second problem is caused by condensation. At 1.9 K, the targets are covered by a fine layer of frost caused by the condensation of residual gases, which make them impervious to the laser beams. “Following the advice of our colleagues in the cryostat section, we decided to use the thermal radiation emitted by the vacuum vessel to heat up the targets,” explains Mateusz Sosin. “The radiation is ‘absorbed’ by an aluminium plate located under the target, keeping it at just the right temperature to avoid condensation. The plate is attached to an epoxy insulating support, which is in turn attached to the cold mass.”</p>\n\n<p>Several tests have already been carried out, including on <a href="https://home.cern/news/news/engineering/crabs-settled-tunnel">a crab cavity prototype installed in the SPS</a>, as well as on an LHC dipole. The final tests, currently in progress, look very promising, and surveyors from other laboratories, notably DESY and Fermilab, have already shown great interest.</p>\n</div>\n t \N 2019-11-15 11:21:33.59 test-con-dani \N \N \N \N \N NORMAL -52 proncero Around the LHC in 252 days <span>Around the LHC in 252 days </span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Corinne Pralavorio</div>\n </div>\n <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span>\n<span>Tue, 11/12/2019 - 14:26</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the teams involved in the <a href="https://home.cern/news/news/accelerators/ls2-report-insulation-lhc-diodes-has-begun">DISMAC (Diode Insulation and Superconducting Magnets Consolidation)</a> project, the LHC tour is a long adventure. On 7 November, they opened the last and 1360th LHC magnet interconnection, 252 days after having opened the first. The electrical insulation work of the magnets’ diodes is done in sequence: opening of the interconnection, cleaning, installation of the insulation, electrical and quality tests, welding, and so on. The teams work sequentially, and the diode insulation is scheduled to be completed next summer.</p>\n</div>\n t \N 2019-11-15 11:30:30.966 test-con-dani \N \N \N \N \N NORMAL -53 proncero LHCf gears up to probe birth of cosmic-ray showers <span>LHCf gears up to probe birth of cosmic-ray showers</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Ana Lopes</div>\n </div>\n <span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span>\n<span>Fri, 11/08/2019 - 13:48</span>\n\n <div class="field field--name-field-p-news-display-list-cds field--type-cerncdsmedia field--label-hidden field--item"><figure class="cds-image" data-record-id="2699736" data-filename="LHCf_Arm2_during_installation_02%20copy%202" id="CERN-HOMEWEB-PHO-2019-131-1"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1" title="View on CDS">\n <img alt="One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe." src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-131-1/file?size=medium" /></a>\n <figcaption>\n One of the LHCf experiment's two detectors, LHCf Arm2, seen here during installation into a particle absorber that surrounds the LHC's beam pipe.\n <span> (Image: CERN)</span>\n </figcaption></figure></div>\n \n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Cosmic rays are particles from outer space, typically protons, travelling at almost the speed of light. When the most energetic of these particles strike the atmosphere of our planet, they interact with atomic nuclei in the atmosphere and produce cascades of secondary particles that shower down to the Earth’s surface. These extensive air showers, as they are known, are similar to the cascades of particles that are created in collisions inside particle colliders such as CERN’s Large Hadron Collider (LHC). In the next LHC, run starting in 2021, the smallest of the LHC experiments – the <a href="https://home.cern/science/experiments/lhcf">LHCf experiment</a> – is set to probe the first interaction that triggers these cosmic showers.</p>\n\n<p>Observations of extensive air showers are generally interpreted using computer simulations that involve a model of how cosmic rays interact with atomic nuclei in the atmosphere. But different models exist and it’s unclear which one is the most appropriate. The LHCf experiment is in an ideal position to test these models and help shed light on cosmic-ray interactions.</p>\n\n<p>In contrast to the main LHC experiments, which measure particles emitted at large angles from the collision line, the LHCf experiment measures particles that fly out in the “forward” direction, that is, at small angles from the collision line. These particles, which carry a large portion of the collision energy, can be used to probe the small angles and high energies at which the predictions from the different models don’t match.</p>\n\n<p>Using data from proton–proton LHC collisions at an energy of 13 TeV, LHCf has recently measured how the number of forward <a href="https://www.sciencedirect.com/science/article/pii/S0370269317310365?via%3Dihub">photons</a> and <a href="https://link.springer.com/article/10.1007%2FJHEP11%282018%29073">neutrons</a> varies with particle energy at previously unexplored high energies. These measurements agree better with some models than others, and they are being factored in by modellers of extensive air showers.</p>\n\n<p>In the next LHC run, LHCf should extend the range of particle energies probed, due to the planned higher collision energy. In addition, and thanks to ongoing upgrade work, the experiment should also increase the number and type of particles that are detected and studied.</p>\n\n<p>What’s more, the experiment plans to measure forward particles emitted from collisions of protons with light ions, most likely oxygen ions. The first interactions that trigger extensive air showers in the atmosphere involve mainly light atomic nuclei such as oxygen and nitrogen. LHCf could therefore probe such an interaction in the next run, casting new light on cosmic-ray interaction models at high energies.</p>\n\n<p>Find out more in the <a href="https://ep-news.web.cern.ch/content/lhcf-sheds-light-hadronic-interaction-models">Experimental Physics newsletter article</a>.</p>\n\n<p> </p>\n</div>\n t \N 2019-11-15 11:30:30.967 test-con-dani \N \N \N \N \N NORMAL -54 proncero How to build beautiful CERN websites <span>How to build beautiful CERN websites </span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Kate Kahle</div>\n </div>\n <span><span lang="" about="https://home.cern/user/40" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">katebrad</span></span>\n<span>Tue, 11/05/2019 - 14:19</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>One year on from<a href="https://home.cern/news/news/cern/welcome-new-cern-website"> launching</a> the new home.cern website, the CERN online landscape has begun to change. Now, more than 600 websites are in production or development using the main open-source content management system supported at CERN: Drupal 8 (D8). Some of these websites have been highlighted in a <a class="bulletin" href="https://drupal-showcase.web.cern.ch/">new Drupal showcase website</a> to give examples of what is possible with the new CERN D8 theme.</p>\n\n<p>Last year, when D8 was launched at CERN, it was accompanied by a <a class="bulletin" href="https://webtools.web.cern.ch/">webtools website</a> to help guide new users. The webtools took on board user feedback and requirements from the last six years of using Drupal 7 at CERN, and continue to be regularly enhanced and improved. Alongside the <a href="https://lms.cern.ch/ekp/servlet/ekp?TX=UNIVERSALSEARCH&INIT=N&ACTION=SEARCH&KEYW=drupal&universal-search-advanced-selector-dropdown=0&SEARCH=">Drupal 8 CERN training courses</a>, these webtools help those embarking on new websites, or migrating their existing websites to Drupal 8. In addition, a <a class="bulletin" href="https://easy-start.web.cern.ch/">new easy-start template</a> is now available to help those unfamiliar with the technology to enter content into a pre-existing template. When <a href="https://webservices.web.cern.ch/webservices/Services/CreateNewSite/Default.aspx">creating a new CERN website</a>, there is now the choice of the easy-start, demo or blank Drupal 8 templates.</p>\n\n<p>By mid-2020, Drupal 7 will no longer be supported at CERN, so website owners will either need to move their websites to Drupal 8 or explore alternatives. To help them with this task, each Drupal 7 website owner was contacted earlier this year with proposals of either moving to Drupal 8 or to alternative technologies.</p>\n\n<p>For those remaining on Drupal, the <a href="https://drupal-community.web.cern.ch/">Drupal community</a>, supported by the IR web team and IT Drupal infrastructure team, uses an online forum and face-to-face meetings every two weeks to help answer queries, alongside twice-yearly official meetings.</p>\n\n<p>If you would like to join the Drupal community to find out the latest news and improvements, <a class="bulletin" href="https://e-groups.cern.ch/e-groups/EgroupsSubscription.do?egroupName=drupal-community">subscribe here</a>.</p>\n</div>\n t \N 2019-11-15 11:30:30.971 test-con-dani \N \N \N \N \N NORMAL -55 proncero Probing dark matter using antimatter <span>Probing dark matter using antimatter</span>\n<span><span lang="" about="https://home.cern/user/159" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">abelchio</span></span>\n<span>Tue, 11/12/2019 - 10:11</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p><a href="https://home.cern/science/physics/dark-matter">Dark matter</a> and the <a href="https://home.cern/science/physics/matter-antimatter-asymmetry-problem">imbalance between matter and antimatter</a> are two of the biggest mysteries of the universe. Astronomical observations tell us that dark matter makes up most of the matter in the cosmos but we do not know what it is made of. On the other hand, theories of the early universe predict that both antimatter and matter should have been produced in equal amounts, yet for some reason matter prevailed. Could there be a relation between this matter–antimatter asymmetry and dark matter?</p>\n\n<p>In a <a href="https://www.nature.com/articles/s41586-019-1727-9">paper</a> published today in the journal Nature, the <a href="https://home.cern/science/experiments/base">BASE </a>collaboration reports the first laboratory search for an interaction between antimatter and a dark-matter candidate, the hypothetical axion. A possible interaction would not only establish the origin of dark matter, but would also revolutionise long-established certainties about the symmetry properties of nature. Working at <a href="http://visit.cern/ad">CERN’s antimatter factory</a>, the BASE team obtained the first laboratory-based limits on the existence of dark-matter axions, assuming that they prefer to interact with antimatter rather than with matter.</p>\n\n<p>Axions were originally introduced to explain the symmetry properties of the strong force, which binds quarks into protons and neutrons, and protons and neutrons into nuclei. Their existence is also predicted by many theories beyond the <a href="https://home.cern/science/physics/standard-model">Standard Model</a>, notably superstring theories. They would be light and interact very weakly with other particles. Being stable, axions produced during the Big Bang would still be present throughout the universe, possibly accounting for observed dark matter. The so-called wave–particle duality of quantum mechanics would cause the dark-matter axion’s field to oscillate, at a frequency proportional to the axion’s mass. This oscillation would vary the intensity of this field’s interactions with matter and antimatter in the laboratory, inducing periodic variations in their properties.</p>\n\n<p>Laboratory experiments made with ordinary matter have so far shown no evidence of these oscillations, setting stringent limits on the existence of cosmic axions. The established laws of physics predict that axions interact in the same way with protons and antiprotons (the antiparticles of protons), but it is the role of experiments to challenge such wisdom, in this particular case by directly probing the existence of dark-matter axions using antiprotons.</p>\n\n<p>In their study, the BASE researchers searched for the oscillations in the rotational motion of the antiproton’s magnetic moment or “spin” – think of the wobbling motion of a spinning top just before it stops spinning; it spins around its rotational axis and “precesses” around a vertical axis. An unexpectedly large axion–antiproton interaction strength would lead to variations in the frequency of this precession.</p>\n\n<p>To look for the oscillations, the researchers first took antiprotons from CERN’s antimatter factory, the only place in the world where antiprotons are created on a daily basis. They then confined them in a device called a Penning trap to avoid their coming into contact with ordinary matter and annihilating. Next, they fed a single antiproton into a high-precision multi-Penning trap to measure and flip its spin state. By performing these measurements almost a thousand times over the course of about three months, they were able to determine a time-averaged frequency of the antiproton’s precession of around 80 megahertz with an uncertainty of 120 millihertz. By looking for regular time variations of the individual measurements over their three-month-long experimental campaign, they were able to probe any possible axion–antiproton interaction for many values of the axion mass.</p>\n\n<p>The BASE researchers were not able to detect any such variations in their measurements that would reveal a possible axion–antiproton interaction. However, the lack of this signal allowed them to put lower limits on the axion–antiproton interaction strength for a range of possible axion masses. These laboratory-based limits range from 0.1 GeV to 0.6 GeV depending on the assumed axion mass. For comparison, the most precise matter-based experiments achieve much more stringent limits, between about 10 000 and 1 000 000 GeV. This shows that today’s experimental sensitivity would require a major violation of established symmetry properties in order to reveal a possible signal.</p>\n\n<p>If axions were not a dominant component of dark matter, they could nevertheless be directly produced during the collapse and explosion of stars as supernovae, and limits on their interaction strength with protons or antiprotons could be extracted by examining the evolution of such stellar explosions. The observation of the explosion of the famous supernova SN1987A, however, set constraints on the axion–antiproton interaction strength that are about 100 000 times weaker than those obtained by BASE.</p>\n\n<p>The new measurements by the BASE collaboration, which teamed up with researchers from the Helmholtz Institute Mainz for this study, provide a novel way to probe dark matter and its possible interaction with antimatter. While relying on specific assumptions about the nature of dark matter and on the pattern of the matter–antimatter asymmetry, the experiment’s results are a unique probe of unexpected new phenomena, which could unveil extraordinary modifications to our established understanding of how the universe works.</p>\n</div>\n t \N 2019-11-15 11:30:30.971 test-con-dani \N \N \N \N \N NORMAL -56 proncero ALICE: the journey of a cosmopolitan detector <span>ALICE: the journey of a cosmopolitan detector</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Camille Monnin</div>\n </div>\n <span><span lang="" about="https://home.cern/user/7476" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">camonnin</span></span>\n<span>Thu, 10/31/2019 - 10:04</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>Passengers aboard United flights 577 and 956 from San Francisco to Geneva, via Newark, were in for a surprise when they discovered their discreet, yet unusual, travel companion: one of the airplane seats was occupied not by a human, but by a piece of a detector. Since it was too fragile to be placed in the hold, the part had its own passenger seat, next to that of its guardian angel, a researcher at the Lawrence Berkeley National Laboratory (LBNL). The part is <a href="https://newscenter.lbl.gov/2019/09/19/how-to-get-a-particle-detector-on-a-plane/">one of the pieces</a> of the ALICE experiment’s new inner detector that have made their way across the globe to reach CERN. Thirty-five institutes from all over the world are involved in the construction, testing and prototyping of the various parts of the new detector called ALICE’s <a href="https://ep-news.web.cern.ch/content/alice-its-upgrade-pixels-quarks">Inner Tracking System</a>. </p>\n\n<p>ALICE (A Large Ion Collider Experiment) is one of the four main experiments at the Large Hadron Collider (LHC). The experiment studies matter as it was just after the Big Bang, when the components of atomic nuclei were not bound together. </p>\n\n<p>With the increase in instantaneous luminosity of heavy-ion collisions planned for the CERN accelerators’ third run, the ALICE detector will boost its read-out rate. This increase in the read-out rate, combined with an online data reconstruction system, means that ALICE will be able to collect 100 times more events than before. </p>\n\n<p>In order to achieve the <a href="https://cerncourier.com/a/alice-revitalised/">desired physics goals</a>, numerous upgrades are being carried out during the current Long Shutdown. One of the worksites concerns the Inner Tracking System, which surrounds the beam pipe. This detector reconstructs the tracks of charged particles and its measurement precision is crucial for physics analyses. The upgrade will therefore result in improved precision, especially in the detection of short-lived particles. </p>\n\n<p>The current inner tracker will be replaced by a system of seven all-pixel cylindrical layers. The previous system had six layers, of which only the two innermost layers were made up of pixels, while the four external layers were composed of silicon sensors with a much lower granularity. The new Inner Tracking System will be composed of 12.5 billion pixels installed on an area of around 10 m<sup>2</sup>.<sup> </sup>These pixels have been specifically developed to cope with a higher collision rate and to reach a fine granularity. The chips thus incorporate both the pixel sensor and the read-out system, enabling the mass of the detector to be reduced by a factor of four compared with its predecessor. Reducing the mass allows for improved precision and efficiency when reconstructing particle trajectories. </p>\n\n<p>The construction of all the mechanical structures was completed last year. The various pieces of the detector have arrived at CERN, and the CERN teams are now starting to assemble them in two half-barrel structures. The fact that the detector components were available quickly has made it possible to begin the commissioning process. The final installation of the detector in the experimental cavern is planned for next summer. </p>\n</div>\n t \N 2019-11-15 11:30:30.975 test-con-dani \N \N \N \N \N NORMAL -57 proncero Be seen, be safe <span>Be seen, be safe</span>\n<span><span lang="" about="https://home.cern/user/151" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">anschaef</span></span>\n<span>Tue, 11/05/2019 - 12:27</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>For the second year running, the HSE unit will be distributing reflective tags for CERN personnel to attach to their clothing or bags in order to help them, or their family members, to be visible and therefore safer on the streets this winter.</p>\n\n<figure class="cds-image" id="CERN-HOMEWEB-PHO-2019-129-2"><a href="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2" title="View on CDS"><img alt="home.cern" src="//cds.cern.ch/images/CERN-HOMEWEB-PHO-2019-129-2/file?size=large" /></a>\n<figcaption><span>(Image: CERN)</span></figcaption></figure><p>They may be small, but these tags make a real difference to how easy it is for pedestrians to be seen by motorists – take a look at the short film that will be running on the information screens in the restaurants over the next few weeks.</p>\n\n<p>Some of you may remember last year’s distribution. This year’s tags are similar, but we’ve customised them a little. Come along to find out how, and to collect your free reflectors, at Restaurants 1, 2 and 3 at lunchtime on 14 November.</p>\n</div>\n t \N 2019-11-15 11:30:30.975 test-con-dani \N \N \N \N \N NORMAL -58 bsilvade Password of account "Push Service Mailbox (push)" will expire in 5 day(s) Version francaise en fin de ce message\nPassword Expiration\nDear Push Service Mailbox,\n\nThe password of the account "Push Service Mailbox (push)" will expire in 5 day(s).\nActions Required\n\n * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * Access to the central services such as Mail, test Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password.\n\nGet Help\n\n * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch)\n * Note: Please do not reply to this message which is generated by a robot, you will not get any answer.\n\nBest regards,\nCERN IT Department.\n\nExpiration du mot de passe\nCher/Chère Push Service Mailbox,\n\nLe mot de passe du compte "Push Service Mailbox (push)" va expirer dans 5 jour(s).\nActions requises\n\n * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * L'accès aux services centraux comme le Mail, les services testistratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe.\n\nObtenir de l'aide\n\n * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>)\n * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n' obtiendrez pas de réponse.\n\nCordialement,\nCERN Département IT\n t \N 2019-11-17 00:00:55.625 \N \N \N \N \N \N NORMAL -59 push Password of account "Push Service Mailbox (push)" will expire in 5 day(s) Version francaise en fin de ce message\nPassword Expiration\nDear Push Service Mailbox,\n\nThe password of the account "Push Service Mailbox (push)" will expire in 5 day(s).\nActions Required\n\n * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * Access to the central services such as Mail, test Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password.\n\nGet Help\n\n * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch)\n * Note: Please do not reply to this message which is generated by a robot, you will not get any answer.\n\nBest regards,\nCERN IT Department.\n\nExpiration du mot de passe\nCher/Chère Push Service Mailbox,\n\nLe mot de passe du compte "Push Service Mailbox (push)" va expirer dans 5 jour(s).\nActions requises\n\n * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * L'accès aux services centraux comme le Mail, les services testistratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe.\n\nObtenir de l'aide\n\n * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>)\n * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n' obtiendrez pas de réponse.\n\nCordialement,\nCERN Département IT\n t \N 2019-11-17 00:00:55.625 \N \N \N \N \N \N NORMAL -61 push Password of account "Push Service Mailbox (push)" will expire in 3 day(s) Version francaise en fin de ce message\nPassword Expiration\nDear Push Service Mailbox,\n\nThe password of the account "Push Service Mailbox (push)" will expire in 3 day(s).\nActions Required\n\n * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * Access to the central services such as Mail, test Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password.\n\nGet Help\n\n * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch)\n * Note: Please do not reply to this message which is generated by a robot, you will not get any answer.\n\nBest regards,\nCERN IT Department.\n\nExpiration du mot de passe\nCher/Chère Push Service Mailbox,\n\nLe mot de passe du compte "Push Service Mailbox (push)" va expirer dans 3 jour(s).\nActions requises\n\n * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * L'accès aux services centraux comme le Mail, les services testistratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe.\n\nObtenir de l'aide\n\n * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>)\n * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n' obtiendrez pas de réponse.\n\nCordialement,\nCERN Département IT\n t \N 2019-11-19 00:00:40.917 \N \N \N \N \N \N NORMAL -62 bsilvade Password of account "Push Service Mailbox (push)" will expire in 1 day(s) Version francaise en fin de ce message\nPassword Expiration\nDear Push Service Mailbox,\n\nThe password of the account "Push Service Mailbox (push)" will expire in 1 day(s).\nActions Required\n\n * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * Access to the central services such as Mail, test Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password.\n\nGet Help\n\n * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch)\n * Note: Please do not reply to this message which is generated by a robot, you will not get any answer.\n\nBest regards,\nCERN IT Department.\n\nExpiration du mot de passe\nCher/Chère Push Service Mailbox,\n\nLe mot de passe du compte "Push Service Mailbox (push)" va expirer dans 1 jour(s).\nActions requises\n\n * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * L'accès aux services centraux comme le Mail, les services testistratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe.\n\nObtenir de l'aide\n\n * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>)\n * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n' obtiendrez pas de réponse.\n\nCordialement,\nCERN Département IT\n t \N 2019-11-21 00:00:39.458 \N \N \N \N \N \N NORMAL -63 push Password of account "Push Service Mailbox (push)" will expire in 1 day(s) Version francaise en fin de ce message\nPassword Expiration\nDear Push Service Mailbox,\n\nThe password of the account "Push Service Mailbox (push)" will expire in 1 day(s).\nActions Required\n\n * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * Access to the central services such as Mail, test Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password.\n\nGet Help\n\n * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch)\n * Note: Please do not reply to this message which is generated by a robot, you will not get any answer.\n\nBest regards,\nCERN IT Department.\n\nExpiration du mot de passe\nCher/Chère Push Service Mailbox,\n\nLe mot de passe du compte "Push Service Mailbox (push)" va expirer dans 1 jour(s).\nActions requises\n\n * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * L'accès aux services centraux comme le Mail, les services testistratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe.\n\nObtenir de l'aide\n\n * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>)\n * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n' obtiendrez pas de réponse.\n\nCordialement,\nCERN Département IT\n t \N 2019-11-21 00:00:39.46 \N \N \N \N \N \N NORMAL -64 proncero LS2 report: The PS is rejuvenated for its 60th birthday <span>LS2 report: The PS is rejuvenated for its 60th birthday</span>\n\n <div class="field field--name-field-p-news-display-byline field--type-entity-reference field--label-hidden field--items">\n <div class="field--item">Corinne Pralavorio</div>\n </div>\n <span><span lang="" about="https://home.cern/user/146" typeof="schema:Person" property="schema:name" datatype="" xml:lang="">cmenard</span></span>\n<span>Mon, 11/25/2019 - 15:36</span>\n\n <div class="field field--name-field-p-news-display-body field--type-text-long field--label-hidden field--item"><p>On 24 November 1959, the Proton Synchotron (PS) accelerated its first beams, making it the most powerful accelerator in the world at the time. Who would have thought that 60 years later, this machine would still be one of the main cogs in the CERN accelerator complex? Incredibly, the PS is still in service. It will even be made more efficient with a bit of tender loving care during this second long shutdown. The <a href="https://home.cern/fr/news/opinion/accelerators/time-lhc-injectors-upgrade-project">LHC Injectors Upgrade (LIU) project</a> includes a long list of <a href="https://home.cern/fr/news/news/accelerators/ls2-report-proton-synchrotrons-magnets-prepare-higher-energies">work to be carried out on the accelerator and its entire infrastructure</a>.</p>\n\n<p>With the first link in the chain of accelerators being replaced by <a href="https://home.cern/fr/news/news/accelerators/brand-new-linear-accelerator-cern">Linac 4</a>, protons will be injected into the PS Booster at 160 MeV, and then accelerated to 2 GeV (up from 1.4 GeV previously) before being sent to the PS. This is why the PS proton injection line, which is about 20 metres in length, will be entirely replaced. To date, the quadrupole magnets have been installed together with a septum magnet. The equipment will continue to be installed in 2020. The power converters which power the injection line, as well as other LIU equipment, have been replaced and installed in renovated buildings. The cabling is now underway.</p>\n\n<p>In the 628-metre-long accelerator, half of the main magnets are being renovated. This major project, which entails lengthy handling operations, will soon be finished. “48 of the 100 magnets have been removed and a vast majority have already been reinstalled”, explains Fernando Pedrosa. New equipment such as <a href="https://home.cern/fr/news/news/accelerators/keeping-close-watch-over-beams">beam wire scanners</a> and internal beam dumps will also be installed in the ring. The teams have used the upgrade works as an opportunity to give the accelerator a deep clean, including the cleaning of certain galleries. The cleaning work, as well as the <a href="https://home.cern/fr/news/news/accelerators/ls2-report-linac4-knocking-door-ps-booster">ongoing Linac 4 tests</a>, require part of the PS to be closed making the work more complex to coordinate. Downstream, the extraction line towards the East Area has been entirely dismantled ahead of the new installation in 2020, as part of the <a href="https://home.cern/fr/news/news/accelerators/ls2-report-east-area-version-20">East Experiment Area renovation project</a>.</p>\n\n<p>In addition to the beam lines, the entire infrastructure is also being renovated. The lighting system has been changed, for example, and major work is being carried out on the cooling system. High luminosity requires more intense beams which entails several changes including increased power for the circuits’ cooling plants. “We have reorganized the entire cooling system to double the flow while also reducing running costs”, explains Serge Delaval, Section Leader for Injectors within the Cooling and Ventilation Group. The two plants that use short cooling towers will therefore be replaced with one central plant, which uses a single cooling tower composed of four units. Two of these units were no longer in use and have been fully upgraded.</p>\n\n<p>At the same time, all the pumps and heat exchangers have been replaced, together with three kilometres of pipes! “We have used this consolidation as an opportunity to reduce the environmental impact, particularly regarding the products used to prevent Legionnaire’s disease”, says Serge Delaval. Stainless steel has therefore been chosen over steel as it requires much less anti-corrosion treatment. Similarly, demineralised water will also be used for some circuits.</p>\n\n<p>Work on the cooling system will continue until March and the accelerator upgrade is slated to be finished at the start of next summer.</p>\n</div>\n t \N 2019-11-25 14:37:21.6 test-con-dani \N \N \N \N \N NORMAL -60 bsilvade Password of account "Push Service Mailbox (push)" will expire in 3 day(s) Version francaise en fin de ce message\nPassword Expiration\nDear Push Service Mailbox,\n\nThe password of the account "Push Service Mailbox (push)" will expire in 3 day(s).\nActions Required\n\n * Please change the password before that date on the Account Management Portal ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * Access to the central services such as Mail, test Services (like EDH), Windows, Linux and AFS will stop working after that date if you do not change your password.\n\nGet Help\n\n * In the event of any questions or problems, please contact the Service Desk (phone +41 22 76 77777 or service-desk@cern.ch)\n * Note: Please do not reply to this message which is generated by a robot, you will not get any answer.\n\nBest regards,\nCERN IT Department.\n\nExpiration du mot de passe\nCher/Chère Push Service Mailbox,\n\nLe mot de passe du compte "Push Service Mailbox (push)" va expirer dans 3 jour(s).\nActions requises\n\n * Veuillez changer le mot de passe avant cette date sur le portail Account Management ( https://account.cern.ch/account/CERNAccount/ChangePassword.aspx?login=push ).\n\nInformation\n\n * L'accès aux services centraux comme le Mail, les services testistratifs (comme EDH), Windows, Linux et AFS ne fonctionnera plus après cette date si vous ne changez pas votre mot de passe.\n\nObtenir de l'aide\n\n * En cas de questions ou de problèmes, merci de contacter le Service Desk (téléphone +41 22 76 77777 ou service-desk@cern.ch<mailto:service-desk@cern.ch>)\n * Merci de ne pas répondre à ce message, qui a été généré par un robot: vous n' obtiendrez pas de réponse.\n\nCordialement,\nCERN Département IT\n t \N 2019-11-19 00:00:40.916 \N \N \N \N \N \N NORMAL -\. - - --- --- TOC entry 3344 (class 0 OID 258989) --- Dependencies: 219 --- Data for Name: Rules; Type: TABLE DATA; Schema: push_test; Owner: test --- - -COPY push_test."Rules" (id, name, channels, type, string, "userUsername") FROM stdin; -1 All as push PUSH AllByEmailOrPush \N proncero -\. - - --- --- TOC entry 3338 (class 0 OID 258811) --- Dependencies: 213 --- Data for Name: Services; Type: TABLE DATA; Schema: push_test; Owner: test --- - -COPY push_test."Services" (id, name, email) FROM stdin; -test-con-dani Push Notifications Service push-notifications@cern.ch -\. - - --- --- TOC entry 3340 (class 0 OID 258938) --- Dependencies: 215 --- Data for Name: UserNotifications; Type: TABLE DATA; Schema: push_test; Owner: test --- - -COPY push_test."UserNotifications" (id, read, pinned, archived, "userUsername", "notificationId") FROM stdin; -5 t f f proncero 5 -6 f f f proncero 6 -7 f f f proncero 7 -9 f f f proncero 12 -11 f f f proncero 10 -12 f f f proncero 11 -13 f f f proncero 8 -14 f f f proncero 16 -15 f f f proncero 17 -16 f f f proncero 14 -17 f f f proncero 15 -8 t f f proncero 13 -10 t f f proncero 9 -18 f f f proncero 18 -19 f f f proncero 20 -20 f f f proncero 24 -21 f f f proncero 21 -22 f f f proncero 23 -23 f f f proncero 22 -24 f f f proncero 19 -25 f f f proncero 25 -26 f f f proncero 26 -27 f f f proncero 27 -28 f f f proncero 28 -29 f f f proncero 29 -30 f f f proncero 30 -31 f f f proncero 31 -32 f f f proncero 32 -33 f f f proncero 33 -36 f f f proncero 36 -37 f f f proncero 37 -35 t f f proncero 35 -34 t f f proncero 34 -38 f f f proncero 39 -39 f f f proncero 40 -40 f f f proncero 42 -41 f f f proncero 41 -42 f f f proncero 43 -43 f f f proncero 38 -44 f f f proncero 44 -45 f f f proncero 45 -46 f f f proncero 46 -47 f f f proncero 47 -48 f f f proncero 49 -49 f f f proncero 48 -50 f f f proncero 50 -51 f f f proncero 51 -52 f f f proncero 52 -53 f f f proncero 53 -54 f f f proncero 54 -55 f f f proncero 55 -56 f f f proncero 56 -57 f f f proncero 57 -58 f f f proncero 64 -\. - - --- --- TOC entry 3337 (class 0 OID 258584) --- Dependencies: 212 --- Data for Name: Users; Type: TABLE DATA; Schema: push_test; Owner: test --- - -COPY push_test."Users" (username, email, enabled) FROM stdin; -ischuszt cristian.schuszter@cern.ch t -lolopez lorys.lopez@cern.ch t -proncero pablo.roncero.fernandez@cern.ch t -fernanre rene.fernandez@cern.ch t -jalcalap joel.alcala.perez@cern.ch t -\. - - --- --- TOC entry 3324 (class 0 OID 257891) --- Dependencies: 199 --- Data for Name: Notifications; Type: TABLE DATA; Schema: test; Owner: test --- - -COPY test."Notifications" (id, target, subject, body, sent, "sendAt", "sentAt", "from") FROM stdin; -470 test-push subject body f \N \N fakeFrom -\. - - --- --- TOC entry 3321 (class 0 OID 257870) --- Dependencies: 196 --- Data for Name: Rules; Type: TABLE DATA; Schema: test; Owner: test --- - -COPY test."Rules" (id, channel, type, "userId", string) FROM stdin; -342 EMAIL AllByEmailOrPushRule \N \N -343 PUSH AllByEmailOrPushRule \N \N -\. - - --- --- TOC entry 3326 (class 0 OID 257903) --- Dependencies: 201 --- Data for Name: Services; Type: TABLE DATA; Schema: test; Owner: test --- - -COPY test."Services" (id, name, "apiKey") FROM stdin; -\. - - --- --- TOC entry 3322 (class 0 OID 257881) --- Dependencies: 197 --- Data for Name: Users; Type: TABLE DATA; Schema: test; Owner: test --- - -COPY test."Users" (id, username, email) FROM stdin; -1 username email@email.com -\. - - --- --- TOC entry 3327 (class 0 OID 257916) --- Dependencies: 202 --- Data for Name: users_notifications__notifications; Type: TABLE DATA; Schema: test; Owner: test --- - -COPY test.users_notifications__notifications ("usersId", "notificationsId") FROM stdin; -\. - - --- --- TOC entry 3385 (class 0 OID 0) --- Dependencies: 210 --- Name: Notifications_id_seq; Type: SEQUENCE SET; Schema: authorization_service; Owner: test --- - -SELECT pg_catalog.setval('authorization_service."Notifications_id_seq"', 1, false); - - --- --- TOC entry 3386 (class 0 OID 0) --- Dependencies: 205 --- Name: Rules_id_seq; Type: SEQUENCE SET; Schema: authorization_service; Owner: test --- - -SELECT pg_catalog.setval('authorization_service."Rules_id_seq"', 1, false); - - --- --- TOC entry 3387 (class 0 OID 0) --- Dependencies: 203 --- Name: Services_id_seq; Type: SEQUENCE SET; Schema: authorization_service; Owner: test --- - -SELECT pg_catalog.setval('authorization_service."Services_id_seq"', 2, true); - - --- --- TOC entry 3388 (class 0 OID 0) --- Dependencies: 208 --- Name: UserNotifications_id_seq; Type: SEQUENCE SET; Schema: authorization_service; Owner: test --- - -SELECT pg_catalog.setval('authorization_service."UserNotifications_id_seq"', 1, false); - - --- --- TOC entry 3389 (class 0 OID 0) --- Dependencies: 191 --- Name: Notfications_id_seq; Type: SEQUENCE SET; Schema: public; Owner: test --- - -SELECT pg_catalog.setval('public."Notfications_id_seq"', 36, true); - - --- --- TOC entry 3390 (class 0 OID 0) --- Dependencies: 193 --- Name: Notifications_id_seq; Type: SEQUENCE SET; Schema: public; Owner: test --- - -SELECT pg_catalog.setval('public."Notifications_id_seq"', 4, true); - - --- --- TOC entry 3391 (class 0 OID 0) --- Dependencies: 189 --- Name: Users_id_seq; Type: SEQUENCE SET; Schema: public; Owner: test --- - -SELECT pg_catalog.setval('public."Users_id_seq"', 1, false); - - --- --- TOC entry 3392 (class 0 OID 0) --- Dependencies: 225 --- Name: Channels_primaryKey_seq; Type: SEQUENCE SET; Schema: push; Owner: test --- - -SELECT pg_catalog.setval('push."Channels_primaryKey_seq"', 21, true); - - --- --- TOC entry 3393 (class 0 OID 0) --- Dependencies: 234 --- Name: DailyNotifications_id_seq; Type: SEQUENCE SET; Schema: push; Owner: test --- - -SELECT pg_catalog.setval('push."DailyNotifications_id_seq"', 2, true); - - --- --- TOC entry 3394 (class 0 OID 0) --- Dependencies: 222 --- Name: Notifications_id_seq; Type: SEQUENCE SET; Schema: push; Owner: test --- - -SELECT pg_catalog.setval('push."Notifications_id_seq"', 37, true); - - --- --- TOC entry 3395 (class 0 OID 0) --- Dependencies: 227 --- Name: Preferences_id_seq; Type: SEQUENCE SET; Schema: push; Owner: test --- - -SELECT pg_catalog.setval('push."Preferences_id_seq"', 22, true); - - --- --- TOC entry 3396 (class 0 OID 0) --- Dependencies: 220 --- Name: UserNotifications_id_seq; Type: SEQUENCE SET; Schema: push; Owner: test --- - -SELECT pg_catalog.setval('push."UserNotifications_id_seq"', 1, false); - - --- --- TOC entry 3397 (class 0 OID 0) --- Dependencies: 216 --- Name: Notifications_id_seq; Type: SEQUENCE SET; Schema: push_test; Owner: test --- - -SELECT pg_catalog.setval('push_test."Notifications_id_seq"', 64, true); - - --- --- TOC entry 3398 (class 0 OID 0) --- Dependencies: 218 --- Name: Rules_id_seq; Type: SEQUENCE SET; Schema: push_test; Owner: test --- - -SELECT pg_catalog.setval('push_test."Rules_id_seq"', 1, true); - - --- --- TOC entry 3399 (class 0 OID 0) --- Dependencies: 214 --- Name: UserNotifications_id_seq; Type: SEQUENCE SET; Schema: push_test; Owner: test --- - -SELECT pg_catalog.setval('push_test."UserNotifications_id_seq"', 58, true); - - --- --- TOC entry 3400 (class 0 OID 0) --- Dependencies: 198 --- Name: Notifications_id_seq; Type: SEQUENCE SET; Schema: test; Owner: test --- - -SELECT pg_catalog.setval('test."Notifications_id_seq"', 470, true); - - --- --- TOC entry 3401 (class 0 OID 0) --- Dependencies: 195 --- Name: Rules_id_seq; Type: SEQUENCE SET; Schema: test; Owner: test --- - -SELECT pg_catalog.setval('test."Rules_id_seq"', 343, true); - - --- --- TOC entry 3402 (class 0 OID 0) --- Dependencies: 200 --- Name: Services_id_seq; Type: SEQUENCE SET; Schema: test; Owner: test --- - -SELECT pg_catalog.setval('test."Services_id_seq"', 509, true); - - --- --- TOC entry 3107 (class 2606 OID 258081) --- Name: Rules PK_9966a0656d39b62e1c37ef912ff; Type: CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Rules" - ADD CONSTRAINT "PK_9966a0656d39b62e1c37ef912ff" PRIMARY KEY (id); - - --- --- TOC entry 3114 (class 2606 OID 258112) --- Name: Notifications PK_a8a64c3cdfb69c2b84ea0dc05f9; Type: CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Notifications" - ADD CONSTRAINT "PK_a8a64c3cdfb69c2b84ea0dc05f9" PRIMARY KEY (id); - - --- --- TOC entry 3109 (class 2606 OID 258091) --- Name: Users PK_a8aa2427c1085e957928fdd3809; Type: CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Users" - ADD CONSTRAINT "PK_a8aa2427c1085e957928fdd3809" PRIMARY KEY (id); - - --- --- TOC entry 3112 (class 2606 OID 258099) --- Name: UserNotifications PK_f89dab386c80a39a17ecd1332d8; Type: CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."UserNotifications" - ADD CONSTRAINT "PK_f89dab386c80a39a17ecd1332d8" PRIMARY KEY (id); - - --- --- TOC entry 3099 (class 2606 OID 258066) --- Name: Services PK_fda332019de682bc8e474112b18; Type: CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Services" - ADD CONSTRAINT "PK_fda332019de682bc8e474112b18" PRIMARY KEY (id); - - --- --- TOC entry 3101 (class 2606 OID 258070) --- Name: Services UQ_615bf21e2614a26b3df0aa30ef9; Type: CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Services" - ADD CONSTRAINT "UQ_615bf21e2614a26b3df0aa30ef9" UNIQUE ("apiKey"); - - --- --- TOC entry 3103 (class 2606 OID 258068) --- Name: Services UQ_f2d51af70f67c2dd86657549f26; Type: CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Services" - ADD CONSTRAINT "UQ_f2d51af70f67c2dd86657549f26" UNIQUE (name); - - --- --- TOC entry 3077 (class 2606 OID 257756) --- Name: Users PK_16d4f7d636df336db11d87413e3; Type: CONSTRAINT; Schema: public; Owner: test --- - -ALTER TABLE ONLY public."Users" - ADD CONSTRAINT "PK_16d4f7d636df336db11d87413e3" PRIMARY KEY (id); - - --- --- TOC entry 3079 (class 2606 OID 257768) --- Name: Notfications PK_6463423e5cf0ee0261103566099; Type: CONSTRAINT; Schema: public; Owner: test --- - -ALTER TABLE ONLY public."Notfications" - ADD CONSTRAINT "PK_6463423e5cf0ee0261103566099" PRIMARY KEY (id); - - --- --- TOC entry 3081 (class 2606 OID 257786) --- Name: Notifications PK_c77268afe7d3c5568da66c5bebe; Type: CONSTRAINT; Schema: public; Owner: test --- - -ALTER TABLE ONLY public."Notifications" - ADD CONSTRAINT "PK_c77268afe7d3c5568da66c5bebe" PRIMARY KEY (id); - - --- --- TOC entry 3136 (class 2606 OID 259870) --- Name: Groups PK_1036beb1e2f958e6ffe4af0668c; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Groups" - ADD CONSTRAINT "PK_1036beb1e2f958e6ffe4af0668c" PRIMARY KEY (id); - - --- --- TOC entry 3132 (class 2606 OID 259849) --- Name: UserNotifications PK_25b987313e820785e36f789fce9; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."UserNotifications" - ADD CONSTRAINT "PK_25b987313e820785e36f789fce9" PRIMARY KEY (id); - - --- --- TOC entry 3157 (class 2606 OID 259931) --- Name: channels_unsubscribed__users PK_2964328ef2c2b2cb6dc455cd906; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.channels_unsubscribed__users - ADD CONSTRAINT "PK_2964328ef2c2b2cb6dc455cd906" PRIMARY KEY ("channelsPrimaryKey", "usersUsername"); - - --- --- TOC entry 3164 (class 2606 OID 260021) --- Name: DailyNotifications PK_3915c9e0a5b61461b8d45ee1570; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."DailyNotifications" - ADD CONSTRAINT "PK_3915c9e0a5b61461b8d45ee1570" PRIMARY KEY (id); - - --- --- TOC entry 3168 (class 2606 OID 260097) --- Name: preferences_disabled_channels__channels PK_429bce42ff0a56eee544722d4a9; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.preferences_disabled_channels__channels - ADD CONSTRAINT "PK_429bce42ff0a56eee544722d4a9" PRIMARY KEY ("preferencesId", "channelsPrimaryKey"); - - --- --- TOC entry 3153 (class 2606 OID 259924) --- Name: channels_members__users PK_47589642d8d14b7ab8f2d8ffe00; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.channels_members__users - ADD CONSTRAINT "PK_47589642d8d14b7ab8f2d8ffe00" PRIMARY KEY ("channelsPrimaryKey", "usersUsername"); - - --- --- TOC entry 3134 (class 2606 OID 259862) --- Name: Notifications PK_4b04b7cc85e5bec41a3e112ab0e; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Notifications" - ADD CONSTRAINT "PK_4b04b7cc85e5bec41a3e112ab0e" PRIMARY KEY (id); - - --- --- TOC entry 3161 (class 2606 OID 259941) --- Name: channels_groups__groups PK_4de83462be76f3c0143fea569a9; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.channels_groups__groups - ADD CONSTRAINT "PK_4de83462be76f3c0143fea569a9" PRIMARY KEY ("channelsPrimaryKey", "groupsId"); - - --- --- TOC entry 3141 (class 2606 OID 259888) --- Name: Channels PK_beb9a033413e67d02a8e38e38a3; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Channels" - ADD CONSTRAINT "PK_beb9a033413e67d02a8e38e38a3" PRIMARY KEY ("primaryKey"); - - --- --- TOC entry 3143 (class 2606 OID 259900) --- Name: Preferences PK_df9d94acb04c3ea85603c634f6b; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Preferences" - ADD CONSTRAINT "PK_df9d94acb04c3ea85603c634f6b" PRIMARY KEY (id); - - --- --- TOC entry 3145 (class 2606 OID 259909) --- Name: Users PK_f446f63889a85308fbc5ce0fe04; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Users" - ADD CONSTRAINT "PK_f446f63889a85308fbc5ce0fe04" PRIMARY KEY (username); - - --- --- TOC entry 3147 (class 2606 OID 259917) --- Name: Services PK_f7fdeaa9c02e5506593d35a939d; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Services" - ADD CONSTRAINT "PK_f7fdeaa9c02e5506593d35a939d" PRIMARY KEY (id); - - --- --- TOC entry 3138 (class 2606 OID 259872) --- Name: Groups UQ_cbf00aa66f2f7ad0970f73d5ae4; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Groups" - ADD CONSTRAINT "UQ_cbf00aa66f2f7ad0970f73d5ae4" UNIQUE ("groupIdentifier"); - - --- --- TOC entry 3149 (class 2606 OID 259919) --- Name: Services UQ_ef4d2e448dd7b00d8c261787002; Type: CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Services" - ADD CONSTRAINT "UQ_ef4d2e448dd7b00d8c261787002" UNIQUE (name); - - --- --- TOC entry 3118 (class 2606 OID 258818) --- Name: Services PK_166c6340639ab62ac94d78ba7f2; Type: CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."Services" - ADD CONSTRAINT "PK_166c6340639ab62ac94d78ba7f2" PRIMARY KEY (id); - - --- --- TOC entry 3123 (class 2606 OID 258944) --- Name: UserNotifications PK_429928d0e28a02b3277c8e6f7e8; Type: CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."UserNotifications" - ADD CONSTRAINT "PK_429928d0e28a02b3277c8e6f7e8" PRIMARY KEY (id); - - --- --- TOC entry 3129 (class 2606 OID 258998) --- Name: Rules PK_65056b33448fdeed62bb4ac0d42; Type: CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."Rules" - ADD CONSTRAINT "PK_65056b33448fdeed62bb4ac0d42" PRIMARY KEY (id); - - --- --- TOC entry 3116 (class 2606 OID 258674) --- Name: Users PK_a0e1b0c28e14b024f7fd85fdbfe; Type: CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."Users" - ADD CONSTRAINT "PK_a0e1b0c28e14b024f7fd85fdbfe" PRIMARY KEY (username); - - --- --- TOC entry 3125 (class 2606 OID 258957) --- Name: Notifications PK_c305c7e954d1b2c4375911489bd; Type: CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."Notifications" - ADD CONSTRAINT "PK_c305c7e954d1b2c4375911489bd" PRIMARY KEY (id); - - --- --- TOC entry 3120 (class 2606 OID 258820) --- Name: Services UQ_e46db72dd9e489367a9c98dbfd7; Type: CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."Services" - ADD CONSTRAINT "UQ_e46db72dd9e489367a9c98dbfd7" UNIQUE (name); - - --- --- TOC entry 3097 (class 2606 OID 257920) --- Name: users_notifications__notifications PK_142b0d79c7e8ced138efb789357; Type: CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test.users_notifications__notifications - ADD CONSTRAINT "PK_142b0d79c7e8ced138efb789357" PRIMARY KEY ("usersId", "notificationsId"); - - --- --- TOC entry 3091 (class 2606 OID 257911) --- Name: Services PK_7472cc1ebfd534e665360a490c2; Type: CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Services" - ADD CONSTRAINT "PK_7472cc1ebfd534e665360a490c2" PRIMARY KEY (id); - - --- --- TOC entry 3085 (class 2606 OID 257878) --- Name: Rules PK_b4023c95b5e08eaa991cf8b1d29; Type: CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Rules" - ADD CONSTRAINT "PK_b4023c95b5e08eaa991cf8b1d29" PRIMARY KEY (id); - - --- --- TOC entry 3087 (class 2606 OID 257888) --- Name: Users PK_b689c8e952c77a5c49388e7532f; Type: CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Users" - ADD CONSTRAINT "PK_b689c8e952c77a5c49388e7532f" PRIMARY KEY (id); - - --- --- TOC entry 3089 (class 2606 OID 257900) --- Name: Notifications PK_df985fc3cf268e7a9d9eaadb72d; Type: CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Notifications" - ADD CONSTRAINT "PK_df985fc3cf268e7a9d9eaadb72d" PRIMARY KEY (id); - - --- --- TOC entry 3093 (class 2606 OID 257913) --- Name: Services UQ_db452d84cc41f7c8e2ebed2ea25; Type: CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Services" - ADD CONSTRAINT "UQ_db452d84cc41f7c8e2ebed2ea25" UNIQUE (name); - - --- --- TOC entry 3095 (class 2606 OID 257915) --- Name: Services UQ_e36e26e678f6607fed8edffdfb0; Type: CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Services" - ADD CONSTRAINT "UQ_e36e26e678f6607fed8edffdfb0" UNIQUE ("apiKey"); - - --- --- TOC entry 3104 (class 1259 OID 258083) --- Name: IDX_54bdd24814fbfbe635ba1b66e9; Type: INDEX; Schema: authorization_service; Owner: test --- - -CREATE INDEX "IDX_54bdd24814fbfbe635ba1b66e9" ON authorization_service."Rules" USING btree (id, type); - - --- --- TOC entry 3105 (class 1259 OID 258082) --- Name: IDX_890c6405f913d40a62f4116674; Type: INDEX; Schema: authorization_service; Owner: test --- - -CREATE INDEX "IDX_890c6405f913d40a62f4116674" ON authorization_service."Rules" USING btree (type); - - --- --- TOC entry 3110 (class 1259 OID 258100) --- Name: IDX_d9a995168f69ddf2434d6f3a88; Type: INDEX; Schema: authorization_service; Owner: test --- - -CREATE INDEX "IDX_d9a995168f69ddf2434d6f3a88" ON authorization_service."UserNotifications" USING btree ("userId", "notificationId"); - - --- --- TOC entry 3154 (class 1259 OID 259932) --- Name: IDX_002c53c060932a4d7a85670be6; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_002c53c060932a4d7a85670be6" ON push.channels_unsubscribed__users USING btree ("channelsPrimaryKey"); - - --- --- TOC entry 3155 (class 1259 OID 259933) --- Name: IDX_053a368046a723ddb69de41813; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_053a368046a723ddb69de41813" ON push.channels_unsubscribed__users USING btree ("usersUsername"); - - --- --- TOC entry 3150 (class 1259 OID 259925) --- Name: IDX_33da04f0e1b8a6de39b274b296; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_33da04f0e1b8a6de39b274b296" ON push.channels_members__users USING btree ("channelsPrimaryKey"); - - --- --- TOC entry 3130 (class 1259 OID 259850) --- Name: IDX_39c5f67aa875674aa4638b5208; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_39c5f67aa875674aa4638b5208" ON push."UserNotifications" USING btree ("userUsername", "notificationId"); - - --- --- TOC entry 3158 (class 1259 OID 259943) --- Name: IDX_63d0692973bdb93d0e57ee08e3; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_63d0692973bdb93d0e57ee08e3" ON push.channels_groups__groups USING btree ("groupsId"); - - --- --- TOC entry 3139 (class 1259 OID 260061) --- Name: IDX_68dff9f8160b7787532e3ab136; Type: INDEX; Schema: push; Owner: test --- - -CREATE UNIQUE INDEX "IDX_68dff9f8160b7787532e3ab136" ON push."Channels" USING btree (id, "deleteDate"); - - --- --- TOC entry 3162 (class 1259 OID 260022) --- Name: IDX_75c5e06708abccf43679fa9e01; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_75c5e06708abccf43679fa9e01" ON push."DailyNotifications" USING btree ("userUsername", "targetPrimaryKey"); - - --- --- TOC entry 3165 (class 1259 OID 260098) --- Name: IDX_8700bf3fe1dd0fdee82af35b81; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_8700bf3fe1dd0fdee82af35b81" ON push.preferences_disabled_channels__channels USING btree ("preferencesId"); - - --- --- TOC entry 3159 (class 1259 OID 259942) --- Name: IDX_ab34bd90c2dd8a41dcbdb42b67; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_ab34bd90c2dd8a41dcbdb42b67" ON push.channels_groups__groups USING btree ("channelsPrimaryKey"); - - --- --- TOC entry 3151 (class 1259 OID 259926) --- Name: IDX_c4f386914106169964fba62575; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_c4f386914106169964fba62575" ON push.channels_members__users USING btree ("usersUsername"); - - --- --- TOC entry 3166 (class 1259 OID 260099) --- Name: IDX_de31a7cfd9b46d36f2cde82d8a; Type: INDEX; Schema: push; Owner: test --- - -CREATE INDEX "IDX_de31a7cfd9b46d36f2cde82d8a" ON push.preferences_disabled_channels__channels USING btree ("channelsPrimaryKey"); - - --- --- TOC entry 3126 (class 1259 OID 258999) --- Name: IDX_8479e16c8f2a9247d6a57ed09a; Type: INDEX; Schema: push_test; Owner: test --- - -CREATE INDEX "IDX_8479e16c8f2a9247d6a57ed09a" ON push_test."Rules" USING btree (type); - - --- --- TOC entry 3121 (class 1259 OID 258945) --- Name: IDX_8e2bcc52d13d59d9114dbd6e20; Type: INDEX; Schema: push_test; Owner: test --- - -CREATE INDEX "IDX_8e2bcc52d13d59d9114dbd6e20" ON push_test."UserNotifications" USING btree ("userUsername", "notificationId"); - - --- --- TOC entry 3127 (class 1259 OID 259000) --- Name: IDX_8fcccdc5a46e13bb83ee86641b; Type: INDEX; Schema: push_test; Owner: test --- - -CREATE INDEX "IDX_8fcccdc5a46e13bb83ee86641b" ON push_test."Rules" USING btree (id, type); - - --- --- TOC entry 3082 (class 1259 OID 257879) --- Name: IDX_54659c03730073cde471d4312c; Type: INDEX; Schema: test; Owner: test --- - -CREATE INDEX "IDX_54659c03730073cde471d4312c" ON test."Rules" USING btree (type); - - --- --- TOC entry 3083 (class 1259 OID 257880) --- Name: IDX_f0e7530dea8d4cb6a7c3ac60ed; Type: INDEX; Schema: test; Owner: test --- - -CREATE INDEX "IDX_f0e7530dea8d4cb6a7c3ac60ed" ON test."Rules" USING btree (id, type); - - --- --- TOC entry 3174 (class 2606 OID 258123) --- Name: UserNotifications FK_099c9aae30fffd2596c80c2b549; Type: FK CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."UserNotifications" - ADD CONSTRAINT "FK_099c9aae30fffd2596c80c2b549" FOREIGN KEY ("notificationId") REFERENCES authorization_service."Notifications"(id); - - --- --- TOC entry 3175 (class 2606 OID 258128) --- Name: Notifications FK_944d1e34f04d46890758dcfc6fe; Type: FK CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Notifications" - ADD CONSTRAINT "FK_944d1e34f04d46890758dcfc6fe" FOREIGN KEY ("fromId") REFERENCES authorization_service."Services"(id); - - --- --- TOC entry 3172 (class 2606 OID 258113) --- Name: Rules FK_dbf68107a33c0cdd2c1e29d32d5; Type: FK CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."Rules" - ADD CONSTRAINT "FK_dbf68107a33c0cdd2c1e29d32d5" FOREIGN KEY ("userId") REFERENCES authorization_service."Users"(id); - - --- --- TOC entry 3173 (class 2606 OID 258118) --- Name: UserNotifications FK_fa7e9a75ff3922059ac04f642e5; Type: FK CONSTRAINT; Schema: authorization_service; Owner: test --- - -ALTER TABLE ONLY authorization_service."UserNotifications" - ADD CONSTRAINT "FK_fa7e9a75ff3922059ac04f642e5" FOREIGN KEY ("userId") REFERENCES authorization_service."Users"(id); - - --- --- TOC entry 3189 (class 2606 OID 259989) --- Name: channels_unsubscribed__users FK_002c53c060932a4d7a85670be64; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.channels_unsubscribed__users - ADD CONSTRAINT "FK_002c53c060932a4d7a85670be64" FOREIGN KEY ("channelsPrimaryKey") REFERENCES push."Channels"("primaryKey") ON DELETE CASCADE; - - --- --- TOC entry 3190 (class 2606 OID 259994) --- Name: channels_unsubscribed__users FK_053a368046a723ddb69de418139; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.channels_unsubscribed__users - ADD CONSTRAINT "FK_053a368046a723ddb69de418139" FOREIGN KEY ("usersUsername") REFERENCES push."Users"(username) ON DELETE CASCADE; - - --- --- TOC entry 3186 (class 2606 OID 259974) --- Name: Preferences FK_117d8c0dfc3b742c41505af10d7; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Preferences" - ADD CONSTRAINT "FK_117d8c0dfc3b742c41505af10d7" FOREIGN KEY ("targetPrimaryKey") REFERENCES push."Channels"("primaryKey"); - - --- --- TOC entry 3187 (class 2606 OID 259979) --- Name: channels_members__users FK_33da04f0e1b8a6de39b274b2964; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.channels_members__users - ADD CONSTRAINT "FK_33da04f0e1b8a6de39b274b2964" FOREIGN KEY ("channelsPrimaryKey") REFERENCES push."Channels"("primaryKey") ON DELETE CASCADE; - - --- --- TOC entry 3193 (class 2606 OID 260027) --- Name: DailyNotifications FK_54fb1c50f82cc3347a8e76d6812; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."DailyNotifications" - ADD CONSTRAINT "FK_54fb1c50f82cc3347a8e76d6812" FOREIGN KEY ("userUsername") REFERENCES push."Users"(username); - - --- --- TOC entry 3194 (class 2606 OID 260032) --- Name: DailyNotifications FK_5f372ebdb6a70ceeb94f4475b9a; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."DailyNotifications" - ADD CONSTRAINT "FK_5f372ebdb6a70ceeb94f4475b9a" FOREIGN KEY ("targetPrimaryKey") REFERENCES push."Channels"("primaryKey"); - - --- --- TOC entry 3192 (class 2606 OID 260004) --- Name: channels_groups__groups FK_63d0692973bdb93d0e57ee08e30; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.channels_groups__groups - ADD CONSTRAINT "FK_63d0692973bdb93d0e57ee08e30" FOREIGN KEY ("groupsId") REFERENCES push."Groups"(id) ON DELETE CASCADE; - - --- --- TOC entry 3180 (class 2606 OID 259944) --- Name: UserNotifications FK_6667b1248a1e038b86beb3072ca; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."UserNotifications" - ADD CONSTRAINT "FK_6667b1248a1e038b86beb3072ca" FOREIGN KEY ("userUsername") REFERENCES push."Users"(username); - - --- --- TOC entry 3182 (class 2606 OID 259954) --- Name: Notifications FK_6ba4194daf95241b854bd83e467; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Notifications" - ADD CONSTRAINT "FK_6ba4194daf95241b854bd83e467" FOREIGN KEY ("targetPrimaryKey") REFERENCES push."Channels"("primaryKey"); - - --- --- TOC entry 3183 (class 2606 OID 259959) --- Name: Channels FK_7a8b4463f203b24390fbecf568f; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Channels" - ADD CONSTRAINT "FK_7a8b4463f203b24390fbecf568f" FOREIGN KEY ("ownerUsername") REFERENCES push."Users"(username); - - --- --- TOC entry 3195 (class 2606 OID 260102) --- Name: preferences_disabled_channels__channels FK_8700bf3fe1dd0fdee82af35b812; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.preferences_disabled_channels__channels - ADD CONSTRAINT "FK_8700bf3fe1dd0fdee82af35b812" FOREIGN KEY ("preferencesId") REFERENCES push."Preferences"(id) ON DELETE CASCADE; - - --- --- TOC entry 3191 (class 2606 OID 259999) --- Name: channels_groups__groups FK_ab34bd90c2dd8a41dcbdb42b67c; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.channels_groups__groups - ADD CONSTRAINT "FK_ab34bd90c2dd8a41dcbdb42b67c" FOREIGN KEY ("channelsPrimaryKey") REFERENCES push."Channels"("primaryKey") ON DELETE CASCADE; - - --- --- TOC entry 3181 (class 2606 OID 259949) --- Name: UserNotifications FK_b2195eece7faad3fb348b593c80; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."UserNotifications" - ADD CONSTRAINT "FK_b2195eece7faad3fb348b593c80" FOREIGN KEY ("notificationId") REFERENCES push."Notifications"(id); - - --- --- TOC entry 3184 (class 2606 OID 259964) --- Name: Channels FK_b5b061cf5ce6513c090be018e9b; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Channels" - ADD CONSTRAINT "FK_b5b061cf5ce6513c090be018e9b" FOREIGN KEY ("testGroupId") REFERENCES push."Groups"(id); - - --- --- TOC entry 3188 (class 2606 OID 259984) --- Name: channels_members__users FK_c4f386914106169964fba625752; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.channels_members__users - ADD CONSTRAINT "FK_c4f386914106169964fba625752" FOREIGN KEY ("usersUsername") REFERENCES push."Users"(username) ON DELETE CASCADE; - - --- --- TOC entry 3196 (class 2606 OID 260107) --- Name: preferences_disabled_channels__channels FK_de31a7cfd9b46d36f2cde82d8a0; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push.preferences_disabled_channels__channels - ADD CONSTRAINT "FK_de31a7cfd9b46d36f2cde82d8a0" FOREIGN KEY ("channelsPrimaryKey") REFERENCES push."Channels"("primaryKey") ON DELETE CASCADE; - - --- --- TOC entry 3185 (class 2606 OID 259969) --- Name: Preferences FK_ea3f751580dc3dd35aafe2928fd; Type: FK CONSTRAINT; Schema: push; Owner: test --- - -ALTER TABLE ONLY push."Preferences" - ADD CONSTRAINT "FK_ea3f751580dc3dd35aafe2928fd" FOREIGN KEY ("userUsername") REFERENCES push."Users"(username); - - --- --- TOC entry 3176 (class 2606 OID 258958) --- Name: UserNotifications FK_9f854dd9ebb621b8e26a8e3845d; Type: FK CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."UserNotifications" - ADD CONSTRAINT "FK_9f854dd9ebb621b8e26a8e3845d" FOREIGN KEY ("userUsername") REFERENCES push_test."Users"(username); - - --- --- TOC entry 3177 (class 2606 OID 258963) --- Name: UserNotifications FK_d3aa6cd0b95e6894c667dc48c9b; Type: FK CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."UserNotifications" - ADD CONSTRAINT "FK_d3aa6cd0b95e6894c667dc48c9b" FOREIGN KEY ("notificationId") REFERENCES push_test."Notifications"(id); - - --- --- TOC entry 3178 (class 2606 OID 258968) --- Name: Notifications FK_d7e72b4a00d9154f9409d8106d3; Type: FK CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."Notifications" - ADD CONSTRAINT "FK_d7e72b4a00d9154f9409d8106d3" FOREIGN KEY ("fromId") REFERENCES push_test."Services"(id); - - --- --- TOC entry 3179 (class 2606 OID 259001) --- Name: Rules FK_dbcef7a35582a45f7550f4010f1; Type: FK CONSTRAINT; Schema: push_test; Owner: test --- - -ALTER TABLE ONLY push_test."Rules" - ADD CONSTRAINT "FK_dbcef7a35582a45f7550f4010f1" FOREIGN KEY ("userUsername") REFERENCES push_test."Users"(username); - - --- --- TOC entry 3170 (class 2606 OID 257926) --- Name: users_notifications__notifications FK_6551d57a770d5fc3c3e25659283; Type: FK CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test.users_notifications__notifications - ADD CONSTRAINT "FK_6551d57a770d5fc3c3e25659283" FOREIGN KEY ("usersId") REFERENCES test."Users"(id) ON DELETE CASCADE; - - --- --- TOC entry 3169 (class 2606 OID 257921) --- Name: Rules FK_d47ff4913a611d261e61ceaa446; Type: FK CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test."Rules" - ADD CONSTRAINT "FK_d47ff4913a611d261e61ceaa446" FOREIGN KEY ("userId") REFERENCES test."Users"(id); - - --- --- TOC entry 3171 (class 2606 OID 257931) --- Name: users_notifications__notifications FK_e58f2e1cf4a7e654daab1046d48; Type: FK CONSTRAINT; Schema: test; Owner: test --- - -ALTER TABLE ONLY test.users_notifications__notifications - ADD CONSTRAINT "FK_e58f2e1cf4a7e654daab1046d48" FOREIGN KEY ("notificationsId") REFERENCES test."Notifications"(id) ON DELETE CASCADE; - - --- Completed on 2020-12-09 11:36:45 CET - --- --- PostgreSQL database dump complete --- - - --- --- TOC entry 228 (class 1259 OID 259892) --- Name: Preferences; Type: TABLE; Schema: push; Owner: test --- - -CREATE TABLE push."UserDailyNotifications" ( - "userId" integer, - "notificationId" integer, - "date" timestamp without time zone, - "time" time without time zone, - PRIMARY KEY("userId", "date", "time") -); - - -ALTER TABLE push."UserDailyNotifications" OWNER TO test;