21.2.3
Summary of testimonies by 3rd engineer Margus Treu
As far as it is known Margus Treu has been interrogated/interviewed 13 times,
of which the following statements are available:(1) on 28.09.94 at 10.30 hours by the central criminal police, Turku - Enclosure <IP_ADDRESS>1
(2) on 28.09.94 at 12.00 hours by unknown authority in Turku - Enclosure <IP_ADDRESS>2
(3) on 29.09.94 at 10.00 hours by central criminal police, Turku - Enclosure <IP_ADDRESS>3
(4) on 29.09.94 - Notes taken by the Swedish members of the JAIC - Enclosure <IP_ADDRESS>4
(5) on 29.09.94 at 12.00 hours by the Estonian security police in Turku - Enclosure <IP_ADDRESS>5
(6) on 03.10.94 by the security police in Tallinn - Enclosure <IP_ADDRESS>6
(7) on 11.10.94 by Finnish members of the JAIC in Naantali - Enclosure <IP_ADDRESS>7
(8) on 16.10.94 by JAIC in Tallinn - Enclosure <IP_ADDRESS>8
(9) on 17.10.94 - Notes taken by Tuomo Karppinen - Enclosure <IP_ADDRESS>9
(10) on 08.03.95 - Interview by Jutta Rabe - Enclosure <IP_ADDRESS>0
(11) on 31.03.95 - The Landvetter Hearing - Enclosure <IP_ADDRESS>1
(12) on 28.02.96 by the Transport Investigation Office, Tallinn - Enclosure <IP_ADDRESS>2
(13) in May 1998 - Interview by Phillip Wearne - Enclosure <IP_ADDRESS>3.
Margus Treu is one of the three survivors considered by the JAIC to be the key witnesses and, thus, was questioned in detail, however, in the presence of the head of the nautical department of ESCO and safety adviser of ESTLINE, Captain Enn Neidre, who was then still a member of the Estonian part of the JAIC and as such insisted on participating despite the urgent requests of the Swedish and Finnish members to stay home. When the psychological expert of the JAIC, the Swede Bengt Schager, was interviewed by Jutta Rabe of Spiegel TV in this connection, he replied the following:
»Q: Hannes Kadak has withdrawn that he saw water coming in at 00.46 hrs, which he withdrew later. He first made a very precise statement and later withdrew it.
A: Oh, yes, you mean that statement, yes. Ah, it was revealed during the Landvetter investigation, when I was asking him and I don't have any explanation to what he said, but I was very curious, because first he said that he had thought about it and wasn't sure anymore and 1 minute later he wasn't sure at all whether he had said so at all. So, I don't know what to believe of that. I am in the hands of the witness, sometimes.
Q: But can it be that confusion was caused, that there were people on behalf of the Shipping Company who were employed there, who were also attending that meeting and Mr. Neidre was more or less like a boss for him, and people do get insecure when being asked.
A: (nodding) Yes, and Mr. Neidre was in full uniform as well for the first time that I have seen it.
Q: But was that very smart?
A: I don't think so, but we had no option, this was the way the Estonians wanted it. Although I had some feelings about it, he was a member of the Commission, I could not say to him, please, I want to talk with him alone. This may have altered some of the responses in the interview, yes.«
This means that Captain Enn Neidre, working ashore in the ESCO administration for many years, had without doubt deliberately put on his captain's uniform to intimidate the crew witnesses and, looking at the answers they have given, he did it successfully.
As a consequence, Treu said less than he had said in his initial statements and stuck to his impossible wrong timing, on which, however, the JAIC has built up their equally impossible casualty scenario. Margus Treu, who is indeed the key witness, because he apparently saw on the monitor how the bow ramp was struck and broke open, because this is what he told motorman Hannes Kadak in explanation of the water ingress on to the car deck according to the first statement of Kadak made on 29 September 1994 to the Finnish criminal police in Turku when he said:
»- suddenly the vessel heeled to starboard, he ran back to the ECR where Treu was watching the monitor and said: "The situation is serious" or "bad" "because the ramp has been struck and became broken." - saw on the monitor that there were high waves on the car deck and that the water level had already reached the height of the personal cars.«
This was not mentioned by any of the JAIC members at the Landvetter meeting, although it concerns one of the topics of the casualty sequence-of-events. The JAIC members instead spent their time with intimidating Kadak to the effect that he withdrew his initial and very precise statement "that at 00.46 hours he saw water penetrating the bow ramp at the upper starboard corner".
In detail:
(1) on 28.09.94 at 10.03 hours by the Central Criminal Police, Turku:- felt 3-4 heavy bangs and when the camera turned to the bow, saw very much water entering from that direction;
- immediate heel of 10°-15° (from previously 1°-2°);
- there was only water on the car deck - not in the engine room;
- the main engines shut off - he managed to start the auxiliaries;
- they tried to pump out the water that was entering the ship.
Note: The above short statement implies two circumstances:
(a) when Treu felt the heavy bangs/blows, the monitor either did not show the bow ramp (because the system was still switched to the rotating mode) or he was somewhere else in the ECR, thus he states: "When the camera turned to the bow, I saw very much water entering from that direction." There might well have been some time between him feeling the impacts and seeing the water penetrate at the bow ramp which does not exclude that at the time of the impacts water was already penetrating the bow ramp.
(b) Treu states that there was only water on the car deck, not in the engine room, but goes on to say that they tried to pump out the water that was entering the ship. Since it is not possible to pump water from the car deck, water must have been in some compartments in the vessel which were pumpable, i.e. 1st deck and/or 0-deck.(2) on 28.09.94 at 12.00 hours by unknown authority in Turku:
- ca. 01.00 hours felt 2 double, hard bangs from forward;
- 01.15 hours saw on the monitor in the ECR that water was penetrating the car deck via the ramp, at the same time he heard the watch A.B. report about water on car deck;
- ca. 01.20 hours the bridge asked whether it would be possible to create a list to port, which it was not, because the port tank was full and the starboard one empty;
- thereafter he established that the starboard list had already increased by 1 degree and from that moment increased rapidly;
- at a list of 30°-35° the 2 port main engines stopped; an attempt to restart the engines failed;
- "We continued to make 5-6 knots."
- a moment later the 4th engine followed by the 3rd engine also stopped; the auxiliaries continued to produce power;
- ca. 01.30 hours the list was 45° and also the auxiliaries stopped and the emergency generator on deck 8 started;
- the bridge asked whether it would be possible to pump freshwater overboard, which it was not as there was no more power for the pumps;
- left the ECR and reached the 8th deck via emergency exit when the list was practically 90°.
Note: This statement was most probably made before anyone from ESCO or the JAIC had spoken to him and can thus be considered uninfluenced. It is the only of the official statements in which he testifies to have felt the two double, hard bangs at about 01.00 hours. At 01.15 hours he certainly saw water entering the car deck via the ramp, but he does not say whether he looked at the monitor straight after the bangs. Actually water had already penetrated the ramp before 01.00 hours. If he saw it for the first time, his timing must be wrong by 13-15 minutes, unless he did not look at the monitor before because he was busy with other matters, e.g. the starboard stabiliser. This is also confirmed by his statement that the list at 01.30 hours was 45°, which it actually was already at ca. 01.15 hours, whilst at 01.30 hours the vessel was on the side or was almost on the side, as confirmed by many survivors, e.g. trainee mate Einar Kukk who looked at his watch.
(3) on 29.09.94 at 10.00 hours by the Central Criminal Police, Turku:
- on watch since midnight with motorman Kadak, vessel was making 15 kn;
- at 01.15 hours the vessel was heavily shaken by 2 breakers following shortly one after the other, never before had I experienced such heavy impacts on a vessel;
- I looked at once at the monitor and saw water penetrating at the bow, the water ingress was so strong that the picture became blurred due to water splashing up to the camera;
Note: This is not possible. It is more likely that the drencher system became activated by some heat development which was subsequently followed by the fire alarm: the "Mr. Skylight to No. 1 and 2" call over the loudspeaker system.
- the result was felt at once when the vessel heeled 2°-3° to starboard.
- I heard on the walkie-talkie the watch A.B. Silver Linde, who was making his rounds and was then on the car deck, report to the watch officer on the bridge that there was water on the car deck;
- within a few minutes the list increased to 10°-15° whilst the vessel proceeded onwards with all 4 main engines and 2 auxiliaries running, then the 4th officer asked whether the list could be corrected by means of the port trim tank;
- as there was possibly some space in the port trim tank due to the list, I tried to pump some seawater into it, but the pump was just sucking air;
- after a few more minutes the list reached 20°-25° and the main engines stopped by means of automatic shut-down;
- I sent motorman Kadak, who was about to panic, up together with Henrik Sillaste;
- at about 01.30 hours the list was 40°-45° and also the auxiliaries stopped;
- the officer from the bridge asked whether it would be possible to pump out water from the starboard freshwater tanks, which it was not as there was no more power after the auxiliaries had shut down;
- I went up to the emergency generator on deck 8, which was running until the vessel was on her side and then also shut down.
Note:
(4) on 29.09.94 - Notes taken by the Swedish member of the JAIC (by Börje Stenström)
Engineer on duty (3rd engineer) (summary of hearing made in Finland):- The speed was about 15 knots.
- At 01.15 hours he noted 2 very heavy wave impacts on the ship. Water was observed, heavy water inflow, from the forward ramp, partly drenching the monitor camera.
- Vessel had 1° starboard list from the beginning, caused by the loading. Trimming tanks filled for compensation. List is starting to increase.
- Deck man of the watch reports water on the car deck. List is increasing to 10°-15° within a number of minutes.
- The bridge (4th officer) questions if the list can be compensated by ballast water. Impossible as water intake pipe now above the waterline, pump is only sucking air.
- List increased to 20°-25°. Port side main engines stop due to lube oil pressure failure, number 3 and 4 engines stop subsequently.
- The motorman on duty is sent to the bridge to report.
- At 01.30 the list has increased to 40°-45°. The engines driving the generators have stopped, (emergency generator has started).
- The bridge questions if trim could be compensated by emptying the starboard side freshwater tanks, no more possible as no electrical power available.
(5) on 29.09.94 at 12.00 hours by the Estonian Security Police in Turku:
- ca. 01.10 hours felt 2-3 heavy impacts at the bow;
- ca. 01.15 hours saw water penetrating the bow ramp at both sides on to the car deck;
- at the same time he heard the watch A.B. report water on the car deck;
- at ca. 01.20 hours the bridge asked whether it would be possible to heel the vessel to port, which it was not; - the heel to starboard increased quickly from this moment;
- tried to pump more water into the port ballast tank which failed;
- sent up the motorman and systems engineer; - at 30°-35° the port engines shut off automatically;
- at this time they were still making 5-6 kn;
- a little later also the 2 starboard engines shut off while the auxiliaries kept producing electricity;
- at about 01.30 hours the heel was ca. 45° and the auxiliaries stopped while the emergency generator started;
- bridge wanted freshwater to be pumped overboard;
- left the ECR when the vessel was practically on the side.
(6) on 03.10.94 by the Security Police in Tallinn:
- was in the ECR, all 4 main engines were running and the vessel was making a speed of ca. 14.5 kn;
- on leaving port they were able to balance the ship, but at sea a list of several degrees to starboard developed;
- heard 2 hard blows one after the other which did not result from wave impact;
- saw on the monitor after the impacts that large quantities of water were being pressed through at the sides of the ramp and under the ramp; at the ramp itself, or at its sides, there were no sealings.
- Before the impacts he saw also AB Silver Linde on the monitor at about 01.00 hours or 5 minutes later.
- At the casualty none of the main engines were running at full revolutions or full ahead. The officers were fixing the power output.
- He informed the officer that the engines had stopped.
- The car deck cannot be pumped out, but there were 12 scuppers on each side leading the water outboard.
- There were lots of cars. No empty space. At the sides there was ca. 20-25 cm space.
- From the bridge he received two orders:
- to pump more water to the port side, which was impossible,
- to pump freshwater overboard, which failed.
Note: In this statement Treu says a lot, viz.
(7) on 11.10.94 by the Finnish members of the JAIC in Naantali:
»During the night of the accident the "Estonia" used 4 engines at about 70 - 74% power. The speed was almost 15 knots. Treu left the ECR at about 0130 when the vessel listed 90°. He exited through the emergency exit by the funnel. A wave threw him towards the lee of the ship. At this stage the ship heeled over 90°. The stern sank first. The ship turned towards Treu. The ship sank about 15 minutes after Treu saw water entering the car deck. Water entered from under the ramp and along its sides. Water was thrown on to the video camera which is mounted in the roof of the car deck on the central casing bulkhead.«
(8) on 16.10.94 by JAIC in Tallinn:
»Treu was employed on board the "Estonia" as 3rd Engineer and had the 00.00-04.00 watch. The speed before the accident was 14.7 knots. The rpm's of the engines before they stopped was 500 rpm, which means 10-11 knots with normal pitch on the propellers. (On the wreck the pitch was found to be about 70%.) Normal speed was about 580-600 rpm's. The stabilisers were deployed at 00.30. Treu did not notice the ship turning before or during the heeling over. He saw Silver Linde on the ECR monitor at about 01.00. Treu heard on the walkie-talkie how Silver Linde reported to the bridge at 01.15 that there is water on deck 1.
At that stage Linde was on deck 7 distributing lifevests and only 9 minutes later he was already in the liferaft. When Treu selected a view of the bow ramp for the TV monitor, the same picture was also transmitted to the bridge. Did anyone there watch the monitor? He noticed water entering under high pressure along both sides of the ramp. From the monitor he could not see if water also entered over the top of the ramp. "Mr. Skylight" was sounded at 01.20-01.21. The port side engines stopped at about 01.20-01.25. At 01.30 Treu looked at his watch, the aux.'s stopped, the heel was 70°-75°, he left the ECR and on leaving checked the operation of the emergency generator. Treu got in the water on the starboard side, meaning in practice the funnel side of the heeled ship from which the wind and the waves came, i.e. the south-west side. In the raft he noted that as the ship sank her bows turned toward him, i.e. to the right. The ship sank at 01.45-20.00.«Note: Now the Silver Linde report "water on car deck" at about 00.45 hours has been replaced by Silver Linde reporting "water on 1st deck", which he also did, but much later, when he was finally on deck 7 after the big heel, i.e. probably at 01.05 hours.
According to page 175 of the protocol of the hearing on 17.10.94 (only this page is available) Treu stated:
»Treu: I did not see Linde but I heard his report to the bridge that water was entering at about 01.1 hours.
Q: What did he report? Treu: Bridge from watch-keeping seaman, there is water on the car deck.«
Why should the Estonian A.B. sailor Linde speak in English to the Estonian 2nd officer Kannussaar on an Estonian vessel? This is highly questionable, in particular in the light of the fact that Silver Linde could speak very little English, if at all, in subsequent interviews.(9) on 17.10.94 - Notes taken by Tuomo Karppinen:
»Watch Estonian time 24.00-04.00. Speed after 2400 was about 14.7-15 knots. Shortly after the accident the speed was reduced. Port ME before the accident was running at 560 rmp's. After the accident it was running at 500 rpm's and the speed was 10-11 knots. Treu did not note any vibrations, indicating that the vessel was turning after the accident. According to the ETA-Pilot the normal speed of the vessel was 580-600 rpm's. Linde was seen on the monitor at 01.00, coming from the pumping station for the visor and ramp. The bridge ordered us to pump ballast when the ship had heeled. When the ME's and Aux's stopped the bridge asked if we could pump out freshwater. 01.20 or 01.21 "Mr. Skylight". 01.20-01.25 ME's stopped due to heel. First Port, then Stb'd ME's stopped due to low oil pressure. Treu left the ECR at 01.30-01.32 when the Aux's had stopped. On (=when looking at) the monitor the ramp seemed to be in its correct position when water entered the car deck around the (ramp) edges. The 4th Engineer had the watch 20.00-24.00 on the Estonian coast. He may have information on the vessel's speed. The ship started heeling when water entered the car deck. When Treu left the ECR the list was 70°-75°. Treu did not observe any heel of the vessel first to one and then to the other side, for instance first to Stb'd and then P and finally back to Stb'd. The ship was thus according to Treu heeling to Stb'd at all times. The 3rd Engineer always had the 00.00-04.00 watch. The propeller pitch could be seen from the ECR. Treu did not observe any change in pitch. When the ship's stern sank the vessel came towards Treu. Treu was in the water on the Stb'd side by the funnel. When he got into a lifeboat the ship's stern was already deep down. The ship was upright (same Finnish word for upright = stern down / stern up, as for upright = no heel, Peter's note). The lights went out at 01.30. The emergency generator functioned at greater angles of heel than the Aux's. The lube oil level in the engines was higher than normal. The emergency generator stopped when the heel was great, almost 90°. When the emergency generator stopped the accumulator batteries took over. There was light until the vessel sank. Treu did not see Linde except on the monitor, but overheard his report to the bridge. Treu is positive that Linde reported to the bridge. Treu cannot estimate when the vessel sank, maybe at 01.45-02.00. Linde reported water on the car deck at 01.15. He did not say how much or how the water was entering the car deck. Treu kept the camera fixed on the bow ramp. There were no observations of water on the lower passenger deck. When the camera showed the bow ramp the same picture was also displayed on the bridge monitor on the Stb'd side of the chart room. Water entered the car deck along the sides of the ramp under great pressure. Water flew all the way on to the video camera lens. Treu did not observe water leaking along the upper edge of the ramp. Partly the upper part of the ramp was visible on the monitor. Treu was not able to say whether he could have observed water entering along the upper edge. The stabilising fins were deployed at 00.30.«
(10) on 08.03.95 - Interview by Jutta Rabe:
Q: When did you note that something unusual was going on?
A: Some minutes before 01.15 hours I heard strong bangs (2-3).
Q: Did you note anything before that time?
A: No, I did not hear anything unusual. I also saw that the watch A.B. was on the car deck at about 01.00 hours going his usual round. It was Silver Linde.
Q: What did you do at the moment of the bangs?
A: I went to the monitor to have a look, because I thought that the cars could have moved. From the monitor one can see the car deck from 4 different views.
Q: What did you see?
A: I saw that water penetrated the bow ramp and was smashing against the camera.
Q: How?
A: The water smashed with pressure against the camera.
Q: Any communication to the bridge?
A: I heard on my walkie-talkie that the watch A.B. told the bridge that water had entered the car deck.
Q: Was Silver Linde then still on the car deck?
A: I heard from the voice that it was Silver Linde, but could not see him anymore.
Q: What communication did you or your colleagues have to the bridge?
A: At this moment I did not take up communication with the bridge. I understood that the bridge was aware of the situation and the bridge did not communicate to me.
Q: Contacted by the bridge at any time?
A: Yes, they did, about 10 minutes later, "Mr. Skylight" alarm had already been announced when they were asking whether ballast could be pumped from one tank to another.
Q: When was the "Skylight" call?
A: That was probably 01.23/25 hours and shortly thereafter they asked for the ballast water pumping. We were unable to do that because the list was that large that we could not do it.
Q: Who asked from the bridge?
A: The 4th officer.
Q: When did you get out of the engine room?
A: I believe it was 01.30 hours. I am pretty sure it was 01.30 hours and the list was 70°-80° because any minute the vessel was on her side.
(11) on 31.03.95 - The Landvetter Hearing:
The Estonian Commission member, Captain Enn Neidre, attended against the strong objections of the Finnish and Swedish members in a captain's uniform.
Treu:»At 01.15 I felt 2 strong blows not caused by waves. I was in the ECR and thought it was some truck that had started to move. I went to the monitor and looked at different pictures and then it showed the forward part. There I saw that water was penetrating between ramp and hull at such high pressure that the camera was hit. I realised that the vessel rolled 3° to starboard and 1.5° to port and the next time much more to starboard and upright and then a very heavy heel to starboard. Then I heard Silver Linde's voice on the walkie-talkie that water was entering. I left the bow camera on and then Kadak and Sillaste entered.
Between 01.20-01.25 the bridge asked whether it was possible to pump over ballast, which it was not. The port main engines had shut off already. Tried to restart them, but in vain. This was at about the time of the first "Mr. Skylight" and 1 minute later the lifeboat alarm was given.
Thereafter I ordered Kadak and Sillaste to leave the engine room. This was at 01.30 when also the auxiliaries stopped.
Next the bridge asked whether it would be possible to pump freshwater overboard which it was not because there was no more power for the pumps.
I informed the bridge that I was also going up now to check the emergency generator, which stopped after a short while when the vessel was on the side and the batteries took over the supply of the emergency lights. The main engines shut off at a heel angle of more than 45° and less than 70°.
The auxiliaries stopped at a heel of 70° and the emergency generator at 90°.
It took maximal 10 minutes from the time the auxiliaries stopped to being in the water.
At 01.35/40 I left the engine room.
Apparently the engine output as well as the pitch had been reduced before the big heel.
It is possible that the port engines did not shut off automatically, but were stopped from the bridge.
There has always been maintenance work by the crew to the visor, bow ramp and locking devices as well as hydraulic cylinders for which 2nd engineer Peeter Tüür was responsible.
Elmar Siegel saw the emergency lifeboat No. 1 - starboard side, the first boat - after the heel in the water with lights on driving away without caring for those in the water. «Note: This was also seen by the passenger Thure Palmgren. »The stabilisers are pulled in automatically if the speed is below 4 kn.«
Among other things Treu made some new statements as to the stabilisers:
»Margus Treu: Yes, it was so that at 00.30 hours they had activated the stabilisers and it is so that if the speed drops below 4 knots the stabilisers move in auto-matically.
Olle Noord: This was not my question. The speed has in this case never been below 4 knots.
Margus Treu: This I cannot say, but I draw your attention to the underwater videos which show that the stabilisers are in.
Olle Noord: There is evidence that they had been activated. At port side a fin was seen ...
Margus Treu: I do not believe this.«
The above indicates that Treu, who is probably the only one to know exactly what happened, does not believe that the stabilisers were out, at least not during the final stage when the speed had dropped below 4 knots. It is the only indication in one of the official documents that there might have been something wrong with the stabilisers, because N&T/ ESCO and the crew remain silent on this, which indicates that there might be some connection with the casualty.
In the book by Andi Meister, the Chairman of the JAIC until July 1996, it is stated in Chapter 7 on page 134:»At about 00.35 hours the watch engineer went into the engine room in order to get the stabilisers in operation. At 00.30 hours the watch officer on the bridge activated the stabilisers in accordance with the master's instructions, however, one fin did not follow (did not move out).«
It is not stated what was done to rectify the problem, but Margus Treu told the English journalist Phillip Wearne in May 1998 that there had been a "stabiliser alarm" at about 00.30 hours, when the bridge tried to activate the stabilisers. It concerned the starboard fin which did not move out and it took him and Sillaste ca. 5 minutes to activate this fin.
Andi Meister told Phillip Wearne subsequently that Henrik Sillaste did not confirm the above and has refused to talk about it. Sillaste told the journalist, however, that there had been major problems with the starboard stabiliser during the installation when the vessel had been in drydock at Naantali the last time, among other things; there had been a fire. The damage caused had to be repaired during the already very short time available and the vessel sailed as planned, however, without everything in way of the starboard stabiliser installation being carried out in accordance with good workmanship as it should have been.In this connection two remarks have to be made:
1.) At the time of the casualty DIANA II was in the process of being taken over by N&T/ESCO in Rostock. Some Estonian crew members were already on board, also Captain Erik Moik as well as the representative of the Turku Repair Yard responsible for the installation of the stabilisers on the ESTONIA. This man had become very stressed upon hearing about the ESTONIA casualty, but then became very relaxed when it was reported that the visor had broken off.
2.) One of the divers spoke to a member of SEA and indicated that it is known why the casualty really happened, viz. something relevant had been only "spot welded" instead of fully welded and the element could thus not withstand the forces acting on it.
During the analysis of the statements of the survivors from deck 1 the possibility that the starboard stabiliser fin broke off and tore open the empty starboard heeling tank and/or the auxiliary engine room compartment will have to be borne in mind, in particular since recent reports from Tallinn state that there had been a lot of water in the engine room which they had been unable to pump out.
In summary:
- Treu heard and felt the impacts, which were not caused by waves, at around 01.00 hours;
- he went straight to the monitor and saw water penetrating the bow ramp at both sides under pressure, i.e. the bow ramp was slightly open because at that time the ramp actuators had already been torn off the ramp and the ramp was being held by the mooring line - see Chapter 19.
- simultaneously or shortly thereafter Silver Linde reported the water ingress to the bridge, i.e. he must have been on the car deck further aft - probably in the door of the centre casing - where the camera did not pick him up and where he saw the water ingress directly. This would mean that it was well before 01.00 hours, because the abrupt heel occurred at 01.02 hours and how else could Linde be in the crew accommodation on 7th deck at ca. 01.05 hours?
- Treu in his statements 2 and 3 has probably deliberately moved the times backwards by some 10 to 15 minutes; this becomes most obvious when he states - in his interview to Jutta Rabe of March 1995 - that the auxiliaries only stopped when the list was about 45° and that then it was 01.30 hours when the vessel was actually on her starboard side and that he, himself, was already on deck.
- The authors of the book 'Katastrofen Kurs', Anders Jörle and Anders Hellberg, who had early access to the initially confidential protocols and working papers of the Swedish part of the JAIC, have revealed that also JAIC had formed the opinion that Treu's timing was impossible. The authors explain this with "Treu's loyalty to Estline which apparently increased all the more as time went on" (last paragraph on page 157).
The authors continue on page 158 top:
»His time scheme becomes totally impossible when as during the detailed questioning at Landvetter he reconfirms: "... the last time I looked at the clock was at 00.30 hours (note: Swedish time) and then the auxiliaries had just stopped."
This, however, is not possible, because Andres Tammes had told the SILJA EUROPA in the course of the distress communi-cation already at 01.25 hours that they had a blackout and therefore could not state their position. But there cannot be a 'blackout' as long as the auxiliaries are running. Even the Estonian Commission admitted that "there has to be something wrong with Treu's statements as to the times, apparently in connection with the alarm clock (in the engine room) ... there is a mistake of between 5 and 8 minutes ...".«- The psychologist Bengt Schager, expert to the Swedish part of the JAIC, also stated:
»Margus Treu's exactness in question of times is questionable ... Margus Treu is about 10 minutes too late in his time statements.«
- In the opinion of this 'Group of Experts' his timing at least 15 minutes late, and his loyalty towards Estline is also demonstrated by the obvious fact that in none of his statements does he say anything about his observation why the bow ramp was slightly open thus enabling water to penetrate the gaps at both sides from the full visor on to the car deck, viz. just what he told Hannes Kadak after Kadak entered the ECR following the abrupt heeling to starboard: "Tillständet är allvarligt" eller "dälig", "efterson rampen har slagit sönder." This translated means: "The situation is dangerous/serious, because the ramp has been struck and become broken."
- It is amazing that the JAIC has ignored this important observation which, fortunately, Kadak testified in his first, obviously uninfluenced, statement. Instead the JAIC has endeavoured, successfully, to weaken Kadak's precise statement (Enclosure <IP_ADDRESS>4) that he saw water penetrating the bow ramp at the starboard upper side already at 00.46 hours, which is most likely the truth bearing in mind the full visor and the conditions of the bow ramp (see statement 2nd engineer Peeter Tüür dated 03.10.94 - Enclosure 12.5.183 - and see also Chapter 16).
- The most probable explanation for Treu's observation that the bow ramp was struck and became broken can be found in Chapter 32.
(12) on 28.02.96 by the Transport Investigation Office, Tallinn:
- at 01.13 there were 2 bangs which caused him to look at the clock, thereafter he saw water penetrating through the ramp and simultane-ously he heard Silver Linde reporting by walkie-talkie that water was penetrating the 1st deck;
- earlier - at 00.55-00.59 hours - he had seen Silver Linde at the ramp, but then there had been no water;
- when the auxiliary engines stopped he decided to leave via the funnel, at that time the heel was 40°-45°, it must have been 01.25 hours;
- already earlier he had sent up Hannes Kadak and Henrik Sillaste the same way;
- it took him 2-3 minutes to reach the emergency generator room;
- when he reached the open deck the heel was 70°-75°;
- when he was still in the ECR he heard "Mr. Skylight to No. 1 and 2", thereafter the boat alarm with signals; at that time the vessel was heeling more than 20°;
- he was still in the ECR when the auxiliaries shut off and the emergency generator started; the vessel's heel was then 40°-45°;
- he was in the emergency generator room when the emergency generator stopped and the batteries took the power supply, the vessel then was heeling about 75°;
- the vessel was on the side when he went into the water.
(13) in May 1998 - Interview by Phillip Wearne:
- came already down to engine room at 23.30 and checked everything;
- at 00.30 the stabilisers were activated;
- at 01.13 he felt strong blows, went to the monitor and saw that water was pressing through the sides of the ramp;
- the water came through at both sides of the ramp and then he heard Silver Linde saying on the walkie-talkie that there is water on the car deck; the next thing he did was to switch the camera to the fore part of the car deck where he could see the water coming in, he stayed there waiting for orders and advice from the bridge;
- then the big heel came and he watched the monitor only for a few moments because he had to concentrate on keeping the engines running as long as possible;
- he did not report to the bridge what he saw on the monitor, because only a few seconds after seeing it he heard Silver Linde report water on the car deck;
- at 01.18 the heel was so big that the main engines stopped, first the port and then the starboard side, thereafter he sent Henrik Sillaste and the motorman up and maybe one or two minutes later also the auxiliaries shut off and he also left for the 8th deck;
- apart from the fact that the port ballast tank was full and the starboard one empty it had just been a normal heavy weather voyage;
- the heel was 25°-30° when the port main engines stopped and after half or one minute also the starboard side stopped;
- at that time the monitor had already fallen down, with a big crashing noise, and the only and last thing he had seen on it was the water being pressed through along both sides of the bow ramp which was spraying on to the camera, thereafter he did not look to the monitor anymore;
- left the engine room around 01.28/30 when it was already dark and the floor had changed to being the wall;
- when he looked at the monitor for the last time, i.e. before the main engines shut off, which they did at a heel of 25°-30°, the ramp was still in place.
In summary of the thirteen statements made by Margus Treu the following can be concluded:
1. ca. 01.00 hours.
2. at 01.13 hours.
3. at 01.14 hours.
4. at 01.15 hours.
5. No statement, but "before the bangs I saw Silver Linde on the car deck, which was at 01.00 hours or 01.05 hours", thus the bangs were "after 01.00 hours".
6. Some minutes before 01.15 hours I heard strong bangs (2-3).
7. 01.13 strong bangs, looked to the monitor and saw water penetrating along both sides of the bow ramp, did not report to the bridge because seconds later he heard Silver Linde on the walkie-talkie reporting to the bridge that there was water on the car deck.
8. Some time before (the bangs) he saw Linde at the ramp at 00.55-00.59 hours - then there was no water.
1. At 01.15 hours saw on the monitor that water was penetrating the car deck via the bow ramp,
2. At 01.15 hours the vessel was shaken by 2 breakers .... I looked at once at the monitor and saw water penetrating at the bow ramp which was so strong (under pressure) that water was splashing up against the camera;
3. Saw on the monitor after the impacts that large quantities of water were being pressed through along the sides of the ramp; at the ramp itself or at its sides there were no sealings.
4. Q. What did you do right after the bangs?
A: I went to the monitor to have a look ... . I saw that water was penetrating the bow ramp and was smashing against the camera. The water smashed with pressure against the camera.Note: The distance between the bow ramp and camera is 25 m, thus the water smashing against the camera did not come from the bow ramp but from the drencher system activated by a possible fire on the car deck.
5. At 01.13 hours after the bangs saw on the monitor that water penetrated through the ramp, simultaneously Silver Linde report water on deck 1.
About 01.30 hours the list was 45° and then the auxiliary engines stopped;
2. At about 01.30 hours the vessel had a list of 40°-45°. The main engines had shut down already earlier and now also the auxiliaries stopped.
3. Q: When did you get out of the engine room?
A: I believe it was 01.30 hours. I am pretty sure it was 01.30 hours and the list was 70°-80° because any minute the vessel was on her side.
4. The auxiliaries stopped at a heel of 40°-50° and thereafter the emergency generator started. This was at about 01.25 hours when he left the engine room.
5. It took him 2-3 minutes to reach the emergency generator room inside the funnel. The heel was then 70°-75°.
6. He had sent up Hannes Kadak and Henrik Sillaste already before the auxiliaries stopped.In spite of his loyalty to Estline and ESCO Margus Treu gave a very important indication by stating that the water being pressed through the sides of the bow ramp reached the lens of the video camera fitted at the upper forepart of the centre casing. As the distance between the bow ramp and the centre casing is 27 m this is technically not possible and the water smashing against the camera lens must have come from somewhere else, the drencher system. It has to be assumed that the drencher system on the car deck as well as the fire alarm were activated and the nozzles fitted under deck also between the bow ramp and the centre casing were spraying water under pressure also on the camera lens. As this did definitely happen before 01.00 hours Margus Treu's timing has to be adjusted accordingly.


