|
Data Structures | |
| struct | tPSP |
Files | |
| file | mindsensors-ps2ctrl-v4.h |
Playstation 2 Controller Sensor. | |
Defines | |
| #define | PSPV4_I2C_ADDR 0x02 |
| #define | PSPV4_REG_CMD 0x41 |
| #define | PSPV4_CMD_INITIALISE 0x49 |
| #define | PSPV4_REG_BTN_SET_1 0x42 |
| #define | PSPV4_REG_BTN_SET_2 0x43 |
| #define | PSPV4_REG_JLEFT 0x44 |
| #define | PSPV4_REG_JRIGHT 0x46 |
| #define | PSPV4_REG_PRES_JPAD_UP 0x4A |
| #define | PSPV4_REG_PRES_JPAD_RIGHT 0x4B |
| #define | PSPV4_REG_PRES_JPAD_DOWN 0x4C |
| #define | PSPV4_REG_PRES_JPAD_LEFT 0x4D |
| #define | PSPV4_REG_PRES_BTN_L2 0x4E |
| #define | PSPV4_REG_PRES_BTN_R2 0x4F |
| #define | PSPV4_REG_PRES_BTN_L1 0x50 |
| #define | PSPV4_REG_PRES_BTN_R1 0x51 |
| #define | PSPV4_REG_PRES_BTN_TRIANGLE 0x52 |
| #define | PSPV4_REG_PRES_BTN_SQUARE 0x53 |
| #define | PSPV4_REG_PRES_BTN_CIRCLE 0x54 |
| #define | PSPV4_REG_PRES_BTN_CROSS 0x55 |
| #define | PSPV4_REG_REF_SIGNAL_CODE 0x56 |
| #define | PSPV4_REG_REF_TX_TYPE 0x57 |
| #define | PSPV4_REG_REF_SIGNAL_RAW 0x58 |
| #define | PSPV4_REG_REF_SIGNAL_COUNT 0x5C |
| #define | PSPV4_SIGNAL_FAST_REWIND 0x32 |
| #define | PSPV4_SIGNAL_FAST_FORWARD 0x34 |
| #define | PSPV4_SIGNAL_PLAY 0x35 |
| #define | PSPV4_SIGNAL_STOP 0x36 |
Functions | |
| bool | _PSPV4init (tSensors link, ubyte address=PSPV4_I2C_ADDR) |
| ubyte | _PSPV4readByte (tSensors link, ubyte reg, ubyte address=PSPV4_I2C_ADDR) |
| bool | PSPV4readButtons (tSensors link, tPSP &controllerState, ubyte address=PSPV4_I2C_ADDR) |
| bool | PSPV4readButtonPressure (tSensors link, tPSP &controllerState, ubyte address=PSPV4_I2C_ADDR) |
| byte | PSPV4readRefSignal (tSensors link, ubyte address=PSPV4_I2C_ADDR) |
| byte | PSPV4readRefSignalCount (tSensors link, ubyte address=PSPV4_I2C_ADDR) |
| byte | PSPV4readRefTXType (tSensors link, ubyte address=PSPV4_I2C_ADDR) |
| long | PSPV4readRawRefTXValue (tSensors link, ubyte address=PSPV4_I2C_ADDR) |
Variables | |
| tByteArray | PSPV4_I2CRequest |
| tByteArray | PSPV4_I2CReply |
| bool | PSPV4initalised [4] = {false, false, false, false} |
| tPSP | pspController |
Playstation 2 Controller Sensor
| #define PSPV4_CMD_INITIALISE 0x49 |
Initialisation command
Definition at line 46 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_I2C_ADDR 0x02 |
PSP-Nx V4 I2C device address
Definition at line 42 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_BTN_SET_1 0x42 |
First button set register
Definition at line 48 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_BTN_SET_2 0x43 |
Second button set register
Definition at line 49 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_CMD 0x41 |
Command register
Definition at line 44 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_JLEFT 0x44 |
Left joystick register
Definition at line 50 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_JRIGHT 0x46 |
Right joystick register
Definition at line 51 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_BTN_CIRCLE 0x54 |
Circle button register
Definition at line 63 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_BTN_CROSS 0x55 |
Cross button register
Definition at line 64 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_BTN_L1 0x50 |
L1 button register
Definition at line 59 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_BTN_L2 0x4E |
L2 button register
Definition at line 57 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_BTN_R1 0x51 |
R1 button register
Definition at line 60 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_BTN_R2 0x4F |
R2 button register
Definition at line 58 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_BTN_SQUARE 0x53 |
Square button register
Definition at line 62 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_BTN_TRIANGLE 0x52 |
Triangle button button register
Definition at line 61 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_JPAD_DOWN 0x4C |
Joypad down button register
Definition at line 55 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_JPAD_LEFT 0x4D |
Joypad left button register
Definition at line 56 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_JPAD_RIGHT 0x4B |
Joypad right button register
Definition at line 54 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_PRES_JPAD_UP 0x4A |
Joypad up button register
Definition at line 53 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_REF_SIGNAL_CODE 0x56 |
Referee Signal Code register
Definition at line 66 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_REF_SIGNAL_COUNT 0x5C |
Referee Signal Count register
Definition at line 69 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_REF_SIGNAL_RAW 0x58 |
Referee Signal Raw Value register
Definition at line 68 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_REG_REF_TX_TYPE 0x57 |
Referee Transmitter Type register
Definition at line 67 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_SIGNAL_FAST_FORWARD 0x34 |
Referee Signal 'fast forward'
Definition at line 72 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_SIGNAL_FAST_REWIND 0x32 |
Referee Signal 'fast rewind'
Definition at line 71 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_SIGNAL_PLAY 0x35 |
Referee Signal 'play'
Definition at line 73 of file mindsensors-ps2ctrl-v4.h.
| #define PSPV4_SIGNAL_STOP 0x36 |
Referee Signal 'stop'
Definition at line 74 of file mindsensors-ps2ctrl-v4.h.
| bool _PSPV4init | ( | tSensors | link, |
| ubyte | address = PSPV4_I2C_ADDR |
||
| ) |
Initialise the sensor.
Note: This is an internal function and should not be used directly.
| link | the PSP sensor port |
| address | I2C address, optional, defaults to PSPV4_I2C_ADDR |
Definition at line 117 of file mindsensors-ps2ctrl-v4.h.
| ubyte _PSPV4readByte | ( | tSensors | link, |
| ubyte | reg, | ||
| ubyte | address = PSPV4_I2C_ADDR |
||
| ) |
Read a byte from the sensor
Note: This is an internal function and should not be used directly.
| link | the PSP sensor port |
| reg | the register to read |
| address | I2C address, optional, defaults to PSPV4_I2C_ADDR |
Definition at line 145 of file mindsensors-ps2ctrl-v4.h.
| bool PSPV4readButtonPressure | ( | tSensors | link, |
| tPSP & | controllerState, | ||
| ubyte | address = PSPV4_I2C_ADDR |
||
| ) |
Read the button states with additional pressure values. Use PSPV4readButtons() if you don't care about how hard someone is pressing a button.
| link | the PSP sensor port |
| controllerState | struct to hold all the button and joystick states and values |
| address | I2C address, optional, defaults to PSPV4_I2C_ADDR |
Definition at line 233 of file mindsensors-ps2ctrl-v4.h.
| bool PSPV4readButtons | ( | tSensors | link, |
| tPSP & | controllerState, | ||
| ubyte | address = PSPV4_I2C_ADDR |
||
| ) |
Read the button states. Use PSPV4readButtonPressure() if you want additional pressure values as well.
| link | the PSP sensor port |
| controllerState | struct to hold all the button and joystick states and values |
| address | I2C address, optional, defaults to PSPV4_I2C_ADDR |
Definition at line 174 of file mindsensors-ps2ctrl-v4.h.
| long PSPV4readRawRefTXValue | ( | tSensors | link, |
| ubyte | address = PSPV4_I2C_ADDR |
||
| ) |
Get the raw data from the receiver. This is useful if custom commands are to be implemented. Simply map the returned value to a new command.
| link | the PSP sensor port |
| address | I2C address, optional, defaults to PSPV4_I2C_ADDR |
Definition at line 321 of file mindsensors-ps2ctrl-v4.h.
| byte PSPV4readRefSignal | ( | tSensors | link, |
| ubyte | address = PSPV4_I2C_ADDR |
||
| ) |
Read the last command sent by the referee.
Values can be:
| link | the PSP sensor port |
| address | I2C address, optional, defaults to PSPV4_I2C_ADDR |
Definition at line 282 of file mindsensors-ps2ctrl-v4.h.
| byte PSPV4readRefSignalCount | ( | tSensors | link, |
| ubyte | address = PSPV4_I2C_ADDR |
||
| ) |
Signal Count - increments each time the sensor receives a signal from the Referee (rolls over to 0 after 255)
| link | the PSP sensor port |
| address | I2C address, optional, defaults to PSPV4_I2C_ADDR |
Definition at line 295 of file mindsensors-ps2ctrl-v4.h.
| byte PSPV4readRefTXType | ( | tSensors | link, |
| ubyte | address = PSPV4_I2C_ADDR |
||
| ) |
Fetch the transmitter type. Can be used to differentiate between various transmitter type (TV remote vs Referee Transmitter)
| link | the PSP sensor port |
| address | I2C address, optional, defaults to PSPV4_I2C_ADDR |
Definition at line 308 of file mindsensors-ps2ctrl-v4.h.
Definition at line 106 of file mindsensors-ps2ctrl-v4.h.
Array to hold I2C reply data
Definition at line 77 of file mindsensors-ps2ctrl-v4.h.
Array to hold I2C command data
Definition at line 76 of file mindsensors-ps2ctrl-v4.h.
| bool PSPV4initalised[4] = {false, false, false, false} |
Definition at line 79 of file mindsensors-ps2ctrl-v4.h.


