Issues - Redmine

Issues

Filters

Add filter

Options

	#	Project	Tracker	Status	Priority	Subject	Assignee	Updated
	4475	PYROS	Evolution	Nouveau	Normal	Build Request		10/07/2016 09:48 am
	4474	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/07/2016 09:48 am
	4473	PYROS	Evolution	Nouveau	Normal	Build Request		10/07/2016 09:47 am
	4472	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/14/2016 02:10 pm
	4471	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/07/2016 09:46 am
	4470	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/14/2016 02:09 pm
	4462	PYROS	Evolution	Nouveau	Normal	Validate		10/06/2016 02:33 pm
	4454	PYROS	Evolution	Nouveau	Normal	Build Request		10/06/2016 12:30 pm
	4453	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/06/2016 12:26 pm
	4452	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/06/2016 12:26 pm
	4451	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/06/2016 12:26 pm
	4450	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/06/2016 12:25 pm
	4449	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/06/2016 12:25 pm
	4448	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/06/2016 12:24 pm
	4447	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/06/2016 12:24 pm
	4446	PYROS	Evolution	Nouveau	Normal	Interface development		10/06/2016 12:11 pm
	4445	PYROS	Evolution	Nouveau	Normal	Interface		10/06/2016 12:09 pm
	4444	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/06/2016 11:36 am
	4443	PYROS	Evolution	Nouveau	Normal	(FT) Tests		10/06/2016 11:35 am
	4442	PYROS	Evolution	Nouveau	Normal	(FT) Architecture du projet		10/06/2016 10:37 am
	4433	PYROS	Evolution	Nouveau	Normal	Période de visibilité JD1-JD2: il peut y en avoir plusieurs dans la nuit, et il faudra que l’ETC/IS les donne TOUTES:		10/14/2016 03:09 pm
	4432	PYROS	Evolution	Nouveau	Normal	Période de visibilité JD1-JD2: recalculer le JD1-JD2 qui sera un peu différent pour chaque nuit		10/06/2016 12:23 pm
	4431	PYROS	Evolution	Nouveau	Normal	Période de visibilité JD1-JD2: Donnée par le logiciel ETC/IS		10/14/2016 03:09 pm
	4430	PYROS	Evolution	Nouveau	Normal	Sequence level (default) “Optional sequence” => option “Mandatory sequence”: if THIS sequence fails, request fails (default) “This night only” => option, “Reportable à la nuit suivante” (jusqu’à 7 nuits maxi)		10/06/2016 12:22 pm
	4429	PYROS	Evolution	Nouveau	Normal	Request level: (default) "Best effort, do as much sequences as you can" => option: "All or nothing": if ANY sequence fails, request fails		10/06/2016 12:21 pm
	4428	PYROS	Evolution	Nouveau	Normal	Pouvoir donner la date sous deux formes (“Tonight” => nuit en cours ou bien nuit qui arrive / Date précise JJ/MM/AAAA (maximum à now + 7 nuits))		10/06/2016 12:21 pm
	4426	PYROS	Evolution	Nouveau	Normal	RoutineManager : Faire un TEST import/export d’une requete		10/06/2016 12:12 pm
	4425	PYROS	Evolution	Nouveau	Normal	Créer un mode DEV : jouer avec la variable DEBUG (ou autre ?) dans src/pyros/settings.py pour mettre à TRUE en mode DEV afin d’éviter d’avoir à commenter certaines lignes lors du lancement du workflow (sinon, c’est trop long)		10/06/2016 10:02 am
	4424	PYROS	Evolution	Nouveau	Normal	Fin de nuit: Majordome fait un system.pause(), ensuite une task de calibration est lancée qui doit vérifier que tout est ok avant de faire START (dome fermé, Tele fermé, …)		10/06/2016 03:04 pm
	4423	PYROS	Evolution	Nouveau	Normal	Démarrage: Ce n’est pas Monitoring mais Majordome qui doit lancer le 1er scheduling en début de nuit		10/06/2016 02:54 pm
	4422	PYROS	Evolution	Nouveau	Normal	public/ : faut-il garder ce dossier qui ne contient qu’un seul dossier static/ ? (ce dossier static/ est-il utile à qqch ?)		10/06/2016 10:00 am
	4421	PYROS	Evolution	Nouveau	Normal	Workflow du "démarrage du système" à documenter (tout se qui se déclenche quand on lance le logiciel pour la toute première fois...) : lancement du monitoring, qui à son tour lance un scheduling, …		10/06/2016 10:47 am
	4420	PYROS	Evolution	Nouveau	Normal	Handle secondary devices errors		10/06/2016 03:43 pm
	4419	PYROS	Evolution	Nouveau	Normal	Handle primary devices errors		10/06/2016 03:43 pm
	4418	PYROS	Evolution	Nouveau	Normal	Change the 'first_schedule' to False at the end of RequestBuilder.validate()		10/14/2016 02:18 pm
	4417	PYROS	Evolution	Nouveau	Normal	When a socket connection fails (exception thrown), set the device to DISABLED (or that kind of status) in the DB, and create a system_pause task (majordome)		10/06/2016 03:24 pm
	4416	PYROS	Evolution	Nouveau	Normal	When unsubmitting, uncomment the scheduling and change the first_schedule to False		10/06/2016 12:08 pm
	4415	PYROS	Evolution	Nouveau	Normal	When unsubmitting, uncomment the check for EXED and EXING removing		10/06/2016 12:08 pm
	4414	PYROS	Evolution	Nouveau	Normal	When submitting, modify the first_schedule to False, when scheduling		10/06/2016 12:08 pm
	4413	PYROS	Evolution	Nouveau	Normal	When submitting, use the monitoring to determine sequences status		10/06/2016 12:08 pm
	4412	PYROS	Evolution	Nouveau	Normal	Uncomment filter for alerts removing		10/06/2016 12:15 pm
	4411	PYROS	Evolution	Nouveau	Normal	When saving, do more checks on coordinates, jd1/2 etc		10/06/2016 12:00 pm
	4410	PYROS	Evolution	Nouveau	Normal	Add help for new users (New accounts only)		10/06/2016 12:14 pm
	4409	PYROS	Evolution	Nouveau	Normal	Add ETC-IS simulation		10/14/2016 03:07 pm
	4408	PYROS	Evolution	Nouveau	Normal	Add options : copy my sequence on x days, and authorise report		10/06/2016 12:13 pm
	4407	PYROS	Evolution	Nouveau	Normal	Add checkbox for JD / GD		10/06/2016 12:09 pm
	4406	PYROS	Evolution	Nouveau	Normal	Add automatic computation of JD1/JD2		10/06/2016 12:03 pm
	4405	PYROS	Evolution	Nouveau	Normal	Do all the needed checks		10/06/2016 12:00 pm
	4404	PYROS	Evolution	Nouveau	Normal	Only propose the objects that matches the conditions (ex: scientific programs of the user only)		10/06/2016 12:03 pm
	4403	PYROS	Evolution	Nouveau	Normal	Put the goods fields (for coordinates etc)		10/06/2016 12:03 pm
	4402	PYROS	Evolution	Nouveau	Normal	At the beginning of the loop, ping the DISABLED devices. If they answer, change their status (TBD), and do their initialization (ex: If it's a camera, set its temperature to -150°)		10/06/2016 04:39 pm
	4401	PYROS	Evolution	Nouveau	Normal	Create tasks of obs condition changes		10/06/2016 04:39 pm
	4400	PYROS	Evolution	Nouveau	Normal	Analyse PLC status (obs conditions, ...)		10/06/2016 04:39 pm
	4399	PYROS	Evolution	Nouveau	Normal	Store the instruments & PLC status		10/06/2016 04:38 pm
	4398	PYROS	Evolution	Nouveau	Normal	Ask filter wheel for status		10/06/2016 04:38 pm
	4397	PYROS	Evolution	Nouveau	Normal	Ask PLC for status		10/06/2016 04:38 pm
	4396	PYROS	Evolution	Nouveau	Normal	After the starting actions, loop to wait for the instruments configuration to be finished		10/06/2016 04:38 pm
	4395	PYROS	Evolution	Nouveau	Normal	Initialize connection with PLC		10/14/2016 02:25 pm
	4394	PYROS	Evolution	Nouveau	Normal	Send software versions to the IC		10/06/2016 04:36 pm
	4393	PYROS	Evolution	Nouveau	Normal	Configure intruments at start		10/06/2016 04:36 pm
	4392	PYROS	Evolution	Nouveau	Normal	Initialize communication with the instruments		10/06/2016 04:32 pm
	4391	PYROS	Evolution	Nouveau	Normal	Implement night start/end computation		10/06/2016 04:28 pm
	4390	PYROS	Evolution	Nouveau	Normal	Uncomment the scheduling at the beginning		10/06/2016 04:28 pm
	4389	PYROS	Evolution	Nouveau	Normal	In the dashboard screens, put scroll on each screen to see the old logs		10/06/2016 04:19 pm
	4388	PYROS	Evolution	Nouveau	Normal	Print PLC informations (with the evolution)		10/06/2016 04:19 pm
	4387	PYROS	Evolution	Nouveau	Normal	Print the instrument status		10/06/2016 04:19 pm
	4385	PYROS	Evolution	Nouveau	Normal	change_obs_conditions : If some status changed, re-launch a scheduling		10/06/2016 03:17 pm
	4384	PYROS	Evolution	Nouveau	Normal	change_obs_conditions : Change sequences status (if needed)		10/06/2016 03:17 pm
	4383	PYROS	Evolution	Nouveau	Normal	system_start : start a scheduling		10/06/2016 03:03 pm
	4382	PYROS	Evolution	Nouveau	Normal	system_pause : stop executing tasks		10/06/2016 03:03 pm
	4381	PYROS	Evolution	Nouveau	Normal	system_pause : abort instruments		10/06/2016 03:03 pm
	4380	PYROS	Evolution	Nouveau	Normal	execute_sequence : Remove the default countdown (1, for tests)		10/06/2016 03:10 pm
	4379	PYROS	Evolution	Nouveau	Normal	execute_sequence : Give first_schedule as false when a scheduling is launched		10/06/2016 03:10 pm
	4378	PYROS	Evolution	Nouveau	Normal	execute_sequence : Use the global telescope (instead of creating one here)		10/06/2016 03:10 pm
	4377	PYROS	Evolution	Nouveau	Normal	execute_sequence : Add the PLC checks at start (to see if we do the slew)		10/06/2016 03:05 pm
	4376	PYROS	Evolution	Nouveau	Normal	TASK MANAGER : In case of alert, do not stop the ongoing plan, and make the instruments abort		10/06/2016 03:24 pm
	4375	PYROS	Evolution	Nouveau	Normal	TASK MANAGER : When a sequence is cancelled, give back the quota to the user		10/06/2016 03:24 pm
	4374	PYROS	Evolution	Nouveau	Normal	Send analyses to FSC		10/14/2016 03:06 pm
	4373	PYROS	Evolution	Nouveau	Normal	Implement the analyses		10/06/2016 04:49 pm
	4372	PYROS	Evolution	Nouveau	Normal	Apply the analyses only if it's a GRB		10/06/2016 04:56 pm
	4371	PYROS	Evolution	Nouveau	Normal	Apply the calibrations in the right function		10/06/2016 04:48 pm
	4370	PYROS	Evolution	Nouveau	Normal	Blank space filling		10/14/2016 03:06 pm
	4369	PYROS	Evolution	Nouveau	Normal	Quotas evolution		10/06/2016 02:25 pm
	4367	PYROS	Evolution	Nouveau	Normal	Do not create the execute_sequence tasks if it's not the night (- 120 seconds)		10/14/2016 02:21 pm
	4365	PYROS	Evolution	Nouveau	Normal	Store the reasons of rejects (create a new attribute, in shs ?)		10/06/2016 02:33 pm
	4364	PYROS	Evolution	Nouveau	Normal	Change the system to determine night start/end (they must be given in parameter, only if first_schedule is True)		10/14/2016 02:19 pm
	4362	PYROS	Evolution	Nouveau	Normal	Give accces to old schedules (day / days before / all end-night plannings / all plannings)		10/06/2016 02:45 pm
	4361	PYROS	Evolution	Nouveau	Normal	Show user sequences in the schedules (with links)		10/06/2016 02:44 pm
	4360	PYROS	Evolution	Nouveau	Normal	Link the main page to the current schedule instead of the simulation page		10/06/2016 02:44 pm
	4359	PYROS	Evolution	Nouveau	Normal	Think about a system of permissions		10/14/2016 03:03 pm
	4358	PYROS	Evolution	Nouveau	Normal	Create the backoffice views as the modules are integrated in pyros		10/14/2016 03:16 pm
	4357	PYROS	Evolution	Nouveau	Normal	Manage users : Users		10/06/2016 10:47 am
	4356	PYROS	Evolution	Nouveau	Normal	Manual operations on the Telescope : Devices/Telescope (TODO)		10/06/2016 10:47 am
	4355	PYROS	Evolution	Nouveau	Normal	Simulate an Alert: Alerts (TODO: Un user "admin" doit pouvoir déclencher une alerte type depuis la page web Alerts)		10/06/2016 10:46 am
	4354	PYROS	Evolution	Nouveau	Normal	Watch alerts: Alerts		10/06/2016 10:43 am
	4353	PYROS	Evolution	Nouveau	Normal	Submit a Routine Request (and get results): Routines		10/06/2016 10:43 am
	4352	PYROS	Evolution	Nouveau	Normal	Watch the data processing (workflow): System (Dashboard)		10/06/2016 10:43 am
	4351	PYROS	Evolution	Nouveau	Normal	Watch the schedule: Schedule		10/06/2016 10:43 am
	4350	PYROS	Evolution	Nouveau	Normal	Watch the environment: Devices, Site, Weather		10/06/2016 10:38 am
	4349	PYROS	Evolution	Nouveau	Normal	Interacting with Pyros: http://localhost:8000		10/06/2016 10:29 am

« Previous 1 2 3 4 5 ... 7 Next » (201-300/678) | Per page: 25, 50, 100

Also available in: Atom CSV PDF