CONSPIRACY THEORY 1997 A film review by Timothy Voon Copyright 1997 Timothy Voon
Cast: Mel Gibson, Julia Roberts, Patrick Stewart. Screenplay: Brian Helgeland. Producers: Joel Silver and Richard Donner. Director: Richard Donner.
How's this for a conspiracy?
"China's title of 'Most Favoured Nation' is in truth a joint effort between the US and Chinese governments to bring about the economic down fall of the industrial giant Japan. If this joint trade assault fails, there is always Plan B devised by the Brits - the actual invasion and take-over of the Japanese country itself. The hand over of Hong Kong to China is nothing more than a ruse; the first step of many toward a pre-planned invasion of the Japanese mainland. If this fails there is always Plan C. The landing on Mars is not an expedition of discovery into the unknown, it is in fact a cover for a much more sinister project, code named 'Death Star': in which the Americans are developing a top secret, deadly laser array on the far side of the moon. When complete, Japan and then the rest of the world will be subjugated to the tyranny of the Americans or become completely eradicated. Lastly, I'm not really Timothy Mark Voon, I am in truth Stephen Graham the moderator of this Newsgroup. I see and know all. Remember 'Big Brother' is watching you this very moment."
From "The Conspiracy Theory Issue 6 vol 5" by TMT Voon.
If we watch enough TV, read enough newspapers, anyone can come up with a conspiracy theory. Most of it will be nonsense. Ever heard of the 'African-Korean Conspiracy Of Body Organ Theft', or the 'Jewish Psychiatrist Conspiracy of Selling Christ'? Mind boggling, but I've actually come across these conspiracies first hand from people who actually believe them! It just happens, that in this movie a particularly incredulous conspiracy - 'The Conspiracy of Government Funded, Mind Controlled Serial Killers' happens to be true. The question then is what does one do about it?
A very mature Julia Roberts plays an intelligent district attorney of the justice department, whose father has recently been murdered. A very confused, mumbling, paranoid Mel Gibson is a taxi driver who has conspiracies for every known news subject, and lives in an apartment where everything is under lock and key - including the combination locked coffee beans in the refrigerator. When Mel's life comes under threat as a result of issuing several copies of his conspiracy theories to his subscribers, Jules is dragged into helping this raving lunatic Mel, but does she believe him?
With what can be described as a slow start to a movie, the plot slowly grows in momentum until it reaches a satisfactory end. It is a long sit, but the director has wisely chosen not to cut corners, thus the longer footage, but at least the events remain comprehensible to the viewer. A very original concept for a movie, but sadly to say Mel Gibson is slightly out of place as the obsessive news reading, paranoid, mentally unbalanced taxi driver; whose acting can be described as a cross between his roles as the insane, over the top detective in 'Lethal Weapon', and the mentally handicapped grown-up in 'Tim'. However, Julia Roberts seems to be at peace with herself as she calmly and confidently accepts her role as a smart lawyer, with thoughts of that 'Pretty Woman' far behind her.
Comment: A satisfactory conspiracy theory.
Conspiracy Feel Scale: 0% Elvis Lives / *THE CONSPIRACY THEORY * / The Second Coming 100%
Timothy Voon e-mail<EMAIL_ADDRESS>The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Our Vision
"THE MALA " envisions quality education as the key resource for national development, delivered to a cross section of our society through sustainable projects..
Mission Statement
"THE MALA" aims for a quality learning experience for the students and quality training for the faculty by providing excellence in education within our socio-cultural framework, bringing forth benefit to students, community and the country.
Quality Policy
To Serve our clients and maintain our position as a leader in school education We intend to achieve this goal by:
Understanding that quality means complete conformance to agreed customer and user expectations, requirements & satisfaction standards.
Understanding that quality is everybody’s direct responsibility and they should continually endeavor to improve processes to ensure customer satisfaction.
Ensuring control of operational variations, through continuous training of personnel for improving service skills and know-how.
Operating all our work places in a safe and healthy environment and improve employee satisfaction.
Core values:
Mala Group of school has integrates teaching, research and creative activities in an engaging, challenging and supportive learning environment to prepare productive citizens for Pakistan and the world. The basis of development of the plan is a set of values which are the fabric of the institution. The guiding values are:
- We exercise high standards for learning, teaching and inquiry.
- We provide a well – rounded education that integrates professional preparation and study in the arts and science with co-curricular involvement.
- We demonstrate integrity through honesty, civility and fairness.
- We embrace the diversity of individuals, ideas and expressions.
- We foster personal growth within an environment in which every individual matter.
- We uphold the responsibility of our students.
Alhamdulillah! With the countless blessings of Allah Almighty and the continuous successes of all branches, Mala School has just started a dynamic project i.e. to fulfill the utmost need for widening one’s horizons. Mala Grammar School is famous for its perennial beauty.