CHAPTER 16
THE CONDITION OF "ESTONIA" AND THE STATUS OF HER MAIN CLASS AND SAFETY CERTIFICATES BEFORE COMMENCEMENT OF HER LAST VOYAGE
16.1
The Certificates
The vessel participated in the "Continuous Class Survey System" for Hull and Machinery (CSH/CSM) of Bureau Veritas and was inspected in regular intervals.
The 3rd period of class for hull and machinery was running from 3 July 1990. Therefore, the next due date for completion of this Class Renewal III would have been 15 July 1995. The last drydocking was in Turku/Finland in January 1994, when inter alia the periodical bottom survey was carried out and the stabilisers were installed as per Hull Survey Report STK/94/3 A - see Enclosure 16.1.205. The last annual survey was carried out from 23rd to 25th August 1994 while the ferry was in service. No remarks about deficiencies affecting the class were noted in any of the reports by the attending surveyor Anders Wirstam - see Enclosure 16.1.206 - Survey Statements STK/94/77A-F dated 25.08.94 - see also the previous Chapter 15.
As part of this survey the following items were checked and apparently found to be to the surveyor's satisfaction:
Since the ferry had been taken over by her new owners, Estline AB - c/o Nordström & Thulin, Stockholm - in January 1993, Bureau Veritas was also authorised by the Government of Estonia to issue Safety Certificates pursuant to the following conventions (specified abbreviated):
LOAD LINE 1966
SOLAS 1974
MARPOL 1973
TONNAGE 1969
Thus B.V. issued also the following certificates on behalf of the Estonian National Maritime Administration allegedly after having performed the respective surveys according to the "Survey Report for Issue of PSSC" dated 27.01.94 - attached as Enclosure 16.1.207.
| Passenger Ship Safety Certificate | issued | Stockholm | 27.01.94 |
| Interim- Enclosure 16.1.208 | valid until | 27.06.94 | |
| Passenger Ship Safety Certificate | issued | Copenhagen | 23.06.94 |
| - Enclosure 16.1.209 | valid until | 26.01.95 |
Note: Although it should have been issued "Interim" it is a normal unlimited/ unrestricted Certificate issued by the Copenhagen office of B.V. and a completely different form from the one used by the Stockholm office before.
| International Load Line Certificate | issued | Stockholm | 11.04.94 |
| Interim - Enclosure 16.1.210 | valid until | 11.09.94 |
Note: According to the Report of the JAIC a new "Interim" Certificate had been issued by B.V. on 09.09.94 which, however, is not available and apparently was also not available to N&T in October/November 1994, because it is not mentioned in the letter of S.C. Forsberg to the criminal police dated 01.11.94 - see Enclosure 5.2.110.
| International Oil Pollution Prevention | issued | Stockholm | 15.03.93 |
| Certificate | valid until | 15.07.95 |
Conclusion
From the available certificates it has to be concluded that
Note: The reasons for the L.L. Certificate having been issued "interim" only were
(a) the "temporary" stability booklet which was not approved by B.V. (on behalf of the Estonian Board of Navigation);
(b) the too small cross-flooding valve between the heeling tanks.The reason why the PSSC was issued wrongly was the fact that the vessel did not comply with the requirements of SOLAS 1974 for the "intended trade", i.e. proceeded more than 20 nm from the nearest land, as stated annually in the "Survey Report for the Issue for PSSC - Clause 1 - General Information" and, thus, the bow ramp plus front bulkheads, as upper extension of the collision bulkhead above bulkhead deck = car deck, were ca. 5.8 m too much forward (see Subchapter 2.4.4 above).
The last issued L.L. Certificate had already expired on 11.09.94 and apparently a further interim one had not been issued by B.V. for reasons unknown to this 'Group of Experts'. In any event, according to the certificates issued after the surveys carried out between the 23-25 August 1994 by Anders Wirstam, the Load Line Survey was apparently carried out and Annex A - to Report No. STK/94/77E - see Enclosure 16.1.206 - was filled out although, as it looks, no new Interim L.L. Certificate had been issued by the time of the casualty.
This was, at least, the situation in October/November 1994, since it has to be assumed that N&T would have submitted the L.L. Certificate valid at the time of sinking, had they had it. However, when the Final Report of the Joint Accident Investigation Commission was published, it was most surprising to note that they stated on page 46, item 3.6.2 that there had been a valid L.L. Certificate issued on 9 September 1994. In any event, also this certificate was issued falsely because visor and bow ramp had been leaking for many months before the casualty.
Based on the status of the class and safety certificates only, it could be assumed that the vessel ESTONIA was in an acceptable condition when she departed from Tallinn on 27 September 1994. This, however, was definitely not the case as will be demonstrated in the following subchapters.
16.2
Condition of the Bow AreaBased on the information contained in the previous chapters 3.5 and 12 regarding the vessel's performance until 27 September 1994, in particular the various observations of passengers, crew members and other persons on or from the car deck or other decks of the ferry, it has to be concluded that
(1) the visor, its locking devices (hinges) and rubber packings;
(2) the bow ramp, its locking devices, hinges and rubber packings had been in a very bad condition respectively were non-existent when the ferry commenced her last voyage on the evening of 27 September 1994.This conclusion is in direct contradiction to the statements made by Bureau Veritas in the many certificates issued by them in respect of all the safety relevant parts of the vessel and it is indeed the question on what basis these certificates have been issued.
Before the observed deficiencies shall be explained in detail the relevant parts of the foreship, which played a crucial role in the casualty sequence-of-events, shall be shown below and on the following page again for easy reference.
In addition, these deficiencies are shown on a drawing of the foreship with open visor which is integrated into this report and forms the following page.
In detail:
(1) The visor, its hinges, locking devices and rubber packings:In detail:
The problems with the visor were initiated by two different circumstances, viz.- severe structural damage caused by proceeding through heavy ice at excessive speed.
- the decision of the Technical Managers, N&T, not to renew the rubber packings, assuring weather(water-)tightness of the visor and preventing the visor from vibrating and thereby avoiding cracks emanating therefrom.Structural damage:
The shell plating as well as the internals are very severely damaged in two places, viz. there is a deep vertical indentation in the bow leading upwards from the stempost for about 2 m, as can be seen on the picture below from the outside,
The arrow points to the deep indentation which is completely painted and the paint does not show contact marks. The following photos showing the inside of the same area do confirm the deep indentation in a very strong part of the visor to be of old origin.
Furthermore, the shell plating as well as the 3rd stringer at the port side are severely indented and set up with the frames buckled which had been sustained already some time before the casualty. - See the pictures above.
The condition of the visor bottom with stempost is evident from the picture below taken on 30.08.94.
Arrow 1 - Indentation in the foremost part of the visor bottom indicating that the visor's initial position was changed to forward most probably due to misalignment of the whole structure. This led to contact between the visor bottom and the stempost on the forepeak deck. Since the visor bottom in this area is not constructed to take up load, the bottom became indented and cracked.
Arrow 2 - Indicates a cracked welding seam through which water penetrated and created the rust stripes.
Arrow 3 - Indicates transverse cracks in the visor bottom in way of the contact area with the starboard steel pad welded to the forepeak deck and which should take up about 10% of the visor's weight in closed condition. Since the corresponding port side is not affected at all, it has to be assumed that the starboard side absorbs all the weight which is another indication for the complete misalignment of the visor.
Arrow 4 - Indicates a further probably cracked area.
In summary of the above it has to be concluded that the visor was completely misaligned in longitudinal, transverse and vertical direction which led to considerable problems during opening and closing. These problems increased all the more as time went by as confirmed by the many observations, e.g. of previous passengers, in particular the truck drivers having spent hours on the car deck waiting for the crew to be able to open the visor (see Subchapter 12.4.3 above).
The difficulties with the visor are also confirmed by previous crew members and pilots having observed the frequent opening and violent closing until the locating horn on the forepeak deck (pyramid) finally fitted into the mating pocket in the visor bottom (see Subchapter 12.4.3 above).Consequences of the misaligned visor
Due to the increasing misalignment it was at first difficult to close the locking devices and subsequently to open them.
Reportedly it had not been possible to open and close the Atlantic lock hydraulically for several months prior to the casualty and the crew members had to go inside the visor before arrival and after departure from Tallinn and hammer open respectively closed the bolt of the Atlantic lock which, among other things affected the load-carrying capacity of the lugs. Also the hydraulic side locks were difficult to close and subsequently to open. Reportedly on many occasions after arrival in Tallinn the lugs had to be cut off the visor by flame-cutting to be able to open the visor. Subsequently the lugs were rewelded to the visor bulkheads which continuously reduced the load-carrying capacity of these lugs (see Subchapter 12.4.3. and Chapter 30).
Obviously also the visor hinges had become affected because on 17 September 1994, i.e. 10 days before the last departure, a passenger filmed the visor and, in particular, the starboard visor hinges in Tallinn during the closing procedure.
The passenger was standing in front of deck 7 and filmed the closing of the visor, finally zooming in on the starboard hinges. The video-prints below are part of the film. Picture 2 is an enlargement of Picture 1.
On Picture 2 there are obviously several major deficiencies visible, viz.
(a) the gap between the starboard vessel hinge plate and the outer bushing is much too large (arrow 1).
(b) the outer bushing is sticking much too far out of the outer visor hinge plate (arrow 2) [which explains the large gap mentioned above].
(c) the lower part of outer bushing is missing.
(d) the securing plate is missing and the outer end of the bolt is not visible.
(e) the outer bushing appears to be twisted anti-clockwise.
(f) the inner bushing appears to be twisted clockwise.
See also Subchapters 12.4.3, 12.5 and Chapter 30.All this indicates that the steel- and bronze-bushings of the starboard visor hinge arrangement had been replaced some time ago in a very unpro-fessional way with an extremely poor standard of workmanship.
Also the member of a working team, the nautical student Rain Oolmets, who stayed on board from 15 July to 11 September 1994, had discovered cracks in the welding seams up to 10 cm long between the steel bushings and the visor hinge plates of the port and starboard visor hinge arrangements which underlines the generally poor condition of these safety relevant components. See Subchapter 12.5.
It is obvious from the above description of the visible deficiencies that the condition of the visor hinges rendered the vessel already initially unseaworthy.
Consequences of missing rubber packings
The last Finnish crew had requested the renewal of 15 m of rubber packing in way of the visor for the then planned yard time in January 1993, because the rubber packing had last been renewed in January 1991. This meant a renewal of the entire packing on the forepeak deck plus about 2 m up each front bulkhead as demonstrated by the following drawing.
Since the new technical managers N&T were of the opinion that visors are full of water at sea anyway, the rubber packings were not renewed in January 1993 and also not later. This means that the visor became quickly filled up with water at sea up to the height of the outside water level. In calm sea it was the height of the bow wave which filled the visor up to the 3rd stringer, however, the worse the weather was and the deeper the bow was diving into the waves, the higher the water rose inside the visor.
The following picture shows the ESTONIA in Tallinn, with open visor but closed bow ramp so that the otherwise invisible underside of the bow ramp is shown with the lowest section being dark - see arrow. Doubtless this was caused by the water inside the visor with hydraulic oil from the leaking cylinders swimming on top of the water surface. When the vessel reduced speed and the bow wave became smaller and finally disappeared completely when the vessel was alongside, the water streamed out of the visor and the oil settled everywhere inside the visor, also on the bow ramp which forms the aft inside of the visor.
The water streaming out of the visor was observed by many passengers when the vessel was alongside in Stockholm with closed visor and, among others, also by the skipper of the Sandhamn pilot boat as well as by several pilots when the ferry was slowing down during the approach to the pilot boat.
The bow wave became smaller and the water streamed at once out of the visor. (See Subchapter 12.4.4.)
It is obvious that at sea inside the visor the conditions in a partly filled ballast water tank did exist with resultant sloshing effects causing additional loads on hinges and locking devices and vibrations to the whole visor, the consequences of which are described in Subchapter 34.3.(2) The bow ramp, its locking devices, hinges and rubber packings:
The bow ramp was part of the upper extension of the collision bulkhead above bulkhead deck and as such had to be mandatorily watertight based on the stringent requirements of SOLAS 1974. This, however, was obviously not the case because back to December 1993 there is reliable evidence that frequently there had been a lot of water on the car deck - see Subchapter 12.4.4. There is also a lot of evidence that the bow ramp was severely misaligned and - in fact - was no more connected to the port outer and probably also inner hinges for some time - see Subchapter 12.4.3. It has thus to be assumed that the water penetrated onto the car deck from the visor, which was filled up to the outside water level, as soon as the vessel was on full speed and the bow wave had risen to ca. 2.5 m height. Since even in calm sea the visor was filled above the level of the 3rd stringer, which is above the car deck level, it is apparent that even in good weather conditions water was streaming onto the car deck. Most of it was most probably absorbed by the 12 scuppers at each side, some of which, however, were reportedly always blocked by stones and other debris.
Consequently it has to be assumed that there was already a deadly connection between the always water-filled and -refilled visor and the large, open car deck via the open port lower edge of the bow ramp since some time before the last departure.The locking devices of the bow ramp were difficult to lock and, once locked, even more difficult to unlock. There is lots of evidence from truck drivers and other passengers having waited for hours on the car deck watching the fruitless attempts to open respectively close the securing bolts hydraulically and, finally, watching them being opened by flame cutting of the upper parts of the mating boxes, which should have been subsequently rewelded but frequently were not. When the crew did not succeed in closing the bolts hydraulically, they tried it by hammering, even by using sledge-hammers and very often gave up, i.e. the ramp remained - at least partly - unsecured! (See Subchapters 12.4.3 / 12.4.5.)
All this led, of course, in time to a considerable reduction of the load-carrying capacity similar as with the hydraulic side locks of the visor. Also the hinges of the bow ramp were severely affected, in particular the port outer hinge. This very heavy hinge arrangement was already damaged before the vessel was taken over by her new owners in January 1993, because the old Finnish crew had already requested renewal at the planned yard time in January 1993 - see Subchapter 6.5.1. Nothing was done by N&T and since the mates of the ESTONIA performed the loading and discharging of the cars and trucks reportedly rather carelessly, the vessel very often had a list during loading or unloading which finally broke the port hinge completely according to the report of a truck driver being an eye witness.
The crew had severe problems to lift up the ramp at all which was only possible after some temporary measurements had been carried out. Ever since, the misalignment of the ramp increased visibly and the problems were growing daily.
Also the rubber packings around the car deck opening, which should be sealed tight by a properly closed and locked bow ramp, apparently did no more seal watertight since some considerable time already, because the last Finnish crew had ordered 10 m of rubber packing to be renewed at the next yard time which was planned for January 1993 - see Subchapter 3.4. - as mentioned before. This was more than half of the total length of the rubber packings, but also these packings were never renewed.