{% extends 'base.html' %} {% block content %} Welcome to an Pitch App an Application that builds you and gives an insight on different pitches applicable in different areas {% endblock %}


(current)
Projects
Portrait Photography
Street Photography
Story Photography
At Home DIY Photography
Book Covers
Pop Art Magazine
About
Contact
NATHAN SPEIGHT
DESIGNS
Web Designer/Developer
Photographer/Videography
Graphic Designer


This version doesn't store the cell structure -- instead it exists only as a ship sailing the system of routes.


Coffin is a UI component built on top of the Skeleton framework. It aims to provide a simple, collapsible left shelf. Coffin is fully responsive and automatically collapses in mobile views - allowing you to swipe away and toggle a nagivation in and out of view. It behaves similar to facebook/path's navigation UI.
Coffin tries to adhere to semver as defined here http://semver.org/
Coffin's only dependency is skeleton. It has no js dependencies.
Currently only tested in Chrome and Safari on my iphone. Planning on adding more browsers as this tightens up though.
Using coffin is super easy. Just define a .coffin and a .page. A coffin is a collapsible drawer (you may have seen it implemented in facebook or path's iphone application). A page is a wrapper for your container. It's what slides over the top of your coffin.
To use coffin make sure you include skeleton's CSS. You'll want to have your assets loaded in a similar order as to what is shown directly below. You should include coffin.js at the bottom of your page, not in the head!
There are three main things to note when marking up a page with a coffin.
A simple implementation for the above markup might look something like this:
This project is hosted on github. Feel free to file an issue or open a pull request against the project here.
If you are opening a bug, please provide a link to a reproducible test case - preferably in jsfiddle or jsbin. If you are submiting a pull request, please do so from a feature branch. Thanks!
Created by @fat, 2012 ©


In modern websites, scripts are often “heavier” than HTML: their download size is larger, and processing time is also longer.
When the browser loads HTML and comes across a <script>...</script>
tag, it can’t continue building the DOM. It must execute the script right now. The same happens for external scripts <script src="..."></script>
: the browser must wait for the script to download, execute the downloaded script, and only then can it process the rest of the page.
That leads to two important issues:
…content before script…
…content after script…
```
There are some workarounds to that. For instance, we can put a script at the bottom of the page. Then it can see elements above it, and it doesn’t block the page content from showing:
<body>
...all content is above the script...
<script src="https://javascript.info/article/script-async-defer/long.js?speed=1"></script>
</body>
But this solution is far from perfect. For example, the browser notices the script (and can start downloading it) only after it downloaded the full HTML document. For long HTML documents, that may be a noticeable delay.
Such things are invisible for people using very fast connections, but many people in the world still have slow internet speeds and use a far-from-perfect mobile internet connection.
Luckily, there are two <script>
attributes that solve the problem for us: defer
and async
.
The defer
attribute tells the browser not to wait for the script. Instead, the browser will continue to process the HTML, build DOM. The script loads “in the background”, and then runs when the DOM is fully built.
Here’s the same example as above, but with defer
:
…content before script…
…content after script…
```
In other words:
defer
never block the page.defer
always execute when the DOM is ready (but before DOMContentLoaded
event).The following example demonstrates the second part:
```html run height=100…content before scripts…
…content after scripts…
```
DOMContentLoaded
event handler waits for the deferred script. It only triggers when the script is downloaded and executed.Deferred scripts keep their relative order, just like regular scripts.
Let’s say, we have two deferred scripts: the long.js
and then small.js
:
<script defer src="https://javascript.info/article/script-async-defer/long.js"></script>
<script defer src="https://javascript.info/article/script-async-defer/small.js"></script>
Browsers scan the page for scripts and download them in parallel, to improve performance. So in the example above both scripts download in parallel. The small.js
probably finishes first.
…But the defer
attribute, besides telling the browser “not to block”, ensures that the relative order is kept. So even though small.js
loads first, it still waits and runs after long.js
executes.
That may be important for cases when we need to load a JavaScript library and then a script that depends on it.
smart header="The `defer` attribute is only for external scripts" The `defer` attribute is ignored if the `<script>` tag has no `src`.
The async
attribute is somewhat like defer
. It also makes the script non-blocking. But it has important differences in the behavior.
The async
attribute means that a script is completely independent:
async
scripts (like defer
).async
scripts, and async
scripts don’t wait for them.DOMContentLoaded
and async scripts don’t wait for each other:
DOMContentLoaded
may happen both before an async script (if an async script finishes loading after the page is complete)In other words, async
scripts load in the background and run when ready. The DOM and other scripts don’t wait for them, and they don’t wait for anything. A fully independent script that runs when loaded. As simple, as it can get, right?
Here’s an example similar to what we’ve seen with defer
: two scripts long.js
and small.js
, but now with async
instead of defer
.
They don’t wait for each other. Whatever loads first (probably small.js
) – runs first:
…content before scripts…
…content after scripts…
```
async
doesn’t block it.DOMContentLoaded
may happen both before and after async
, no guarantees here.small.js
goes second, but probably loads before long.js
, so small.js
runs first. Although, it might be that long.js
loads first, if cached, then it runs first. In other words, async scripts run in the “load-first” order.Async scripts are great when we integrate an independent third-party script into the page: counters, ads and so on, as they don’t depend on our scripts, and our scripts shouldn’t wait for them:
<!-- Google Analytics is usually added like this -->
<script async src="https://google-analytics.com/analytics.js"></script>
There’s one more important way of adding a script to the page.
We can create a script and append it to the document dynamically using JavaScript:
js run let script = document.createElement('script'); script.src = "/article/script-async-defer/long.js"; document.body.append(script); // (*)
The script starts loading as soon as it’s appended to the document (*)
.
Dynamic scripts behave as “async” by default.
That is: - They don’t wait for anything, nothing waits for them. - The script that loads first – runs first (“load-first” order).
This can be changed if we explicitly set script.async=false
. Then scripts will be executed in the document order, just like defer
.
In this example, loadScript(src)
function adds a script and also sets async
to false
.
So long.js
always runs first (as it’s added first):
```js run function loadScript(src) { let script = document.createElement(‘script’); script.src = src; script.async = false; document.body.append(script); }
// long.js runs first because of async=false loadScript(“/article/script-async-defer/long.js”); loadScript(“/article/script-async-defer/small.js”); ```
Without script.async=false
, scripts would execute in default, load-first order (the small.js
probably first).
Again, as with the defer
, the order matters if we’d like to load a library and then another script that depends on it.
Both async
and defer
have one common thing: downloading of such scripts doesn’t block page rendering. So the user can read page content and get acquainted with the page immediately.
But there are also essential differences between them:
| Order | DOMContentLoaded |
|
|---|---|---|
async |
Load-first order. Their document order doesn’t matter – which loads first runs first | Irrelevant. May load and execute while the document has not yet been fully downloaded. That happens if scripts are small or cached, and the document is long enough. |
defer |
Document order (as they go in the document). | Execute after the document is loaded and parsed (they wait if needed), right before DOMContentLoaded . |
In practice, defer
is used for scripts that need the whole DOM and/or their relative execution order is important.
And async
is used for independent scripts, like counters or ads. And their relative execution order does not matter.
``warn header="Page without scripts should be usable" Please note: if you're using
deferor
async`, then user will see the the page before the script loads.
In such case, some graphical components are probably not initialized yet.
Don’t forget to put “loading” indication and disable buttons that aren’t functional yet. Let the user clearly see what he can do on the page, and what’s still getting ready. ```


| timeoutMs?: number |
Value must be between 4000 and 10000 or an error will be thrown. Defaults to 5000 (5 seconds). |
| stacked?: boolean |
Positions the action button/icon below the label instead of alongside it. Defaults to false. |
| leading?: boolean |
Positions the snackbar on the leading edge of the screen. |
| trailing?: boolean |
Positions the snackbar on the trailing (right) edge of the screen. |
| direction?: string |
The layout direction of the snackbar content. Default is 'ltr'. |
| dismiss?: boolean |
Show dismiss ("X") icon. Default is false. |
| closeOnEscape?: boolean |
Whether the snackbar closes when it is focused and the user presses the ESC key. Default is true. |
| classes?: string | string[] |
Add a CSS class or an array of classes. |
| actionClasses?: string | string[] |
Add a CSS class or an array of classes to the action button. |
| dismissClasses?: string | string[] |
Add a CSS class or an array of classes to the action icon. |
| politeness?: AriaLivePoliteness |
The politeness level for the screen reader announcement. Default is 'polite' |


"""
from dipy.data import read_sherbrooke_3shell
img, gtab = read_sherbrooke_3shell()
moving = np.array(img.get_data()[..., 0], dtype = floating)
//Warp the S0 with a synthetic rotation
iterations. Any modification that produces a change in the energy profile
should be carefully validated to ensure no accuracy loss.
"""
moving, static = moving, static = get_synthetic_warped_circle(20)
//Create the CC metric
sigma_diff = 2.0
radius = 4


Matcheos is happy to announce its first working Alpha release. After several weeks of development (see Updates #1-#5), the software is now ready for initial alpha testers and public code review. This alpha version only requires participants to provide an email address. Currently, the invitations are sent on a first-come-first-serve basis (...for those on the waiting list, please be patient). As the software gets hardened through testing/bug fixes, the rate of invitations will steadily increase. For now, the software should be considered as a 0.1 version. It is expected that the software is preliminary. Do not view it as a final release. There will be resets as the software upgrades to newer blockchain versions.
Matcheos wants to be a force for good. One of the core innovations of the Matcheos Smart Contract is to penalize scammers and trolls for violations of the Code of Conduct. The goal is to meet new people in a trustless and safe manner. Having said that, the crypto space is currently experiencing high-rates of scams. Please be vigilant and protect yourself. To use the Alpha version of Matcheos, you only need an email to receive the invitation. MATCHEOS DOES NOT ASK FOR PUBLIC OR PRIVATE EOS KEYS. You do not even need to have any EOS tokens to use the Alpha version. Any official Matcheos announcements will occur on multiple platforms - including this site. Please report any phishing scams or other malfeasance.
Question: What is Matcheos?
Answer: It's a new way to meet people using EOS.
Question: How far along is Matcheos?
Answer: Matcheos is in private alpha on a Dawn 3 Tesnet.
Question: How do I try Matcheos out?
Answer: Just enter your email to join the alpha waiting list.
Question: Wait. So I only need an email for the alpha?
Answer: Yup. Use a free email provider if you have privacy concerns.
Question: Do I need anything else (like private keys, EOS, etc)?
Answer: No! You only need an email. Of course, Matcheos doesn't ask for private keys.
Question: So I don't need EOS?
Answer: Not for the alpha. For the alpha, you get testnet EOS.
Question: Is the code open source?
Answer: Yes. Please review it on github here


This is an easy to use and fully asynchronous frontend to manage a CouchDB instance using ES6 promises.
The following is a step by step guide to test the functionality included in couching.js. Just press the "Next" button to start.


{% extends "jam/base.html" %} {% from "_formhelpers.html" import form_errors %} {% block title %}{{ jam.title }} » Create game{% endblock %} {% block content %}
Please enter the title of your game. You will be able to set more details later, as well as upload images and packages.


Looking like a touring bike!
So I’ve had the new bike for a while now and I’ve made a few changes to it since then. It’s actually now beginning to look like a touring bike!
A few things I already had lying around and I’ve added these to the bike, others have required a purchase. The changes I’ve made so far are:-
Saddle
The saddle was the first change - in fairness, I changed this the day after I got the bike as my Charge Spoon is the comfiest saddle I’ve used.  That, and they aren’t cheap (I paid about £20 for the Charge Spoon!).
Grips
The first major change was the addition of the Ergon GP3 Grips. This obviously required the removal of the default (decent enough) grips that have been installed by Halfords and came with the bike. However, I wanted bar ends and the tatty ergonomic grips I’d used on the previous hybrid I owned meant I didn’t really consider anything other than Ergon for the grips - as Ergon grips came with the bar end integrated into the grip and this would mean I could use an ergonomic grip as well.
These took some setting up to actually sort them out and get them about right for my hands but they seem to be in a good position now - I’d installed the right hand one with the bar end too upright and the grip itself too high up so it was uncomfy in comparison to the left hand grip. With that sorted, they feel really nice in the hand and the bar ends give me help getting up hills and an alternative hand position during riding so I shouldn’t get any hand pains.
Rack
The rack is a Tortec one I’d picked up one from the local bike shop. Can’t comment much more on it, other than to say that I’d bought another one to fit to this but had issues hitting the bags on the pedal stroke upwards so I moved back to this rack (which was fine, now I’ve found the second supporting rod which had been missing) as this allows me to mount the bags higher up which means the issue doesn’t happen.
Bags
After some looking around, I ended up getting an Ortlieb handlebar bag. I’d been toying with one for a while and ended up getting the Ortlieb one after seeing it in the shop compared to the Altura one in the shop. The O bag was far better quality in terms of waterproofing it seemed and in respect to how it worked - the O bar has magnets that allow the bag to remain closed at all times. (Interestingly, I saw that the O bag that Brompton sell doesn’t have magnets but has standard poppers. This seems a bit of a departure from the quality that I expect from Brompton, especially as the Brompton O Bag is more expensive than the non-Brompton specific bag.)
Having used it recently, it’s a decent bag with a sizeable storage amount.  Ortlieb sell other versions, that includes a divider for the internal space and a map case to put on top of the bag. A detailed review perhaps to follow.
The pannier racks are some Altura ones I’d picked up previously with the rack. They’ve served me well so far but I’m concerned that perhaps with the touring I’m hoping of doing that they might not be able to cope with the amount of kit. They don’t seem to bad in this instance (weekend ride) but I’ve also not got any of the camping gear I’d be using in those.
Misc
Under miscellaneous, I’ve added a extension to my handlebars - a Minoura Space Mount. I picked this up in person at Simpson Cycles (and I was very impressed with their service and would be using again, even if the website isn’t fantastic to use). I required this to use my lights alongside the O bag as this covers up the space where the light would normally go, so I required something to sort it. I saw that Ortlieb do their own adapters for the bag but I didn’t see these for sale in the UK and needed a solution sharpish, so was able to nip to Simposon Cycles during my lunch break.
Overall, the bikes beginning to take shape quite nicely and I look forward to use it!


We optimize services!
- incubate cutting-edge mindshare
- scale global e-commerce
- expedite collaborative solutions
- cultivate extensible platforms
- leverage impactful deliverables
- mesh web-enabled solutions
- e-enable granular e-markets
- synthesize impactful technologies
- orchestrate leading-edge infomediaries
- envisioneer best-of-breed architectures
- orchestrate real-time networks
- morph distributed users
- visualize visionary e-tailers
- harness interactive channels


{% extends "layout.html" %} {% block page_title %} Registered Traveller {% endblock %} {% block content %} Back What is your email address? This will only be used to contact you about your registration Continue {% endblock %}
This will only be used to contact you about your registration


Welcome to Game Town! On this site you will find dozens of games and categories! Many of the games you will find
are flip-card style games and I am sure there is something for everyone!
A few of the games you will find are: Trivia, Jib-Jab, Mad-Libs, and much more!
Click the button below to browse our game selection!


This is title
Hello world
We are updating the file
We are again updating this file. This is the change THis is the demosjdflkjs;ldfk;lsk;flksf;lkfs;l
Another Paragraph added


Reservation
Delete
Date {{item.Date | date:'short'}} - {{item.Hour}}
Numberof person {{item.NbPerson}}
Comment : {{item.Comment}}


library(mosaic)
data(tips, package = "reshape2")
Recode sex
:
tips %>%
mutate(sex_n = case_when(
sex == "Female" ~ 0,
sex == "Male" ~ 1
)) -> tips2
Fit model:
glm1 <- glm(sex_n ~ total_bill, data = tips2,
family = "binomial")
Way 1
plotModel(glm1)
Way 2
Add predictions to data frame:
tips2 %>%
mutate(pred = predict(glm1, newdata = tips, type = "response")) %>%
mutate(predict_Male = pred > .5) -> tips3
Check values of predictions:
gf_histogram(~pred, data = tips3)
Plot jittered observed values (as points) plus prediction (as line):
gf_point(sex_n ~ total_bill, data = tips3,
shape = ~sex,
color = ~sex,
size = 3,
alpha = .5,
position = "jitter") %>%
gf_line(pred ~ total_bill, color = "grey40")
Way 3
Plot predicted values as points
gf_point(pred ~ total_bill, data = tips3,
color = ~sex,
shape = ~sex,
size = 3,
alpha = .5) +
labs(y = "Predicted probabality of being Male")


Left aligned text. The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies
Center aligned text. The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies
Right aligned text. The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies
Justified text. The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies
No wrap text. The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies The initiative of LICT is part of the government's plan to create 30,000 direct and 120,000 indirect jobs in the IT and ITES companies


Before Change
lines = []
for u, v in edge_nodes:
// if there are parallel edges, select the shortest in length
data = min([data for data in G.edges[u, v].values()], key=lambda x: x["length"])
// if it has a geometry attribute (ie, a list of line segments)
if "geometry" in data and use_geom:
After Change
lines = []
for u, v in edge_nodes:
// if there are parallel edges, select the shortest in length
data = min(G.get_edge_data(u, v).values(), key=lambda x: x["length"])
// if it has a geometry attribute (ie, a list of line segments)
if "geometry" in data and use_geom:


Making Delicious Cakes
Cake Ingredients
Flour
Sugar
Eggs
How to Make Cake
Go and buy cake ingredients
Make the cake
Eat the cake
Functions of the ingredients
Flour
It give the cake a nice texture.
Sugar
It makes the cake sweet.
Eggs
It gives the cake a yellow colour


San Bernardino County man considered 'armed and dangerous' wanted on felony domestic violence warrant
SAN BERNARDINO, Calif. (KABC) -- A San Bernardino County man considered "armed and dangerous" is wanted on a felony domestic violence warrant, authorities said Tuesday.
The alleged incident occurred Saturday at about 10:11 p.m. in Yucaipa.
The suspect, 41-year-old Bloomington resident Carlos Llanes, is known to have ties to a residence in the 12000 block of 13th Street in Yucaipa, according to the San Bernardino County Sheriff's Department.
Authorities say he is known to frequent the Yucaipa area and is considered "armed and dangerous."
Llanes is described as 6 feet tall and weighs approximately 180 to 200 pounds. He generally has a shaved head and has several tattoos on his face and neck.
He is known to drive a black 2005 Lexus IS300 sedan with the California plate 8KYU876.
Anyone with information is asked to call Deputy Christopher Coillot at the Yucaipa Station at<PHONE_NUMBER>.


Track Name
Artist
Album
1
Hide You
Kosheen
Resist
2
.38.45
Thievery Corporation
Sounds From the Thievery Hi-Fi
3
Fix You
Cold Play
X&Y
4
Hide You
Kosheen
Resist
5
.38.45
Thievery Corporation
Sounds From the Thievery Hi-Fi
6
Fix You
Cold Play
X&Y


| Interface | Description |
|---|---|
| BucketTimedMetric |
Used to collect timed metrics but puts the statistics into millisecond time ranges (buckets).
|
| CounterMetric |
Metric based on a counter (long value) typically used to count discrete events.
|
| CounterStatistics |
Statistics provided by the
CounterMetric . |
| GaugeDouble |
A Gauge returning a double value providing the 'source' for a
GaugeDoubleMetric . |
| GaugeDoubleGroup |
Groups
GaugeDoubleMetric that are closely related. |
| GaugeDoubleMetric |
Metric based on a gauge returning double values.
|
| GaugeLong |
A Gauge returning a long value providing the 'source' for a
GaugeLongMetric . |
| GaugeLongGroup |
Groups
GaugeLongMetric gauges that are closely related. |
| GaugeLongMetric |
Metric based on an underlying gauge that reports long values.
|
| Metric |
A Metric that collects statistics on events.
|
| MetricName |
The name of the metric.
|
| MetricNameCache |
Cache of MetricNames that share a common base name.
|
| MetricVisitor |
Visitor for the statistics held by a metric.
|
| TimedEvent |
A TimedEvent that is ended with either success or error.
|
| TimedMetric |
Collects and provides statics for a timed event.
|
| TimedMetricGroup |
A group of TimedMetric that share a common base name.
|
| ValueMetric |
Metric that collects long values (e.g.
|
| ValueStatistics |
Statistics collected by ValueMetric or TimedMetric.
|
| Class | Description |
|---|---|
| MetricManager |
Manages the creation and registration of Metrics.
|
Avaje metrics provides various metrics for.
Each of the metrics collect statistics. Generally a MetricReporter is used to periodically collect and report the statistics collected.
Copyright © 2014. All Rights Reserved.


This privacy notice applies to the personal data of consumers that is collected or used by Koninklijke Philips N.V. or its affiliates or subsidiaries (Philips). Philips appreciates the interest you have shown in our company, products and services by visiting our websites, www.philips.com or related communication channels, including, but not limited to, our social media pages and/or channels and blogs (together "Philips pages"). This privacy notice applies to all the personal data that Philips collects when you interact with Philips, such as when you visit our websites, when you use the products or services offered by Philips, when you purchase Philips products or services, when you subscribe to newsletters, when you contact customer support, and when you interact with Philips as a business customer, supplier or business partner, etc.
This includes, without limitation, all online and offline collections of all types of personal data. However, some Philips pages collections involve with types of data with special requirements (for example, medical data) and which require a different privacy notice. Whenever and wherever that is the case, Philips will make it clear that the privacy notice concerned is different from this general privacy notice.
To create a global approach on the protection of privacy and to allow internal data transfers between Philips companies worldwide, Philips has adopted Binding Corporate Rules called the Philips Privacy Rules. You can find more information on the Philips Privacy Rules on the Philips privacy website (www.philips.com/privacy)


by Peter Cook / @prcweb / www.prcweb.co.uk
Freelance data visualisation and web development
Brighton based
Portfolio and more at prcweb.co.uk
Question: how many ways can a single dataset by visualised?
Data: Wimbledon 2012
Comma separated value (CSV) data from tennis-data.co.uk
Single table, each row represents a single match
Each match consists of: round, player names, ATP points, games won in each set etc.
Questions & aims
Design
Data wrangling
Implementation
Who won?
What were the surprises?
Who were the heroes?
Surprise defeats?
What were the interesting matches?
etc.
No message - just allow the user to explore.
Pencil & paper
node.js + Underscore.js
D3 + HTML + SVG + CSS
Iterative
Match overview
Player overview
Hybrid?
___
Tournament is a tree structure
Circle more space efficient than triangle
D3 partition layout
D3 + HTML/CSS (no SVG)
Surprisingly usable
D3 + HTML/CSS (no SVG)
Transitions
Only shows top 32 due to space!
D3 + HTML/CSS (no SVG)
Sortable
Interaction
Shows all players in one screen
Graph -> force directed?
SVG: paths (arcs)
Another tree structure
Node = player & children = defeated players
D3 pack layout
Games won vs. ATP points
We expect games won to increase with ATP points
Outliers are heroes or losers
Hero score = sum of point differences (of unexpected win)
Simple bar chart - div elements
Graph structure
Matches where winner defeated player of higher rank
D3 force-directed layout
For each match, show the game differences
Sort by 'swinginess'
D3 + HTML/CSS (no SVG)
Design
Data wrangling
Implementation
Pencil & paper + in browser design (no Illustrator/Photoshop)
Iterative process: design, implement, design etc.
node.js + Underscore.js
5 sets of json (matches, players, matchtree, winstree, herograph)
D3/HTML/CSS/SVG in fairly equal measure
Main uses of D3: binding data to HTML/SVG elements, binding events, selection, layouts
Nothing out of the ordinary
How many ways can a single dataset be visualised? At least 10!
Start with questions
Consider exploratory visualisations too
Iterative design
Setting a challenge results in creativity
Peter Cook / @prcweb / prcweb.co.uk
___
One day beginner's D3 workshop
Brighton 3rd July 2013
Discount code: londond3


Punch List has been generated, with details as below:
PUNCHLIST ITEM ID: {punchlistid}
JOB NUMBER: {jobnumber}
JOB NAME: {jobname}
JOB PHONE: {jobphone}
JOB CONTACT: {contact}
CONTACT PERSON: {salesman}
COMPLAINT: {complaint}
Click Here to view entire PunchList


|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object | +--java.util.EventObject | +--com.milk.util.BaseEvent | +--com.milk.objed.event.EditorEvent
This is the class for events having to do with Editor
objects.
| Field Summary | |
static int |
DESCRIPTION_CHANGED
type code for descriptionChanged event |
static int |
FIELD_ADDED
type code for fieldAdded event |
static int |
FIELD_EVENT
type code for fieldEvent event |
static int |
FIELD_REMOVED
type code for fieldRemoved event |
static int |
MUTABILITY_CHANGED
type code for mutabilityChanged event |
static int |
VALUE_CHANGED
type code for valueChanged event |
| Fields inherited from class com.milk.util.BaseEvent |
myArgument, myType |
| Fields inherited from class java.util.EventObject |
source |
| Constructor Summary | |
private |
EditorEvent(Editor source,
int type,
java.lang.Object argument)
Construct an EditorEvent of the particular type for the
particular object. |
| Method Summary | |
boolean |
canSendTo(java.util.EventListener listener)
Return true if this event is appropiate for the given listener. |
static EditorEvent |
descriptionChanged(Editor source,
java.lang.String description)
Construct and return a descriptionChanged event. |
static EditorEvent |
fieldAdded(Editor source,
Editor field,
int index)
Construct and return a fieldAdded event. |
static EditorEvent |
fieldEvent(Editor source,
EditorEvent event)
Construct and return a fieldEvent event. |
static EditorEvent |
fieldRemoved(Editor source,
Editor field,
int index)
Construct and return a fieldRemoved event. |
java.lang.String |
getDescription()
Get the argument of this event as a string description, that is, the description from a descriptionChanged event. |
Editor |
getEditor()
Get the source of this event as an Editor . |
Editor |
getField()
Get the field of this event, that is, the sub-editor field from a fieldAdded or fieldRemoved event. |
int |
getIndex()
Get the index of this event, that is, the index from a fieldAdded or fieldRemoved event. |
boolean |
getMutability()
Get the argument of this event as a mutability value, that is, the mutability from a mutabilityChanged event. |
EditorEvent |
getSubEvent()
Get the argument of this event as a sub-event, that is, the event from a fieldEvent event. |
java.lang.Object |
getValue()
Get the value of this event, that is, the value from a valueChanged event. |
static EditorEvent |
mutabilityChanged(Editor source,
boolean mutability)
Construct and return a mutabilityChanged event. |
void |
sendTo(java.util.EventListener listener)
Send this event to the given listener. |
protected java.lang.String |
typeToString(int type)
Turn the given type code into a string. |
static EditorEvent |
valueChanged(Editor source,
java.lang.Object value)
Construct and return a valueChanged event. |
EditorEvent |
withNewSource(Editor source)
Return a new EditorEvent which is just like this one,
except with a new source. |
| Methods inherited from class com.milk.util.BaseEvent |
getArgument, getTimeStamp, getType, getTypeString, toString |
| Methods inherited from class java.util.EventObject |
getSource |
| Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait |
| Field Detail |
public static final int VALUE_CHANGED
valueChanged
event
public static final int DESCRIPTION_CHANGED
descriptionChanged
event
public static final int MUTABILITY_CHANGED
mutabilityChanged
event
public static final int FIELD_EVENT
fieldEvent
event
public static final int FIELD_ADDED
fieldAdded
event
public static final int FIELD_REMOVED
fieldRemoved
event
| Constructor Detail |
private EditorEvent(Editor source, int type, java.lang.Object argument)
EditorEvent
of the particular type for the
particular object.
source
- the object in questiontype
- the event typeargument
- the argument| Method Detail |
public EditorEvent withNewSource(Editor source)
EditorEvent
which is just like this one,
except with a new source.
source
- the new source
public static EditorEvent valueChanged(Editor source, java.lang.Object value)
source
- the editor in chargevalue
- the new valuepublic static EditorEvent descriptionChanged(Editor source, java.lang.String description)
source
- the editor whose description changeddescription
- its new descriptionpublic static EditorEvent mutabilityChanged(Editor source, boolean mutability)
source
- the editor in chargemutability
- the new mutability valuepublic static EditorEvent fieldEvent(Editor source, EditorEvent event)
fieldEvent
event.
source
- the editor in chargeevent
- the event for the field that changedpublic static EditorEvent fieldAdded(Editor source, Editor field, int index)
fieldAdded
event.
source
- the editor in chargefield
- the sub-editor that was addedindex
- the index it was added atpublic static EditorEvent fieldRemoved(Editor source, Editor field, int index)
fieldRemoved
event.
source
- the editor in chargefield
- the sub-editor that was removedindex
- the index it was atpublic Editor getEditor()
Editor
. It is merely a
convenience to avoid having to do the cast yourself.
Editor
public java.lang.Object getValue()
valueChanged
event. It's the same as
getArgument()
but is named to match the event name.
public boolean getMutability()
mutabilityChanged
event. It merely
casts the argument to save you the trouble.
public java.lang.String getDescription()
descriptionChanged
event. It merely
casts the argument to save you the trouble.
String
public EditorEvent getSubEvent()
fieldEvent
event. It merely
casts the argument to save you the trouble.
EditorEvent
public int getIndex()
fieldAdded
or fieldRemoved
event.
public Editor getField()
fieldAdded
or fieldRemoved
event.
protected java.lang.String typeToString(int type)
typeToString
in class BaseEvent
type
- the type code to translate
public void sendTo(java.util.EventListener listener)
sendTo
in class BaseEvent
listener
- the listener to send topublic boolean canSendTo(java.util.EventListener listener)
canSendTo
in class BaseEvent
listener
- the listener to check
|
||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


About me
Hello, I'm an aspiring communication designer . After graduating at the Liceo classico of San Benedetto del Tronto, I'm now studying at the Politecnico of Milan. My interests are design, art, but also poetry and psychoanalysis. I hope you enjoy mi projects!


I am experienced in increasing work effectiveness providing a strong synopsis for high-level overview. The approach uses analysis and translates it into a product with programming languages and data structures to provide solutions.
Create and Design web-based application systems for the online market. Using PHP, Javascript, Mysql and HTML5 CSS3.
Create and develop web and mobile based applications using Java for mobile and PHP for the Web. Graphic design for product use using phostohop, corel draw.
Create article content for product requirements by the rules of Serach Enggine Optimization using creative and attractive techniques to attract organic customers from the internet.
Create mobile applications for iOS using Swift 4.2, create applications using kotlin and java and teach algorithms, database design, UI UX with Figma and Sketch.
Create applications based on Business processes and MVP using React Native. Code implementation based on UI UX consume API, Google Maps Integration, Socket IO, Redux, Resonsive Mobile Design and Consume API to produce optimal applications.
Create applications based on Business processes with Graphql and React Native
Working with Angular technology creating internal project.
As a frontend, I developed UI KIT Library with NextJS and Storybook for Web, then developed React dashboard for Bus tracking and developed Angular Thingsboard for IOT dashboard.
Part of me being a developer, I like to write, like reading, farming and graphic design.
I also like watching comedy and sc-fi movies like Interstellar and Inception. Running sports because before I had participated in athletics and marathon competitions. A healthy body is very important for self-productivity.


July,2017 - June,2018
Senior System Engineer/Programmer
‣ Being the subject matter expert for private cloud platform framework of BNY Mellon since 2 years, started working on re engineering of same. The new platform called as "App Engine" was based on open source tools such as
‣


Brazil says Amazon deforestation is worst since 2008
by EndPlayRIO DE JANEIRO (AP) - A report by a Brazilian government agency says the rate of deforestation in the Amazon rainforest is at its highest in more than a decade.
The National Institute for Space Research said Monday that deforestation between August 2018 and July 2019 reached 9,762 square kilometers (3,769 square miles), a 30 percent increase over the previous year and the most since 2008.
Concern about the Amazon heightened after President Jair Bolsonaro took office in January. He advocates the loosening of protections for natural reserves and indigenous lands as a way to promote economic development.
Fires in the Amazon spread at a pace unseen since 2010 in July and August, then slowed in September.
Environment ministry officials say they will meet the Amazon region's governors Thursday to discuss ways to reduce deforestation.


Shereef mentions some mindsets in this video.He compares consumer mindset(or restauraut mindset) with kitchen mindset. I totally agree with him at this point that we should learn with kitchen mindset,feel respondsible for this environment, be hungary and inspiring.By the way, he compares soccer with tennis when he is explaining the benefits of pair programming. I think he means single tennis not double. Double tennis does like soccer or pair programming that needs communication and collaboration.
I feel that EDA emphasizes teamwork a lot. "Go fast,go alone;go far,go together." And EDA's ambition is "go fast and far together"? I doubt it but would like to go through the whole learning process to see whether it does happen or not.
I am an open-minded person so I would like to soak myself up in this type of culture and see what happen to me and others. And because of my international background(I lived in 3 different countries before.),hope I could bring in something unique.
Haven't yet.So far so good.
Yes I am excited to be invovled in this kind of learning enviroment. And no it doesn't make me nervous, maybe because I know what I want and also I only need to compare myself at this moment with me of yesterday. I don't have to compare with other person. Anyhow, it is my life,my way.


CustomerName:
Small (10 inch)
Medium (12 inch)
Large (14 inch)
Bacon
Extra Cheese
Onion
Mushroom
Crust: Regular Chicargo Deep Dish New York Think
Comments: How do we get to your house?


Bastian Schweinsteiger drops hint over Jose Mourinho's next job in management
Niko Kovac was sacked as Bayern Munich manager on Sunday and the German giants are in need of a new boss
by Jake Polden, https://www.mirror.co.uk/authors/jake-polden/Bastian Schweinsteiger has revealed that Jose Mourinho would often ask about Bayern Munich when he worked with him at Manchester United.
Niko Kovac was sacked as Bayern boss on Sunday, just one day after the Bundesliga giants were pummelled 5-1 by Eintracht Frankfurt at the Commerzbank-Arena.
Bayern chiefs have already spoken to Ajax boss Erik ten Hag, but former Manchester United manager Mourinho is currently out of work and has also been linked with the job.
And according to Bayern Munich legend Schweinsteiger, who played under the Portuguese at Old Trafford, managing the German giants appears to appeal to Mourinho.
"I can imagine Mourinho in Germany," Schweinsteiger told Deutsche Welle.
"I remember he was always asking me about Bayern and the Bundesliga. During our away games, there was always Bundesliga on TV.
"He really knew every single player, even from the smaller teams. He was also learning German."
Mourinho has also been linked with the Arsenal job in recent weeks, as pressure continues to mount on Unai Emery.


Chester Billiards League
2022-2023
Cayzer Cup Fixture Schedule and Match Results
| Week 1 : 17th January 2023 | ||||||
|---|---|---|---|---|---|---|
| Ewloe B | 509 | 0 | v | 2 | 600 | Eastham Home Guard |
| Upton A | 624 | 0 | v | 2 | 689 | Ewloe A |
| Waverton | 714 | 0 | v | 2 | 790 | Upton B |
| Week 2: 24th January 2023 | ||||||
| Eastham Home Guard | 597 | 0 | v | 2 | 800 | Upton A |
| Ewloe A | 721 | 0 | v | 2 | 756 | Waverton |
| Upton B | 584 | 2 | v | 0 | 461 | Ewloe B |
| Week 3: 31st January 2023 | ||||||
| Waverton | 678 | 0 | v | 2 | 786 | Eastham Home Guard |
| Ewloe B | 400 | 2 | v | 0 | 383 | Upton A |
| Upton B | 730 | 2 | v | 0 | 722 | Ewloe A |
| Week 4: 7th February 2023 | ||||||
| Eastham Home Guard | 744 | 2 | v | 0 | 639 | Upton B |
| Upton A | 798 | 2 | v | 0 | 679 | Waverton |
| Ewloe A | 400 | 2 | v | 0 | 319 | Ewloe B |
| Week 5: 14th February 2023 | ||||||
| Ewloe A | 608 | 0 | v | 2 | 796 | Eastham Home Guard |
| Upton A | 715 | 2 | v | 0 | 712 | Upton B |
| Waverton | 400 | 2 | v | 0 | 313 | Ewloe B |
| Bye Week : 21st February 2023 | ||||||
| Week 6: 28th February 2023 | ||||||
| Eastham Home Guard | 400 | 2 | v | 0 | 334 | Ewloe B |
| Ewloe A | 701 | 0 | v | 2 | 702 | Upton A |
| Upton B | 775 | 2 | v | 0 | 703 | Waverton |
| Week 7: 7th March 2023 | ||||||
| Upton A | 686 | 2 | v | 0 | 648 | Eastham Home Guard |
| Waverton | 504 | 0 | v | 2 | 600 | Ewloe A |
| Ewloe B | 560 | 2 | v | 0 | 543 | Upton B |
| Week 8: 14th March 2023 | ||||||
| Eastham Home Guard | 300 | 0 | v | 2 | 600 | Waverton |
| Upton A | 400 | 2 | v | 0 | 327 | Ewloe B |
| Ewloe A | 746 | 2 | v | 0 | 703 | Upton B |
| Week 9: 21st March 2023 | ||||||
| Upton B | 713 | 0 | v | 2 | 790 | Eastham Home Guard |
| Waverton | 519 | 0 | v | 2 | 573 | Upton A |
| Ewloe B | 551 | 0 | v | 2 | 589 | Ewloe A |
| Week 10: 28th March 2023 | ||||||
| Eastham Home Guard | 745 | 2 | v | 0 | 576 | Ewloe A |
| Upton B | 376 | 0 | v | 2 | 600 | Upton A |
| Ewloe B | 762 | 2 | v | 0 | 745 | Waverton |
| Bye Week : 4th April 2023 - catch up unplayed matches |


It is Sky Music's policy to respect your privacy regarding any information we may collect while operating our website.
This Privacy Policy applies to https://sky-music.herokuapp.com/ ("us", "we", or "https://sky-music.herokuapp.com/").
We respect your privacy and are committed to protecting personally identifiable information you may provide us through the Website.
We have adopted this privacy policy ("Privacy Policy") to explain what information may be collected on our Website, how we use this information, and under what circumstances we may disclose the information to third parties.
This Privacy Policy applies only to information we collect through the Website and does not apply to our collection of information from other sources.
This Privacy Policy, together with the Terms and conditions posted on our Website, set forth the general rules and policies governing your use of our Website.
Depending on your activities when visiting our Website, you may be required to agree to additional terms and conditions.
Like most website operators, Sky Music collects non-personally-identifying information of the sort that web browsers and servers typically make available, such as the browser type, language preference, referring site, and the date and time of each visitor request.
Sky Music's purpose in collecting non-personally identifying information is to better understand how Sky Music's visitors use its website.
From time to time, Sky Music may release non-personally-identifying information in the aggregate, e.g., by publishing a report on trends in the usage of its website.
Sky Music also collects potentially personally-identifying information like Internet Protocol (IP) addresses for logged in users and for users leaving comments on https://sky-music.herokuapp.com/ blog posts.
Sky Music only discloses logged in user and commenter IP addresses under the same circumstances that it uses and discloses personally-identifying information as described below.
The security of your Personal Information is important to us, but remember that no method of transmission over the Internet, or method of electronic storage is 100% secure
While we strive to use commercially acceptable means to protect your Personal Information, we cannot guarantee its absolute security.
Sky Music may collect statistics about the behavior of visitors to its website.
Sky Music may display this information publicly or provide it to others.
However, Sky Music does not disclose your personally-identifying information.


{% extends "landing/base.html" %}{% load compress %}{% load i18n %} {% block js %}{{ block.super }} {% endblock %} {% block content %}
{% block password_set_instructions %}{% trans "To set up your account, enter your password twice in the form below." %}{% endblock %}
{% trans "The invite link was invalid, possibly because it has already been used. Please request a new invitation." %}


Tests Scheduler design
Background
The motivation of the feature is to exhilarate the execution of the Fixturing, buy enable configuration execution in threads. This infrastructure will be used in tests as well.
Following are the design considerations:
- Easy execution unit that enable easy execution and debug.
- Should be familiar to QA eng.
- Should support separate reporting for every process.
- Should enable parametrization of the execution unit.
Design
The execution unit that was selected is a regular test (SystemTestCase). User can build several tests run and debug them separately then use the infrastructure to execute it in parallel.
TestThreadGroup
Will manage a group of tests that will be executed in parallel. Will include methods like:
- addTest - add a new test to the group.
- start - start the execution of all the tests that were added.
- join - join all the executions.
To create the TestThreadGroup the TestThreadFactory will be used.
TestThreadFactory
A singleton that manage all the TestThreadGroup. To instantiate the object a static getInstance method will be used. The factory will have the following methods:
- getTestThreadGroup - enable the creation of TestThreadGroup.
- joinAll - join all the open groups.
- removeGroup - remove a group from the factory.
Code example
public void testThread() throws Exception {
// create 2 tests
ClearAndConfigRouter1 t1 = new ClearAndConfigRouter1();
// set the method to be used
t1.setName("testClearAndConfigRouter1");
// set the documentation (will be used in the report)
t1.setTestDocumentation("Clearing and configuring the first router...");
ClearAndConfigRouter2 t2 = new ClearAndConfigRouter2();
t2.setName("testClearAndConfigRouter2");
t2.setTestDocumentation("Clearing and configuring the second router...");
// get the default test thread group
TestThreadGroup group = TestThreadFactory.getInstance().getTestThreadGroup();
// add the 2 tests to the group
group.addTest(t1);
group.addTest(t2);
// start the execution
group.start();
// wait for all the execution to finish
group.join(100000);
}
public void tearDown() throws Exception {
TestThreadFactory.getInstance().joinAll(10000);
}
Reports
The reports will be sorted to the tests. Every test will be seen in different report level. The user will be able to set the level name by setting the test documentation (see code example).
Things to consider.
- Use thread pool in the group and support setting the number of thread to be used.
- Support rear reports of execution and only then present the sorted reports.
- Support disable of the feature.
Testing
- Run 4 router configurations.
- Execute all type of tests (pass, error, failure, fail report).
- Execute test that never return.
- Check Fixture agnostics.
...


In some scenarios on Mobile devices (without jQuery), the click events should NOT be hijacked.
$mdGestureProvider is used to configure the Gesture module to ignore or skip click hijacking on mobile
devices.
app.config(function($mdGestureProvider) {
// For mobile devices without jQuery loaded, do not
// intercept click events during the capture phase.
$mdGestureProvider.skipClickHijack();
});


App\Command\ListUsersCommand
A console command that lists all the existing users.
To use this command, open a terminal window, enter into your project directory
and execute the following:
$ php bin/console app:list-users
See https://symfony.com/doc/current/cookbook/console/console_command.html
For more advanced uses, commands can be defined as services too. See
https://symfony.com/doc/current/console/commands_as_services.html
- Author: Javier Eguiluz<EMAIL_ADDRESS>Synopsis
class ListUsersCommand
extends Command
{
- // members
- protected static string $defaultName = 'app:list-users';
- private $mailer;
- private $emailSender;
- private $users;
- // methods
- public void __construct()
- protected void configure()
- protected void execute()
- private void sendReport()
Hierarchy
Extends
- Symfony\Component\Console\Command\Command
Violations
Checkstyle
| Line | Column | Severity | Message |
|---|---|---|---|
| 82 | 126 | warning | Line exceeds 120 characters; contains 126 characters |
Members
private
- $emailSender
- $mailer
- $users
protected
- $defaultName
Methods
private
- sendReport() — Sends the given $contents to the $recipient email address.
protected
- configure() — {@inheritdoc}
- execute() — This method is executed after initialize(). It usually contains the logic to execute to complete this command task.
History
-
2019-01-14T18:46:33+00:00 (commit #e020244)
Author: Jose Antonio Martinez Iglesias (jositoyoyo@jose-antonio-martinez) / Commiter: Jose Antonio Martinez Iglesias (jositoyoyo@jose-antonio-martinez)
Primer commit


You are back in the present. With all the experience and problem-solving skills that you have gained throughout your time-travelling journeys.
You now believe that you have the skills to find who Derek’s murderer is.
But before that, you are to visit the final boss, Brexton who won all of Chris’ money (as shown in the promotional video).
Brexton brings you to the poker table and shows you a set of turns, but apparently these turns are not related to poker at all.
“Guess 1 out of 5 cards. ” he whispers to you, and leaves you to ponder upon the meaning of his words.

Are you able to figure out what the murderer likes to do, and thereby deducing who the murderer is?


Event Calendar
Calendar
Customise
Connect
Jun
2013
Jul
Aug
Sep
Oct
Nov
More
Today
Tu
4
6:30pm
Creative Skills
The Smell of Ink in the Morning
The Kitchen
This Month
Tu
4
6:30pm
Creative Skills
The Smell of Ink in the Morning
The Kitchen
Th
8
6pm
DesignPro
The Smell of Ink in the Morning and waffles in the evening
A long location to show how things cut off
Fr
9
7pm
Photography Meetup
The Smell of Ink in the Morning
The Kitchen
July
Mo
1
6:30pm
Creative Skills
The Smell of Ink in the Morning
The Kitchen
Mo
1
8pm
.Net Usergroup
The Smell of programmers in the Morning
The Bedroom
Mo
1
9pm
Functional Programming Usergroup
More programming mayhem.
The Bathroom
We
3
7:30pm
Creative Skills
The Smell of Ink in the Morning
The Kitchen
Customise
which sources to show
Done
Design
(All 9 selected)
All design sources
Creative Skills
DesignPro
UX Meetup
Creative Suite Meetup
Design & Thinking
Maker Meetup
Design Cinema
Photography Meetup
Webstock
Technology
(All 23 selected)
All technology sources
Agile Wellington
Macintosh Society
SharePoint Usergroup
.Net Usergroup
Makers Meetup
SQL Usergroup
Adobe Web Tech Meetup
Mobile Dev Meetup
Summer of Tech
Functional Programming Usergroup
Nerd Nite
TeamSystem (VSTS)
Hackers & Founders
NoSQL Usergroup
Unlimited Potential (UP)
Institute of IT Professionals
NZ ICT
Well Railed
Java Usergroup
Perl Mongers
Webstock
JS Meetup
Python Usergroup
Done
Connect
this calendar to your own
Google
Outlook
iCal


Access the Kubernetes dashboard running within the minikube cluster
minikube dashboard [flags] [options]
Use "minikube options" for a list of global command-line options (applies to all commands).


freeCodeCamp Survey Form
Thank you for taking the time to help us improve the platform
Name
Email
Age
Which option best describes your current role?
Select current role
Student
Full time job
Full time learner
Prefer not to say
Other
Would you recommend freeCodeCamp to a friend?
Definitely
Maybe
Not sure
What is your favorite feature of freeCodeCamp?
Select an option
Challenges
Projects
Community
Open source
What would you like to see improved? (Check all that apply)
Front-end Project
Front-end Project
Data Visualization
Challenges
Open Source Community
Gitter help room
Videos
City Meetups
Wiki
Forum
Additional Courses
Any comments or suggestions?
Submit


Dogfish
Catfish
Salmon
Note that there is no "Salmon" data. This is meant to fail gracefully.
Use arrays instead of objects