1
When Earth is shaken with her (final) earthquake
2
And Earth yieldeth up her burdens,
3
And man saith: What aileth her ?
4
That day she will relate her chronicles,
5
Because thy Lord inspireth her.
6
That day mankind will issue forth in scattered groups to be shown their deeds.
7
And whoso doeth good an atom's weight will see it then,
8
And whoso doeth ill an atom's weight will see it then.


Current time is: {{ time }}
Voltage: {{ voltage }}V, Current: {{ current }}A
Energy: {{ energy }}Ah over {{ duration }}
Home


* "F" (file) specs define files and other i/o devices F ARMstF1 IF E K Disk Rename(ARMST:RARMST) * "D" (data) specs are used to define variables D pCusNo S 6p D pName S 30a D pAddr1 S 30a * The "chain" command is used for random access of a keyed file C pCusNo chain ARMstF1 * If a record is found, move fields from the file into parameters C if %found C eval pName = ARNm01 C eval pAddr1 = ARAd01 C eval pAddr2 = ARAd02 C eval pCity = ARCy01 C endif * RPG makes use of switches. One switch "LR" originally stood for "last record" * LR flags the program and its dataspace as removable from memory C eval *InLR = *On * "F" (file) specs define files and other i/o devices FARMstF1 IF E K Disk Rename(ARMST:RARMST) * "D" (data) specs are used to define variables and parameters * The "prototype" for the program is in a separate file * allowing other programs to call it /copy cust_pr * The "procedure interface" describes the *ENTRY parameters D getCustInf PI D pCusNo 6p 0 const D pName 30a D pAddr1 30a D pAddr2 30a D pCity 25a D pState 2a D pZip 10a /free // The "chain" command is used for random access of a keyed file chain pCusNo ARMstF1; // If a record is found, move fields from the file into parameters if %found; pName = ARNm01; pAddr1 = ARAd01; pAddr2 = ARAd02; pCity = ARCy01; pState = ARSt01; pZip = ARZp15; endif; // RPG makes use of switches. One switch "LR" originally stood for "last record" // LR actually flags the program and its dataspace as removable from memory. *InLR = *On; /end-free H main(GetCustInf) D ARMSTF1 E DS P GetCustInf B D GetCustInf PI extpgm('CUS001') D inCusNo like(arCNum) const D outName like(arName) D outAddr1 like(arAdd1) D outAddr2 like(arAdd2) D outCity like(arCity) D outState like(arStte) D outZip like(arZip) /free exec sql select arName, arAdd1, arAdd2, arCity, arStte, arZip into :outName, :outAddr1, :outAddr2, :outCity, :outState, :outZip from ARMSTF1 where arCNum = :inCusNo fetch first 1 row only with CS use currently committed; /end-free P GetCustInf E


The sites we’ve built to display on a desktop, smartphone, or a tablet today could be on a TV Screen, coffee table display, or mega space yacht projection system tomorrow. Do yourself a favor and heed the advice of the Dao: A fully-scalable web1
For a solid base we use default font settings to allow elements to display in their natural size determined by the browser's default stylesheet. This makes for lighter CSS and more flexibility in the markup you choose to use. We also ensure unit values for line-heights are never used per the recommendations of Eric Meyer.
Establish clearly distinguishable heading levels with consistent font-sizes over randomly chosen values. Choose a type hierarchy that is harmonious and consistent with your project. In order to do so we suggest using a modular scale that calculates sizes via a ratio ensuring your design and typography can relate in a meaningful way. There’s an excellent calculator for this at modularscale.com.
Just like in print, don’t use the darkest black available in your body text (#000
). Instead, go for something softer, like #444
. You can use a slightly darker color for titles like (#222
) for example. Since these values are considered a de facto standard in practice, they're not necessarily ordained by law.
#000
#222
#444
The word-wrap CSS property is used to specify whether or not the browser may break lines within words in order to prevent overflow when an otherwise unbreakable string is too long to fit in its containing box.
On the web, paragraphs are commonly set in blocks, with top and bottom margins. Historically, paragraphs are set using indentation, which makes it easier to scan long-form text and are (we think) more conducive to readability.
For the curious, here's a few example sites using the paragraph indentation approach we've chosen for our starter kit…Mark Boulton, Nice Web Type, Andy Rutledge and Nathan Ford just to name a few.
Authors choosing to opt out of our default styling may feel free to change the boolean variable in the Sass port to remove this opinionated default as depicted in the example below. CSS people you'll have to settle for the manual route to customize.
Responsive or not, there’s no reason why we shouldn’t all be designing and building sites on flexible foundations. In a fluid layout, browser width and typographic measure are linked: the wider the viewport, the more characters per line. Keeping in mind that a range of 45-75 characters per line is generally accepted as safe for comfortable reading, there are a few things that can be done to avoid extra long lines of text in fluid layouts. Robert Bringhurst recommends for us to leave at least two characters behind and take at least three forward.
Small caps help to make abbreviations way easier to read but won’t stand out from the text. We highly suggest this bit of typographic flare with your content. True small capitals are now possible on the web, but alas they are still difficult and will also depend on the type face in use. Definitely check out Open Typography for those typefaces and services that provide authentic small caps.
A “Drop Cap” is the art of using an uppercase glyph to mark the start of copy. A technique that has been around for almost two thousand years!
With the unicode-range
property we can avoid using verbose markup and only target the characters we like according to the unicode unique identifier. We also harness the power of the %placeholder
in Sass allowing like minded selectors to string together this shared property in a DRY way from one single declaration. Copy and paste the Sass below into Codepen and check out the output for yourself. Hint: create multiple classes.
The small
element is used to represent side comments or what’s commonly referred to as ‘small print’: disclaimers, caveats, legal restrictions, or copyrights. It can also be used for attributions or satisfying licensing requirements.
Monospace
fonts just as you desire for all your code block dreams! Monospace fonts or “fixed pitch” fonts, contain characters that all have the same character width. ‘l’, ‘1’ and ‘i’ are easily distinguished with monospace, ‘0’, ‘o’ and ‘O’ are easily distinguished and clear punctuation characters, especially braces, parenthesis and brackets.
The blockquote element represents a section that is being quoted from another source. Good blockquotes should include a citation, but one is not required. Stylistically, these can look a lot like pull-quotes by using :before
and :after
pseudo elements for the curly quotes, or, authors can include them inline.
The contents of blockquote
are limited to headings and paragraphs. header
, footer
, or cite
tags are not allowed. For more examples, see A List Apart's sample blockquote patterns.

Pull quotes are tricky, but with this little ditty they’re not so difficult or tedious anymore. The example is an improvement based upon the 24 ways article discussing swooshy curly quotes without images. This particular example depicted takes advantage of psuedo selectors and the
tag.

The sites we’ve built to display on a desktop, smartphone, or a tablet today could be on a TV Screen, coffee table display, or mega space yacht projection system tomorrow. Do yourself a favor and heed the advice of the Dao: A fully-scalable web1

↩

The dl element is for another type of list called a definition list. Instead of list items, the content of a dl consists of dt (Definition Term) and dd (Definition Description) pairs.
TypePlate offers several different patterns for definition lists. In all three of the examples below, the contents of dts are wrapped in b tags, and a class of .micro is given to the contents of dds. First is the default format for definitions lists.
dl
.dt
may be followed by multiple dd
s.

This is a term

this is the definition of that term, which both live in a dl.

Another Term

And it gets a definition too, which is this line

This is a 2nd definition for a single term. A dt may be followed by multiple dds.

The second format for definition lists is lining. This style is more robust, with support for multiple terms defined by a single definition, and applies proper punctuation (: ,) where appropriate:
dl
.dt
terms may stand on their own without an accompanying dd
, but in that case they share descriptions with the next available dt
. You may not have a dd
without a parent dt
.

This is a term

this is the definition of that term, which both live in a dl.

Another Term

And it gets a definition too, which is this line

 this is a 2nd definition for a single term.

Term

Other Defined Term

dt terms may stand on their own without an accompanying dd, but in that case they share descriptions with the next available dt. You may not have a dd without a parent dt.

The third format for definition lists is dictionary. This style is more a formal, applying proper punctuation where necessary and includes ordinal indicators:
dl
.dt
terms may stand on their own without an accompanying dd
, but in that case they share descriptions with the next available dt
. You may not have a dd
without a parent dt
.

This is a term

this is the definition of that term, which both live in a dl.

Another Term

And it gets a definition too, which is this line

 this is a 2nd definition for a single term.

Term

Other Defined Term

dt terms may stand on their own without an accompanying dd, but in that case they share descriptions with the next available dt. You may not have a dd without a parent dt.


PASSION OF MIND
Reviewed by Harvey Karten Paramount Classics/Lakeshore Entertainment Director: Alain Berliner Writer: Ronald Bass, David Field Cast: Demi Moore, Sinead Cusack, William Fichtner, Peter Riegert, Stellan Skarsgard
Some spokespersons for the feminist movement have promised that women could have it all. They could be hard-hitting top executives with corner suites on the upper floors of Manhattan skyscrapers and come home to loving husbands, kids, dogs and picket fences. Alas, in most cases, this was not to be. Women with MBAs who donned business suits felt guilty leaving their kids with nannies, and those who stayed home to take care of their loved ones felt they could have done a lot more with their lives. With a script by Ronald written a decade ago with that dilemma in mind, "Passion of Mind" gives the predicament a visual, metaphoric presentation, contrasting the life of a low-key book reviewer draped in casual threads living with her two daughters in the south of France with that of a high-power literary agent going about her fast-moving Manhattan business in smashing designer clothes. The kicker is that the two women are actually one and the same: yet another case of split personality disorder--investigated in a sluggish, cerebral story that never springs to life but which promises a payoff that the more prescient moviegoers could probably predict.
The premise designed to serve as a hook for the audience is the nature of dreams. As you read these words, how do you know you that you're not dreaming? You pinch yourself? This does not always work. Here is my solution: say to yourself, "Is this a dream?" Your mere ability to consider that concept will indicate to you that this is reality. Dreams may seem real enough when they are in progress, but that is only because you have not been able to ask yourself this simple question.
For Marty/Marie (Demi Moore), though, that technique does not work. When she falls asleep in France, she has visions of a separate life in New York, where she looks about the same and acts pretty much like her double in Provence, and even runs into the same problems in her romantic life. When she beds down in New York, she is soon back in France. And so it goes, day after day, night after night. In a sense she is not the hapless situation that director Alain Berliner might presume it to be. After all, how else can you enjoy the delights of both worlds even faster than you could travel from one to the other on the Concorde? Folks in the audience might be tempted to say, "Live with the problem. Lighten up and enjoy yourself--in both worlds. And don't worry too much about which is real."
In New York, Marty, the literary agent, is gradually falling for her accountant, the shy, even nerdy Aaron (William Fichtner), whose idea of romantic pursuit is to make dates to meet in Central Park on Sunday mornings. In Provence, the man who captures Marie's interest is William (Stellan Skarsgard), who takes an unusual interest in Marie's kids, so much so that you wonder whether he is feigning this attention to win his lady over. Marie's psychotherapist in France, Dr. Langer (Joss Ackland), is of little help, but her friend, Jessie (Sinead Cusack), advises her to give in to her longing for love. Meanwhile her New York therapist, Dr. Peters (Peter Riegert), strongly cautions Marty to keep her double life a secret from Aaron, lest Aaron bolt from a person with an all- consuming psychosis.
As a romance, the story displays nothing of the passion we'd expect from a woman who has been without a man for years. (Her husband in France had died two years earlier while in New York she seems to avoid dating altogether.) The thirty-seven year old Demi Moore just doesn't fit together with the older Stellan Skarsgard, who comes across as avuncular rather than appetitive. And no woman with any taste could fall for a guy like William Fichtner who sports an unusually scruffy beard, the hair pouring down to his neck without symmetry. For every woman needing a psychiatrist to resolve her duplicate life there's another who'd be sensible enough to enjoy doubling her pleasure--just like the twins in the old Doublemint gum commercials. Whether dreaming of New York of fantasizing Provence, Moore sleepwalks through this lethargic role in a film whose value lies principally in Eduardo Serra's picture-postcard shots of the Gold Triangle area of Gordes, Bonnieux and Lacoste in the Luberon valley of Provence.
Rated PG-13. Running time: 107 minutes. (C) 2000 by Harvey Karten<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


In the last few weeks, there’s been a lot of public attention focused on the PANSTARRS comet. It’s now visible to the naked eye if you’re in the right place at the right time. Sounds tricky right? Fortunately, one great piece of software called Stellarium that gives you a good idea of where to look based your location and time, visually. It couldn’t get much easier. The downside is that comets are not installed with Stellarium by default. Below I will outline the steps needed to get Stellarium comet-friendly. If you don’t have Stellarium, you can get it for free here.
Turning on the comet wisdom
Stellarium comes with a plugin installed to show you comet locations in the sky relative to where you are at any time. Here’s how we do it. Go to configuration window > solar system editor > options > configure > import orbital elements in MPC format > select the type > comets > select a source from the list > MPC’s list of observable comets and then hit get orbital elements. Then search for CL 2011 L4 (PANSTARRS). Got that? I’m impressed ;-). In case that was a bit too dense, here’s a video.


|
||||||||||
| PREV LETTER NEXT LETTER | FRAMES NO FRAMES |
MWDumpReaderFactory.addBeforeTimestampFilter(String)
method, except
for the fact that here only the revisions contributed after the given timestamp are considered valid.
|
||||||||||
| PREV LETTER NEXT LETTER | FRAMES NO FRAMES |


Activates the next sheet in the active workbook.
Syntax
WORKBOOK.NEXT( )
Remarks
If the last sheet in the workbook is active, this function has no effect.
This function skips over hidden sheets in the workbook.
Return to index


# File test/tc_disassembly.rb, line 7 def test_simple assert(/RTS/.match(D65.disassemble("\x60")),"disassembly of 0x60 should be RTS") end


Text control
`content.label = undefined` and `content.placeholder = undefined`
`content.label` is NOT `undefined` and `content.placeholder = undefined`
`content.label = undefined` and `content.placeholder` is NOT `undefined`
`content.label` is NOT `undefined` and `content.placeholder` is NOT `undefined`


@(suggestionTemplateForm: Form[SuggestionTemplate])(implicit messages: Messages) @admin("Creating a new suggestion", "suggestionTemplates") {


Zend Framework
LICENSE
This source file is subject to the new BSD license that is bundled with this package in the file LICENSE.txt. It is also available through the world-wide-web at this URL: http://framework.zend.com/license/new-bsd If you did not receive a copy of the license and are unable to obtain it through the world-wide-web, please send an email to<EMAIL_ADDRESS>so we can send you a copy immediately.
__construct(
$params
)
:
void
Public constructor
In addition to the parameters of Zend_Mail_Part::__construct() this constructor supports: - flags array with flags for message, keys are ignored, use constants defined in Zend_Mail_Storage
| Name | Type | Description |
|---|---|---|
| $params |
| Exception | Description |
|---|---|
| \Zend_Mail_Exception |
__get(
string $name
)
:
string
Getter for mail headers - name is matched in lowercase
Inherited from: \Zend_Mail_Part::__get()This getter is short for Zend_Mail_Part::getHeader($name, 'string')
| Name | Type | Description |
|---|---|---|
| $name | string | header name |
| Type | Description |
|---|---|
| string | value of header |
| Exception | Description |
|---|---|
| \Zend_Mail_Exception |
__isset(
$name
)
:
boolean
Isset magic method proxy to hasHeader
Inherited from: \Zend_Mail_Part::__isset()This method is short syntax for Zend_Mail_Part::hasHeader($name);
| Name | Type | Description |
|---|---|---|
| $name | string |
| Type | Description |
|---|---|
| boolean |
__toString(
)
:
string
magic method to get content of part
Inherited from: \Zend_Mail_Part::__toString()| Type | Description |
|---|---|
| string | content |
_cacheContent(
)
:
null
Cache content and split in parts if multipart
Inherited from: \Zend_Mail_Part::_cacheContent()countParts(
)
:
int
Count parts of a multipart part
Inherited from: \Zend_Mail_Part::countParts()| Type | Description |
|---|---|
| int | number of sub-parts |
current(
)
:
\Zend_Mail_Part
implements Iterator::current()
Inherited from: \Zend_Mail_Part::current()| Type | Description |
|---|---|
| \Zend_Mail_Part | current part |
getChildren(
)
:
\Zend_Mail_Part
implements RecursiveIterator::getChildren()
Inherited from: \Zend_Mail_Part::getChildren()| Type | Description |
|---|---|
| \Zend_Mail_Part | same as self::current() |
getContent(
$stream
=
null
)
:
string
Body of part
Inherited from: \Zend_Mail_Part_File::getContent()If part is multipart the raw content of this part with all sub parts is returned
| Name | Type | Description |
|---|---|---|
| $stream |
| Type | Description |
|---|---|
| string | body |
| Exception | Description |
|---|---|
| \Zend_Mail_Exception |
getFlags(
)
:
array
get all set flags
| Type | Description |
|---|---|
| array | array with flags, key and value are the same for easy lookup |
getHeader(
string $name, string $format
=
null
)
:
string|array
Get a header in specificed format
Inherited from: \Zend_Mail_Part::getHeader()Internally headers that occur more than once are saved as array, all other as string. If $format is set to string implode is used to concat the values (with Zend_Mime::LINEEND as delim).
| Name | Type | Description |
|---|---|---|
| $name | string | name of header, matches case-insensitive, but camel-case is replaced with dashes |
| $format | string | change type of return value to 'string' or 'array' |
| Type | Description |
|---|---|
| stringarray | value of header in wanted or internal format |
| Exception | Description |
|---|---|
| \Zend_Mail_Exception |
getHeaderField(
string $name, string $wantedPart
=
0, string $firstName
=
0
)
:
string|array
Get a specific field from a header like content type or all fields as array
Inherited from: \Zend_Mail_Part::getHeaderField()If the header occurs more than once, only the value from the first header is returned.
Throws a Zend_Mail_Exception if the requested header does not exist. If the specific header field does not exist, returns null.
| Name | Type | Description |
|---|---|---|
| $name | string | name of header, like in getHeader() |
| $wantedPart | string | the wanted part, default is first, if null an array with all parts is returned |
| $firstName | string | key name for the first part |
| Type | Description |
|---|---|
| stringarray | wanted part or all parts as array($firstName => firstPart, partname => value) |
| Exception | Description |
|---|---|
| \Zend_Exception, | Zend_Mail_Exception |
getHeaders(
)
:
array
Get all headers
Inherited from: \Zend_Mail_Part::getHeaders()The returned headers are as saved internally. All names are lowercased. The value is a string or an array if a header with the same name occurs more than once.
| Type | Description |
|---|---|
| array | headers as array(name => value) |
getPart(
int $num
)
:
\Zend_Mail_Part
Get part of multipart message
Inherited from: \Zend_Mail_Part_File::getPart()| Name | Type | Description |
|---|---|---|
| $num | int | number of part starting with 1 for first part |
| Type | Description |
|---|---|
| \Zend_Mail_Part | wanted part |
| Exception | Description |
|---|---|
| \Zend_Mail_Exception |
getSize(
)
:
int
Return size of part
Inherited from: \Zend_Mail_Part_File::getSize()Quite simple implemented currently (not decoding). Handle with care.
| Type | Description |
|---|---|
| int | size |
getTopLines(
)
:
string
return toplines as found after headers
| Type | Description |
|---|---|
| string | toplines |
hasChildren(
)
:
bool
implements RecursiveIterator::hasChildren()
Inherited from: \Zend_Mail_Part::hasChildren()| Type | Description |
|---|---|
| bool | current element has children/is multipart |
hasFlag(
mixed $flag
)
:
bool
check if flag is set
| Name | Type | Description |
|---|---|---|
| $flag | mixed | a flag name, use constants defined in Zend_Mail_Storage |
| Type | Description |
|---|---|
| bool | true if set, otherwise false |
headerExists(
string $name
)
:
boolean
Check wheater the Mail part has a specific header.
Inherited from: \Zend_Mail_Part::headerExists()| Name | Type | Description |
|---|---|---|
| $name | string |
| Type | Description |
|---|---|
| boolean |
isMultipart(
)
:
bool
Check if part is a multipart message
Inherited from: \Zend_Mail_Part::isMultipart()| Type | Description |
|---|---|
| bool | if part is multipart |
key(
)
:
string
implements Iterator::key()
Inherited from: \Zend_Mail_Part::key()| Type | Description |
|---|---|
| string | key/number of current part |
next(
)
:
null
implements Iterator::next()
Inherited from: \Zend_Mail_Part::next()| Type | Description |
|---|---|
| null |
rewind(
)
:
null
implements Iterator::rewind()
Inherited from: \Zend_Mail_Part::rewind()| Type | Description |
|---|---|
| null |
valid(
)
:
bool
implements Iterator::valid()
Inherited from: \Zend_Mail_Part::valid()| Type | Description |
|---|---|
| bool | check if there's a current element |


Nilsson makes 26 saves as Senators beat Flyers 2-1
OTTAWA, Ontario (AP) - The Ottawa Senators made up for a bad start with a solid ending.

Ottawa’s Colin White took a double minor for high-sticking Claude Giroux with just over four minutes remaining in the game. The Flyers pulled Carter Hart for a two-man advantage, but were unable to get the equalizer.
TOP STORIES
Adam Schiff cracking under 'point of order' pressure
Obama officials wary of Hunter Biden's big-money job, ousted Ukraine ambassador admits
Evangelist Franklin Graham calls impeachment hearing 'a day of shame for America'
“That was maybe our worst start of the year on the first three shifts,” Senators coach D.J. Smith said. “We just weren’t ready or maybe they were ready, one of the two, but after that first five minutes I thought we were really competitive and played hard.”
Tyler Ennis also scored for the Senators (8-10-1), who won back-to-back games for just the second time this season.
Tyler Pitlick scored for the Flyers (10-6-3), who lost in regulation for the first time since Oct. 29. Hart stopped 19 shots.
“We should still find a way to win a game,” Philadelphia’s Jakub Voracek said. “I think we have a better team. Nothing against Ottawa, they played a good game, but we have to find a way to win those games.”
The Senators got both of their goals in the second.
Ennis tied it at 1 with a power-play goal 13:12 into the period. Ennis has three of the Senators‘ five power-play goals this season.
“Special teams and good goaltending got us the win,” Ennis said. “The power play has been struggling lately, but it was a factor in us winning and especially the penalty kill as well.”
Chlapik made it 2-1 with 2:51 left. It was his second of the season.
The fourth line of Chlapik, Chris Tierney and Bobby Ryan was solid for the Senators, creating a number of chances and drawing the penalty that led to Ennis’ goal.
Pitlick gave Philadelphia the lead just two minutes into the game, beating Nilsson with a wrist shot.
The Flyers had a number of great chances in the first period, but Nilsson was solid. James Van Riemsdyk had two scoring chances on the same shift to open the game.

“I think everyone knows right now what we, as a team, need to do to win hockey games,” he said. “We can’t out-skill the opponent. We have to beat every opponent every night on work ethic and we have to work extremely hard and we have to work harder than our opponents.”
Philadelphia went 0 for 5 on the power play.
“Our execution was a little bit off,” Flyers coach Alain Vigneault said. “At the end the power play has the opportunity to tie us the game, had a lot of possession time in that four minutes, but no real good look that I would say.”
NOTES: Ottawa F Logan Brown returned to the lineup after missing the last six games with an upper-body injury.
UP NEXT
Flyers: Host New York Islanders on Saturday night.
Senators: At Buffalo on Saturday night.
More AP NHL: https://apnews.com/NHL and https://twitter.com/AP_Sports
Sign up for Daily Newsletters
Copyright © 2019 The Washington Times, LLC.
Please read our comment policy before commenting.


Hello My Dear, I am mrs rose savimbi please i need your help since after the incidence that lead to the death of my late husband MRJONAS SAVIMBI of unita of Angola . I know we have not met before but I am contacting you with due sense of humanity responsibility and the few awareness that you will give it a mutual understanding I am soliciting for an assistance to move the sum $24 million USD to your country for investment The fund is presently in a security company in Holland for safety since on the 12- 2- 1999. The real content was not declared as it was kept as photographic equipment I need you as partner to assist in transferring the fund and provide good investment plans for it. The fund will be under your investment control for three years during which only the profit will be shared annually 70% for me and 30% for you annually I am a Christian with the fear of GOD in any thing I am doing so please I want us to build trust to each other. you should always reply me through this new email address if you are interested<EMAIL_ADDRESS>Thanks in anticipation of your response Best regards MRS ROSE SAVIMBI Ms. Savimbi, _____________________________________________ Free email with personality! Over 200 domains! http://www.MyOwnEmail.com Looking for friendships,romance and more? http://www.MyOwnFriends.com


sillySally
Interests
Math Computer Science Physics Science Technology Sport Science
dorkyDave
flirtyFrancis
beardedBill
stachioSergio


UNDER CONSTRUCTION
My website is currently under construction. Should be back shortly. Thank you for your patience.
NOTIFY ME
facebook
twitter
instagram
linkedin
github
hackaday/a>


Landing Page
Special Projects
This story is part of a series of specially designed stories that represents some of the best journalism The Post has to offer. Check out the rest of the special projects here.
03.08.18
When Ohio University students came to campus in the 1960s, they were presented with handbooks that outlined rules, expectations and information about campus services. The women’s handbook, titled “You, the Coed,” also featured a section with social tips, curfew hours and advice on how to be a lady.
“The most important thing about being a college woman is being a lady,” page 13 of the 1964-65 version of “You, the Coed” reads. “The coed is ladylike in the classroom, at parties and on campus.”
Kaitlin Coward | MANAGING EDITOR
That handbook is 76 pages long, while the men’s one, called “You the College Man,” is 29 pages long.
“A college man is many things, but above all else, he is a scholar,” the 1964-65 version of “You the College Man” reads.
Female students also had to follow a strict set of rules, including a curfew, referred to as “hours.” Male students didn’t have “hours.”
“You, the Coed” stated that women were not allowed to leave their housing units before 7 a.m. Hours were broken down by what year a female student was in college. The curfew for Sunday through Thursday was 10 p.m. for freshmen, 10:30 p.m. for sophomores and juniors, and 11 p.m. for seniors. On Friday and Saturday, the curfew for all female students was 12:30 a.m.
Those students could get permission to stay out later during the week based on their previous semester’s GPAs. If women had a GPA of greater than 3.5, they would receive an unlimited number of “lates” — except for freshmen, who were limited to four.
In the late 1960s, about 850 female students protested the curfew hours and participated in a walkout. They gathered outside Templeton-Blackburn Alumni Memorial Auditorium at 11:15 p.m. and clapped, stomped and cheered until shortly after midnight.
At the time, all women under 21 and juniors and seniors without parental permission had to follow the curfew, which was set at midnight on weekdays.
“Women, it’s a minute after 12 and we’re liberated,” Alicia Woodson, a leader of the Women’s Hours Steering Committee, said in a previous Post report.
The curfew was abolished in Fall Quarter 1971 as part of a new policy former OU President Claude Sowle approved, according to the April 1971 Ohio University Alumni Journal.
In the two pages of notes on social tips, that section highlighted how women should not ignore men’s attempts to light their cigarettes. They also weren’t allowed to wear pin curls, rollers and scarves in lounges or on campus.
Women were expected to wear dresses, skirts, blouses and sweaters on weekdays, and men were expected to wear long pants and collared shirts. Additionally, women were not supposed to put on makeup or comb their hair in public.
“High standards or personal hygiene and an attractive appearance are expected of all women,” page 20 of “You, the Coed” reads.
“You the College Man” described the dress standard for all students and stressed the importance of neatness, cleanliness and appropriateness.
“Both in college and later in life, a man is often judged by his appearance,” page 14 of “You, the College Man” reads.
Women were also instructed to not accept dates if they didn’t want them and to never cancel dates. The handbook presented women with suggestions on how to do introductions and how to write formal invitations, as well. It concluded with a detailed breakdown of all the sororities and residence halls.
Landing Page
This story is part of a series of specially designed stories that represents some of the best journalism The Post has to offer. Check out the rest of the special projects here.


7.4. The qr/⋯/ Operator and Regex ObjectsIntroduced briefly in Chapter 2 and Chapter 6 (☞76; 277), qr/⋯/ is a unary operator that takes a regex operand and returns a regex object. The returned object can then be used as a regex operand of a later match, substitution, or split, or can be used as a sub-part of a larger regex. Regex objects are used primarily to encapsulate a regex into a unit that can be used to build larger expressions, and for efficiency (to gain control over exactly when a regex is compiled, discussed later). As described on page 291, you can pick your own delimiters, such as qr{⋯} or qr!⋯!. It supports the core modifiers /i, /x, /s, /m, and /o. 7.4.1. Building and Using Regex ObjectsConsider the following, with expressions adapted from Chapter 2 (☞76): my $HostnameRegex = qr/ [-a-z0-9]+( ? :\.[-a-z0-9]+)+\.(?: com|edu|info)/i; my $HttpUrl = qr{ http:// $HostnameRegex \b # Hostname (?: / [ - a-z0-9R:\@&? = +,.!/~*'%\$]* # Optional path (?<![.,?!]) # Not allowed to end with [.,?!] )? }ix; The first line encapsulates our simplistic hostname-matching regex into a regular-expression object, and saves it to the variable $HostnameRegex. The next lines then use that in building a regex object to match an HTTP URL, saved to the variable $HttpUrl. Once constructed, they can be used in a variety of ways, such as if ($text =~ $HttpUrl) { print "There is a URL\n"; } to merely inspect, or perhaps while ($text =~ m /($HttpUrl)/g) { print "Found URL: $1\n"; } to find and display all HTTP URLs. Now, consider changing the definition of $HostnameRegex to this, derived from Chapter 5 (☞205): my $HostnameRegex = qr{ # One or more dot-separated parts⋯ (?: [a-z0-9]\. | [a-z0-9][-a-z0-9]{0,61}[a-z0-9]\. ) * # Followed by the final suffix part⋯ (?: com|edu|gov|int|mil|net|org|biz|info|⋯|aero|[a-z][a-z] ) }xi; This is intended to be used in the same way as our previous version (for example, it doesn't have a leading ^ and trailing $, and has no capturing parentheses), so we're free to use it as a drop-in replacement. Doing so gives us a stronger $HttpUrl. <IP_ADDRESS>. Match modes (or lack thereof) are very stickyqr/⋯/ supports the core modifiers described on page 292. Once a regex object is built, the match modes of the regex it represents can't be changed, even if that regex object is used inside a subsequent m/⋯/ that has its own modifiers. For example, the following does not work: my $WordRegex = qr/\b \w+ \b/; # Oops, missing the /x modifier! if ($text =~ m/^($WordRegex)/x) { print "found word at start of text: $1\n"; } The /x modifiers are used here ostensibly to modify how $WordRegex is applied, but this does not work because the modifiers (or lack thereof) are locked in by the qr/⋯/ when $WordRegex is created. So, the appropriate modifiers must be used at that time. Here's a working version of the previous example: my $WordRegex = qr/\b \w+ \b/x; # This works! if ($text =~ m/^($WordRegex)/) { print "found word at start of text: $1\n"; } Now, contrast the original snippet with the following: my $WordRegex = '\b \w+ \b'; # Normal string assignment if ($text =~ m/^($WordRegex)/x) { print "found word at start of text: $1\n"; } Unlike the original, this one works even though no modifiers are associated with $WordRegex when it is created. That's because in this case, $WordRegex is a normal variable holding a simple string that is interpolated into the m/⋯/ regex literal. Building up a regex in a string is much less convenient than using regex objects, for a variety of reasons, including the problem in this case of having to remember that this $WordRegex must be applied with /x to be useful. Actually, you can solve that problem even when using strings by putting the regex into a mode-modified span (☞135) when creating the string: my $WordRegex = '(?x:\b \w+ \b)'; # Normal string assignment if ($text =~ m/^($WordRegex)/) { print "found word at start of text: $1\n"; } In this case, after the m/⋯/ regex literal interpolates the string, the regex engine is presented with ^((?x:\b•\w+•\b)), which works the way we want. In fact, this is what logically happens when a regex object is created, except that a regex object always explicitly defines the "on" or "off" for each of the /i, /x, /m, and /s modes. Using qr/\b•\w+•\b/x creates (?x-ism:\b•\w+•\b). Notice how the mode-modified span, (? x -ism:⋯), has /x turned on, while /i, /s, and /m are turned off. Thus, qr/⋯/ always "locks in" each mode, whether given a modifier or not. 7.4.2. Viewing Regex ObjectsThe previous paragraph talks about how regex objects logically wrap their regular expression with mode-modified spans like (?x-ism:⋯). You can actually see this for yourself, because if you use a regex object where Perl expects a string, Perl kindly gives a textual representation of the regex it represents. For example:
% perl -e 'print qr/\b \w+ \b/x, "\n"'
(?x-ism:\b \w+ \b)
Here's what we get when we print the $HttpUrl from page 304: (?ix-sm: http:// (?ix-sm: # One or more dot-separated parts⋯ (?: [a-z0-9]\. | [a-z0-9][-a-z0-9]{0,61}[a-z0-9]\. ) * # Followed by the final suffix part⋯ (?: com|edu|gov|int|mil|net|org|biz|info|⋯|aero|[a-z][a-z] ) ) \b # hostname (?: / [ - a-z0-9R:\@&? =+,.!/~*'%\$]* # Optional path (?<![.,?!]) # Not allowed to end with [.,?!] )? ) The ability to turn a regex object into a string is very useful for debugging. 7.4.3. Using Regex Objects for EfficiencyOne of the main reasons to use regex objects is to gain control, for efficiency reasons, of exactly when Perl compiles a regex to an internal form. The general issue of regex compilation was discussed briefly in Chapter 6, but the more complex Perl-related issues, including regex objects, are discussed in "Regex Compilation, the /o Modifier, qr/⋯/, and Efficiency" (☞348). |


Contains implementation of public parts of IRendererMarshaller.
Global function for creating the RendererMarshaller. This method should generally not be called. Use the ICausticFactory to create new Caustic objects.
Returns the newly created RendererMarshaller.
{Link:import Rendering.Caustic.IRendererMarshaller;{Rendering/Caustic/IRendererMarshaller.cpp}}


To enter this website please confirm your age.
This content is age restricted. Please confirm your entry.
Which planet are you from?


Learning resources for web developers can be found all over the internet. Try out web.dev, w3schools.com or our MDN web docs.


=DDETerminate(CHANNEL)
* this command closes the channel which you opened using DDEInitiate.
for example, the following program fragment closes channel iCh1:
=DDETerminate(iCh1)


2004-02-22 - work-in-progress
The following is a first bash at an XHTML representation of w6. It's an expandable outline, so clicking on the grey squares should expand/contract it. I'm working in IE, but I'll try and keep it working in Mozilla, it should fall back on being a simple outline list in Lynx etc. Be sure and view the source. There's an XSLT stylesheet to generate the RDF (after pretty-printing), and another (xow2bookmarks.xsl) that puts the data in a format suitable for importing into Mozilla/Firefox (w6bm.html). I'm working on making this in-place editable, so it can be used for rapid input/annotation. Lots to do...
See also: XHTML Outlines and W6 notes on my blog, also XO and GRDDL
The icons correspond to who, what, why, when, where, how
W6
An easy ontology
Using an OWL Ontology
The Web Ontology Language


Porsche 911 manual here in 2020
The three-pedal 911 has been confirmed for Australia, but Porsche hasn't locked in pricing or which models will get the option.
by Scott Collie- shares
Porsche has confirmed a manual version of the latest 911 will be offered in Australia from next year, but the company hasn't confirmed whether it will be offered on the base Carrera.
As before, the manual offered in non-GT 911 models will be a seven-speeder. Porsche says the 100km/h sprint takes around four seconds, and the manual is about 10kg lighter than the dual-clutch PDK automatic.
Although it locked in a 2020 launch for the three-pedal 911, Porsche Australia says it has "nothing to confirm at this stage" about which models will get the option.
In the USA, Porsche will only offer the option on the more expensive, more powerful 911 Carrera S and 4S.
The 'stick shift' is a no-cost option in America, and comes with the Sport Chrono pack and its active engine mounts, auto rev-matching, and a wheel-mounted drive mode switch as standard.
Were Porsche to follow in its footsteps locally, the cheapest manual 911 would start at $264,400 before on-road costs – $34,900 more expensive than the entry-level 911 Carrera.
It would also raise the price of entry to three-pedal 911 ownership by$43,900 over the now-superseded 991.2 model.
1
2
nextprevious
Porsche 911 manual here in 2020


from the bujumbor refugge camp accra ghana, west africa....... dear,sir/madam Please permit me to introduce myself to you through this medium. I know you don't know me before and maybe surprise to read from me today, I got your contact in my searching of a good reputation foriegn partner to assit me in my late father fund, when I was making a research on how me and my two brothers, can travel to overseas and Invest on the petroleum business. I am very glad to have this opportunity to contact you and I want to count on you for reliability and trustworthiness and I also want you to handle this Issue I am about to disclose to you as confidential, because of my personality in my country. I am mumba the son of Chief Tama Koroma from Diamond Creek, Lofa County, Liberia. My father was until his death, the Paramount Chief of Lofa County also an Independent Diamond Mineral & Merchant. He died in March 13, 1999 after a brief illness at the age of 70.One day after my father's death, I was going through his under ground save when I saw some very Important Documents which reveals to me that my Late father has deposited one trunk of consignment box of $22.2 Million U.S dollars with a Security company here in ghana My two brothers, PETER and MOSES and myself have not traveled out side West Africa before. his is the main problem we have.At this moment, we are now in Accra-Ghana where we flee to in the wake of recent fighting between the government, the LURD & MODEL, Rebel groups. We are presently taking refuge at the Buduburam Refugee Camp here in Ghana under the Auspices of the United Nations High Commission for Refugees, U.N.H.C.R.I want you to assist us in retrieving the funds to your country then make aragements for me and my two brothers, to Join you there, where you will also help us buy a House and Invest the rest of the money on any profitable business for us.My two brothers, and myself are willing to set-aside 5% of the Total money to cover any expenses you make. We also offer to give you 15% of the Total amount for your service.I will give you further details of the Security company in ghana also the Documents covering the funds as soon as I get an indication of your interest to help us,please do send me your phone number and your fax number on your reply. Thank you very much, mumba Tama Koroma...... you can alaso reach me on my private email, mumba5055@yahoo.com


Set-up your spoken language.
Choose your option
Afrikanns
Albanian
Arabic
Armenian
Basque
Bengali
Bulgarian
Catalan
Cambodian
Chinese (Mandarin)
Croation
Czech
Danish
Dutch
English
Estonian
Fiji
Finnish
French
Georgian
German
Greek
Gujarati
Hebrew
Hindi
Hungarian
Icelandic
Indonesian
Irish
Italian
Japanese
Javanese
Korean
Latin
Latvian
Lithuanian
Macedonian
Malay
Malayalam
Maltese
Maori
Marathi
Mongolian
Nepali
Norwegian
Persian
Polish
Portuguese
Punjabi
Quechua
Romanian
Russian
Samoan
Serbian
Slovak
Slovenian
Spanish
Swahili
Swedish
Tamil
Tatar
Telugu
Thai
Tibetan
Tonga
Turkish
Ukranian
Urdu
Uzbek
Vietnamese
Welsh
Xhosa
Your spoken language:
Save
save


Product List
User List
Order List
Employee List
FeedMeLife
Backstore
Sign Out
Add New Item
Choose Isle...
Fruits & Veges
Dairy & Eggs
Meat & Poultry
Pantry
Snacks
Prepared Meals
Frozen
Bakery
Beverages
Perishable...
Yes
No
Save Changes


PFAs invest N34.89bn pension funds in infrastructure
by Nike PopoolaNike Popoola
Pension Funds Administrators have raised their investments in infrastructure to N34.89bn as of the end of September 2019 from the pension monies in their custody, according to the latest data from the National Pension Commission.
Figures obtained from the commission on Friday revealed that the total assets under the CPS stood at N9.58tn as of the end of September.
Operators of the Contributory Pension Scheme have also said investors continued to intensify their lobby to access the funds in their custody.
According to the commission, in May 2015, the operators invested N568m in infrastructure and increased it to N1.35bn in December 2015.
It added that the PFAs invested N2.06bn in infrastructure bond in December 2016, and gradually increased the pension funds invested in the portfolio.
According to PenCom, the PFAs invested N6.86bn in the nation’s infrastructure as of December 2017.
The amount invested in infrastructure as of the end of September 2018 was N17.12bn.
The President, PenOp, Mrs Aderonke Adedeji, said the issue of the role of pension funds in economic development had moved into the focus of public attention, particularly with regard to Nigeria’s growing need for long-term capital.
She explained that successful mobilisation of pension fund assets for the economic growth of any nation was an essential policy objective.
“For the first time, our country can now boast of a long-term funding base and the impact to date has included the funding of the government and government projects, development of the capital market, as well as increased foreign development inflows,” she said.
While this is positive, she added, a note of caution must be raised in view of recent agitations to access the funds for infrastructure.
Copyright PUNCH.
All rights reserved. This material, and other digital content on this website, may not be reproduced, published, broadcast, rewritten or redistributed in whole or in part without prior express written permission from PUNCH.
Contact: theeditor@punchng.com


 Soon folks be ordering all kinds of mess.
Awwww yisss, coming soon mate.


Intro to Data and Probability
2018-12-30
Summary
Check out the course activity week-by-week by navigation help from left.
Github repository link for this course: https://github.com/akshayreddykotha/intro-data-prob
2018-12-30
Check out the course activity week-by-week by navigation help from left.
Github repository link for this course: https://github.com/akshayreddykotha/intro-data-prob


"GATH-HEPHER "wine-press of the well, a town of Lower Galilee, about 5 miles from Nazareth; the birthplace of Jonah (2 Kings 14:25); the same as Gittah-hepher (Joshua 19:13). It has been identified with the modern el-Meshed, a village on the top of a rocky hill. Here the supposed tomb of Jonah, Neby Yunas, is still pointed out.
"GATH-HEPHER "wine-press of the well, a town of Lower Galilee, about 5 miles from Nazareth; the birthplace of Jonah (2 Kings 14:25); the same as Gittah-hepher (Joshua 19:13). It has been identified with the modern el-Meshed, a village on the top of a rocky hill. Here the supposed tomb of Jonah, Neby Yunas, is still pointed out.


Shop Online
Using our convenient web app, you'll get all the power of gFood without having to call your order in. Order in your pajamas, order 24 hours a day, order on Christmas, we're here to serve you.
Using our convenient web app, you'll get all the power of gFood without having to call your order in. Order in your pajamas, order 24 hours a day, order on Christmas, we're here to serve you.
You've never seen ordering this quick.  We'd ask what that is, but gFood respects your privacy.
Money: You've got it, we want it. But let it never be said we're not incredibly fair! Burger sales? Check. Pizza sales? Check. Burger and pizza sales?? Check, check, check! We seriously can't stop making deals.


I am a 29 year old male in decent health. I have been an infrequent user of MDMA, Ecstasy and Cocaine over the past 12 years, on average taking them 3 - 4 times per year, with a few periods of more concentrated usage, so I have a good understanding of stims. I was a heavy daily cannabis user for about 5 years, but have not smoked cannabis for about 5 years. I am a regular heavy drinker. I have taken very good quality MDMA and Cocaine on a number of occasions so I can use these experiences as a point of reference.
11.30 (T -0:15) Package of Mephedrone arrives in post; off white crystals.
11.45 (T 0:00) Small amount approx 50 Mg (no scales present) taken orally at home, mixed in water; this is generally how I take MDMA. I have not eaten, but have drunk black coffee.
12.00 (T 0:15) I feel something; increased energy, euphoria, increased ability to concentrate. These effects are very mild, but noticeable. I begin to do some university work.
12.30 (T 0:45) Work is going well, it is not easy to think very logically, but it can be done with some effort. On looking at the work done later it is of a decent standard, no different to total sobriety.
12.45 (T 1:00) Feeling horny and restless, still feeling nice. I redose with approx 100Mg.
13.00 (T 1.15) Feelings of arousal increased.  Restlessness increased, need to move around. Feels nice, but nothing like an MDMA high.
13.45 (T 2.00) Doing housework, this is unusual for me; I clean the bathroom, folds sheets etc. Mild but noticeable chewing develops. Slight dilation of the pupils.
14.15 (T 2.30) I go to the shop to buy cigarettes and gum. I am not a regular smoker, but like to smoke on MDMA or Cocaine. Mild confusion; want to buy Marlboro, but ask for Mayfair. No paranoia about people thinking I am on something, but human interactions require definite effort to ensure I donít sound high. Effects are still mild, but pleasant; empathy, euphoria, energy.
14.30 (T 2.45) Still feels nice, but definite need for movement. Some sweating noticed.
14.45 (T 3.00) I decide to go for a walk. Physically I feel good, no increased heart rate or other physical side effects. I redose, initially thinking 100mg, but then decide that given this RC feels quite safe decide to dose 200mg. I consider insulfating, take 5 Ė 10mg in my nostril, very definite burn, very unpleasant, decide insulfating is a bad idea, take the rest orally.
15.00 (T 3.15) BANG! I am walking through the park listening to psytrance and come up like good MDMA.  Compelled to run up a hill; movement definitely enhances this substance. Strong internal dialogue begins.
15.30 (T 3.45) Still feels fantastic, walking through high street, feels like floating; alert, feels like I could cope with human interaction if needed, music is very helpful to create a buffer from reality. I reach a pub, decide to drink a pint of Guinness to compensate for lack of food; no feelings of hunger, but I understand that the body needs food. Ordering a pint is no problem, but I would not want to talk to someone sober as I know I would appear quite high.
16.00 (T 4.15) Finished pint, smoked a number of cigarettes, very pleasant. Feeling very very aroused. I am straight, but consider a homosexual encounter I am so horny. Leave park and carry on walking.
16.30 (T 4.45) Walking through large park, strong internal dialogue continues, listening to old skool hiphop from my youth. Stop to stroke dog, still feels delicious like good MDMA. No desire to redose felt. Park is very large but empty save for a few dog walkers, I feel the need to bounce around to the music from time to time; when completely unobserved give into desires and really enjoy it.
17.30 (T 5.45) Back in high street, no feelings of hunger felt, but I know I needs to eat, so proceed to supermarket to buy light food such as salad. At the checkout I have a pleasant chat with the cashier about music, this is unheard of; conversation passes without incident.
18.00 (T 6.15) I arrive home. Effects are diminished considerably. I am not feeling bad, but am feeling normal and in comparison am bad. I am not sure what to do with myself. I have a protein drink and watch a cartoon. I class this as a crash, the crash lasts for about 30 mins - 1 hour. This is not painful or unpleasant, but a necessary part in the return to normality. I am very glad that I had not taken anything with me on my walk as this prevented me from being able to redose, however I was not itching to get home to get another dose.
19.00 (T 7.15) I am feeling nice and mellow, the crash has passed and I have an appetite, I manage a big bowl of vegetable stew. For the rest of the evening I am in a state of calmness, watch some films; feel nice.  Stings like hell, I clean it off quickly, seems like the chemical is very caustic it has started to strip some of the skin from my glans, I spray lots of antiseptic on it, the next day it has completely healed.
00.00 (T 12.45) I try to sleep, feel a bit restless, my head is clear, but there is background noise that keeps breaking through, some loud music even comes in; just as I start to drop off a few times a loud noise seems to occur which wakes me. I consider that this is the most unpleasant side effect of Mephedrone that I have experienced. Six months ago I took 500mg of speed and was unable to sleep properly for 3 days, this was something of an internal hell and was infinitely worse than these Mephedrone aftershocks. However the Mephedrone aftershocks seemed to be much more uncontrollable and external in nature; would be quite scary if they became strong or lasted for more than an hour or so.
01.30 (T 14.15) I fell asleep.
12.30 (T 23.15) I wake up, good sleep, no nightmares, feels normal.
Conclusion
^^^^^^^^^^
* Mephedrone very closely simulated the effects of MDMA. Maybe slightly different, but comparable in terms of high.
* The high came on within 10 - 15 minutes.
* The high lasted 2 - 3 hours.
* There was a gentle return to normality; this feels a bit like a crash, the crash lasts about 1 hour.
* After the crash there was a pleasant feeling of calmness, but external stimuli may be necessary to maintain feelings of normality.
* Good sleep was possible, but there was a worrying effect of unwanted external voices in the mind for a few hours after the crash.
* This substance is highly caustic.
* This substance is a very strong aphrodisiac, but does not seriously impair the ability to gain an erection; this may be a good or bad thing.
I was very very surprised by this substance. I now think that given its ready availability, low price, excellent MDMA rivaling high and its mild comedown I would rather take this if going to a club, than buy some wrap of expensive white powder that I know nothing about.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


This is an example of getting a request from a web-based service. In most cases, servers will prevent a request from a page/program that was not served by itself - this is called a 'Cross-Origin Resource Sharing Violation'.
How do we get around it? There is a 'dance' that the server and requestor go through in order to validate that a request is coming from a valid service. By setting our server to allow CORS, we can get service content from any location. We allow CORS through the server by using the cors node package.
To see this in action - click this button:
(no data received...)


|
ELENA Standard Library 2.0 |
system'Object | +--system'BaseBoolValue
A base Boolean value
| Method Summary | |
and : bool
= bool
|
Bitwise AND operarion
|
bool = bool
|
|
cast : verb
&to:object
= object
|
Dispatches the verb to the target object with bool subject
|
cast : verb
&to:object
&with:object
= object
|
Dispatches the verb to the target object with bool subject providing the parameter
|
clone = object
|
|
else : action
|
|
equal : object
= bool
|
|
equal : bool:bool
= bool
|
|
iif : object
: object
= object
|
|
literal = literal
|
|
not = bool
|
|
or : bool
= bool
|
Bitwise OR operarion
|
then : action
|
|
then : action
&else:actio
|
|
wide = wide
|
|
xor : bool
= bool
|
Bitwise XOR operarion
|
system'Object | +--system'false
A false value symbol
| Method Summary | |
and : bool
= bool
|
Bitwise OR operarion
|
bool = bool
|
Returns itself.
|
else : action
|
Executes the action;
|
cast : verb
&to:object
= object
|
Dispatches the verb to the target object with bool subject
|
cast : verb
&to:object
&with:object
= object
|
Dispatches the verb to the target object with bool subject providing the parameter
|
clone = object
|
Returns itself.
|
equal : object
= bool
|
Determines whether the specified object is equal to the current object boolean value.
|
equal : bool:bool
= bool
|
Determines whether the specified object is equal to the current object boolean value.
|
iif : object
: object
= object
|
Always returns the second parameter
|
literal = literal
|
Returns literal representation.
|
not = bool
|
Always return true
|
or : bool
= bool
|
Bitwise OR operarion
|
then : action
|
Always returns nil.
|
then : action
&else:action
|
Executes else-action;
|
wide = wide
|
Returns wide literal representation.
|
xor : bool
= bool
|
Bitwise XOR operarion
|
system'Object | +--system'nil
A nil value
| Method Summary | |
cast : verb
&to:object
= object
|
Dispatches the verb to the target object with void subject
|
cast : verb
&with:object
&to:object
= object
|
Dispatches the verb to the target object with void subject providing the parameter
|
equal : object
= object
|
Returns true if the operand is nil
|
generic.get = object
|
Always return nil value
|
A common ancestor
| Constructor Summary | |
new = object
|
Creates the object
|
| Method Summary | |
cast : verb
&to:object
= object
|
Dispatches the verb to the target object with object subject
|
cast : verb
&with:object
&to:object
= object
|
Dispatches the verb to the target object with object subject providing the parameter
|
dispatch |
Implements a message dispatching in VMT
|
equal : object
= bool
|
Returns true if the specified object is equal to the current object; otherwise, false.
|
system'Object | +--system'true
A true value symbol
| Method Summary | |
and : bool
= bool
|
Bitwise AND operarion
|
bool = bool
|
Returns itself.
|
cast : verb
&to:object
= object
|
Dispatches the verb to the target object with bool subject
|
cast : verb
&to:object
&with:object
= object
|
Dispatches the verb to the target object with bool subject providing the parameter
|
clone = object
|
Returns itself.
|
else : action
|
Always returns nil.
|
equal : object
= bool
|
Determines whether the specified object is equal to the current object boolean value.
|
equal &bool:bool
= bool
|
Determines whether the specified object is equal to the current object boolean value.
|
iif : object
: object
= object
|
Always returns the first parameter
|
literal = literal
|
Returns literal representation.
|
not = bool
|
Always return false
|
or : bool
= bool
|
Bitwise OR operarion
|
then : action
|
Executes the action;
|
then : action
&else:action
|
Executes then-action;
|
wide = wide
|
Returns wide literal representation.
|
xor : bool
= bool
|
Bitwise XOR operarion
|
|
ELENA Standard Library 2.0 |


A Goal is defined as an end state that a Stakeholder intends to achieve.
An end can represent anything a stakeholder may desire, such as a state of affairs, or a produced value.
Goals are generally expressed using qualitative words.
Motivation
Increase profit, reduce waiting times at the helpdesk, introduce on-line portfolio management, more sales


Forty seven dead beats living in the back street
North, east, west, south, all in the same house
Sitting in a back room, waiting for the big boom
I'm in a bedroom waiting for my baby
She's so mean but I don't care I love her eyes and her wild, wild hair
Dance to the beat that we love best Heading for the nineties
Living in the wild, wild west The wild, wild west (wild west)
Well, Mandy's in the backroom, handing out Valium
Sheriff's on the airwaves, talking to the D.J.'s
Forty seven heartbeats beating like a drum
Got to live it up, live it up, Ronnie's got a new gun
She's so mean but I don't care I love her eyes and her wild, wild hair
Dance to the beat that we love best Heading for the nineties
Living in the wild, wild west The wild, wild west (wild west)
Now put your flags in the air and march them up and down
You can live it up, live it up all over the town
And turn to the left, turn to the right
I don't care as long as she comes tonight
She's so mean but I don't care I love her eyes and her wild, wild hair
Dance to the beat that we love best Heading for the nineties
Living in the wild, wild west The wild, wild west (wild west)
Brrrr, here come a musical disc 'Cause some people them a-keep waitin' for
This one's called the outlaw, wow They want me
Ride the rhythm like me ridin' a bike Shine on me
Murder me chatter when me chat on the mic
Shorties thought this could keep them rockin' 'til the broad daylight
And here comes Thrown 2 Gether to rock it all night, say
Heading for the nineties, living in the eighties
Screaming in a back room, waiting for the big boom
Give me, give me wild west, give me, give me safe sex
Give me love, give me love, give me time to live it up
She's so mean but I don't care I love her eyes and her wild, wild hair
Dance to the beat that we love best Heading for the nineties
Living in the wild, wild west The wild, wild west (wild west)


Configure the Prometheus data source for the Sensors dashboards:
PrometheusPrometheus URL is required.
Data source "{{ctrl.datasourceName}}" is configured.
Edit the data source if you need to set any further information.
Import dashboards under the Dashboards tab.


'br}
'br}
{\
pg_upgradecluster - upgrade an existing PostgreSQL cluster to a new major version.
pg_upgradecluster [-v newversion] oldversion name [newdatadir]
pg_upgradecluster upgrades an existing PostgreSQL server cluster (i. e. a collection of databases served by a postmaster instance) to a new version specified by newversion (default: latest available version). The configuration files of the old version are copied to the new cluster.
The cluster of the old version will be configured to use a previously unused port since the upgraded one will use the original port. The old cluster is not automatically removed. After upgrading, please verify that the new cluster indeed works as expected; if so, you should remove the old cluster with pg_dropcluster|(8). Please note that the old cluster is set to *(L"manual*(R" startup mode, in order to avoid inadvertently changing it; this means that it will not be started automatically on system boot, and you have to use pg_ctlcluster|(8) to start/stop it. See section *(L"s-1STARTUP CONTROL*(R"s0 in pg_createcluster|(8) for details.
The newdatadir argument can be used to specify a non-default data directory of the upgraded cluster. It is passed to pg_createcluster. If not specified, this defaults to /var/lib/postgresql/newversion/name.
Please note that this program cannot upgrade clusters which use tablespaces. If you use those, you have to upgrade manually.
Set the version to upgrade to (default: latest available).
Set a custom log file path for the upgraded database cluster.
Set the default locale for the upgraded database cluster. If this option is not specified, the locale is inherited from the old cluster.
\fB--lc-collate=\fR\fIlocale\fR 4
\fB--lc-ctype=\fR\fIlocale\fR 4
\fB--lc-messages=\fR\fIlocale\fR 4
\fB--lc-monetary=\fR\fIlocale\fR 4
\fB--lc-numeric=\fR\fIlocale\fR 4
\fB--lc-time=\fR\fIlocale\fR 4
Like --locale, but only sets the locale in the specified category.
\fB-m\fR, \fB--method=\fRdump|upgrade 4
Specify the upgrade method. *(L"dump*(R" uses pg_dump|(1) and pg_restore|(1), *(L"upgrade*(R" uses pg_upgrade|(1). The default is *(L"dump*(R".
In pg_upgrade mode, use hard links instead of copying files to the new cluster. This option is merely passed on to pg_upgrade. See pg_upgrade|(1) for details.
Some PostgreSQL extensions like PostGIS need metadata in auxiliary tables which must not be upgraded from the old version, but rather initialized for the new version before copying the table data. For this purpose, extensions (as well as administrators, of course) can drop upgrade hook scripts into f(CW*(C`/etc/postgresql-common/pg_upgradecluster.d/*(C'. Script file names must consist entirely of upper and lower case letters, digits, underscores, and hyphens; in particular, dots (i. e. file extensions) are not allowed.
Scripts in that directory will be called with the following arguments:
<old version> <cluster name> <new version> <phase>
Phases:
A virgin cluster of version new version has been created, i. e. this new cluster will already have template1, but no user databases. Please note that you should not create tables in this phase, since they will be overwritten by the dump/restore or pg_upgrade operation.
All data from the old version cluster has been dumped/reloaded into the new one. The old cluster still exists, but is not running.
Failing scripts will abort the upgrade. The scripts are called as the user who owns the database.
When --mode=dump and upgrade hook scripts are used, pg_restore is invoked with --no-data-for-failed-tables.
pg_createcluster|(8), pg_dropcluster|(8), pg_lsclusters|(1), pg_wrapper|(1)
Martin Pitt <mpitt@debian.org>


Epworth Villa seniors help others prepare for winter chill
by Staff reportsWith winter weather approaching, the residents of Epworth Villa held their annual fall clothing drive.
The biannual event allows residents to clean out their closets and give their clothing items to Skyline Urban Ministries.
“I had a closet of good coats, and I only need one," said Jan Neel, Epworth resident. "I can help keep others warm this winter with the coats that I am not wearing.”
Each year in the fall and spring there is a clothing drive at Epworth Villa. Skyline workers said they love receiving donations from Epworth Villa because of the quality and care that goes into providing items. One Skyline volunteer said, “We also like the clothes Epworth Villa donates for our 'Dress for Success' patrons.”
This fall, Epworth residents gathered 845 pounds of warm clothing and coats for Skyline.
Epworth Villa is a nonprofit, Life Plan Retirement Community in north Oklahoma City.


|
JavaTM 2 Platform Standard Ed. 5.0 |
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface XADataSource
A factory for XAConnection
objects that is used internally.
An object that implements the XADataSource
interface is
typically registered with a naming service that uses the
Java Naming and Directory InterfaceTM
(JNDI).
| Method Summary | |
|---|---|
int |
getLoginTimeout()
Retrieves the maximum time in seconds that this data source can wait while attempting to connect to a data source. |
PrintWriter |
getLogWriter()
Retrieves the log writer for this XADataSource object. |
XAConnection |
getXAConnection()
Attempts to establish a physical database connection that can be used in a distributed transaction. |
XAConnection |
getXAConnection(String user,
String password)
Attempts to establish a physical database connection, using the given user name and password. |
void |
setLoginTimeout(int seconds)
Sets the maximum time in seconds that this data source will wait while attempting to connect to a data source. |
void |
setLogWriter(PrintWriter out)
Sets the log writer for this XADataSource object
to the given java.io.PrintWriter object. |
| Method Detail |
|---|
XAConnection getXAConnection() throws SQLException
XAConnection
object, which represents a
physical connection to a data source, that can be used in
a distributed transaction
SQLException
- if a database access error occursXAConnection getXAConnection(String user, String password) throws SQLException
user
- the database user on whose behalf the connection is being madepassword
- the user's password
XAConnection
object, which represents a
physical connection to a data source, that can be used in
a distributed transaction
SQLException
- if a database access error occursPrintWriter getLogWriter() throws SQLException
Retrieves the log writer for this XADataSource
object.
null
if no log
writer has been set, which means that logging is disabled
SQLException
- if a database access error occurssetLogWriter(java.io.PrintWriter)
void setLogWriter(PrintWriter out) throws SQLException
XADataSource
object
to the given java.io.PrintWriter
object.
The log writer is a character output stream to which all logging
and tracing messages for this XADataSource
object will be
printed. This includes messages printed by the methods of this
object, messages printed by methods of other objects manufactured
by this object, and so on. Messages printed to a log writer that is
specific to a data source are not printed to the log writer associated
with the java.sql.DriverManager
class. When a data source
object is created, the log writer is initially null
.
out
- the new log writer; to disable logging, set to null
SQLException
- if a database access error occursgetLogWriter()
void setLoginTimeout(int seconds) throws SQLException
Sets the maximum time in seconds that this data source will wait while attempting to connect to a data source. A value of zero specifies that the timeout is the default system timeout if there is one; otherwise, it specifies that there is no timeout. When a data source object is created, the login timeout is initially zero.
seconds
- the data source login time limit
SQLException
- if a database access error occursgetLoginTimeout()
int getLoginTimeout() throws SQLException
XADataSource
object or zero if there is no
no timeout limit or the timeout limit is the default system
timeout limit if there is one
SQLException
- if a database access error occurssetLoginTimeout(int)
|
JavaTM 2 Platform Standard Ed. 5.0 |
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | |||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
Copyright © 2004, 2010 Oracle and/or its affiliates. All rights reserved. Use is subject to license terms. Also see the documentation redistribution policy.