|
MeterLogger
|
Go to the source code of this file.
| #define REG_SPI_BASE | ( | i | ) | (0x60000200-i*0x100) |
Definition at line 14 of file spi_register.h.
| #define SLV_SPI_INT_EN 0x0000001f |
Definition at line 188 of file spi_register.h.
| #define SLV_SPI_INT_EN_S 5 |
Definition at line 189 of file spi_register.h.
| #define SPI_ADDR | ( | i | ) | (REG_SPI_BASE(i) + 0x4) |
Definition at line 32 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_AHB_ENDIAN_MODE 0x00000003 |
Definition at line 130 of file spi_register.h.
| #define SPI_AHB_ENDIAN_MODE_S 8 |
Definition at line 131 of file spi_register.h.
| #define SPI_AHB_USR_COMMAND (BIT(3)) |
Definition at line 136 of file spi_register.h.
| #define SPI_AHB_USR_COMMAND_4BYTE (BIT(1)) |
Definition at line 138 of file spi_register.h.
| #define SPI_BUS_TIMER_LIMIT 0x0000FFFF |
Definition at line 55 of file spi_register.h.
| #define SPI_BUS_TIMER_LIMIT_S 0 |
Definition at line 56 of file spi_register.h.
| #define SPI_CK_I_EDGE (BIT(6)) |
Definition at line 133 of file spi_register.h.
| #define SPI_CK_OUT_EDGE (BIT(7)) |
Definition at line 132 of file spi_register.h.
Referenced by spi_mode().
| #define SPI_CK_OUT_HIGH_MODE 0x0000000F |
Definition at line 87 of file spi_register.h.
| #define SPI_CK_OUT_HIGH_MODE_S 12 |
Definition at line 88 of file spi_register.h.
| #define SPI_CK_OUT_LOW_MODE 0x0000000F |
Definition at line 89 of file spi_register.h.
| #define SPI_CK_OUT_LOW_MODE_S 8 |
Definition at line 90 of file spi_register.h.
| #define SPI_CLK_EQU_SYSCLK (BIT(31)) |
Definition at line 97 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CLKCNT_H 0x0000003F |
Definition at line 102 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CLKCNT_H_S 6 |
Definition at line 103 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CLKCNT_L 0x0000003F |
Definition at line 104 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CLKCNT_L_S 0 |
Definition at line 105 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CLKCNT_N 0x0000003F |
Definition at line 100 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CLKCNT_N_S 12 |
Definition at line 101 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CLKDIV_PRE 0x00001FFF |
Definition at line 98 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CLKDIV_PRE_S 18 |
Definition at line 99 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CLOCK | ( | i | ) | (REG_SPI_BASE(i) + 0x18) |
Definition at line 96 of file spi_register.h.
Referenced by spi_clock().
| #define SPI_CMD | ( | i | ) | (REG_SPI_BASE(i) + 0x0) |
Definition at line 16 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_CS0_DIS (BIT(0)) |
Definition at line 167 of file spi_register.h.
| #define SPI_CS1_DIS (BIT(1)) |
Definition at line 166 of file spi_register.h.
| #define SPI_CS2_DIS (BIT(2)) |
Definition at line 165 of file spi_register.h.
| #define SPI_CS_DELAY_MODE 0x00000003 |
Definition at line 75 of file spi_register.h.
| #define SPI_CS_DELAY_MODE_S 26 |
Definition at line 76 of file spi_register.h.
| #define SPI_CS_DELAY_NUM 0x0000000F |
Definition at line 73 of file spi_register.h.
| #define SPI_CS_DELAY_NUM_S 28 |
Definition at line 74 of file spi_register.h.
| #define SPI_CS_HOLD (BIT(4)) |
Definition at line 135 of file spi_register.h.
Referenced by ext_spi_init(), and spi_init().
| #define SPI_CS_HOLD_DELAY 0x0000000F |
Definition at line 51 of file spi_register.h.
| #define SPI_CS_HOLD_DELAY_RES 0x00000FFF |
Definition at line 53 of file spi_register.h.
| #define SPI_CS_HOLD_DELAY_RES_S 16 |
Definition at line 54 of file spi_register.h.
| #define SPI_CS_HOLD_DELAY_S 28 |
Definition at line 52 of file spi_register.h.
| #define SPI_CS_I_MODE 0x00000003 |
Definition at line 181 of file spi_register.h.
| #define SPI_CS_I_MODE_S 10 |
Definition at line 182 of file spi_register.h.
| #define SPI_CS_SETUP (BIT(5)) |
Definition at line 134 of file spi_register.h.
Referenced by ext_spi_init(), and spi_init().
| #define SPI_CTRL | ( | i | ) | (REG_SPI_BASE(i) + 0x8) |
Definition at line 34 of file spi_register.h.
| #define SPI_CTRL1 | ( | i | ) | (REG_SPI_BASE (i) + 0xC) |
Definition at line 50 of file spi_register.h.
| #define SPI_CTRL2 | ( | i | ) | (REG_SPI_BASE(i) + 0x14) |
Definition at line 72 of file spi_register.h.
| #define SPI_DIO_MODE (BIT(23)) |
Definition at line 38 of file spi_register.h.
| #define SPI_DOUT_MODE (BIT(14)) |
Definition at line 47 of file spi_register.h.
| #define SPI_DOUTDIN (BIT(0)) |
Definition at line 139 of file spi_register.h.
| #define SPI_ENABLE_AHB (BIT(17)) |
Definition at line 44 of file spi_register.h.
| #define SPI_EXT0 | ( | i | ) | (REG_SPI_BASE(i) + 0xF0) |
Definition at line 257 of file spi_register.h.
| #define SPI_EXT1 | ( | i | ) | (REG_SPI_BASE(i) + 0xF4) |
Definition at line 264 of file spi_register.h.
| #define SPI_EXT2 | ( | i | ) | (REG_SPI_BASE(i) + 0xF8) |
Definition at line 271 of file spi_register.h.
| #define SPI_EXT3 | ( | i | ) | (REG_SPI_BASE(i) + 0xFC) |
Definition at line 275 of file spi_register.h.
| #define SPI_FASTRD_MODE (BIT(13)) |
Definition at line 48 of file spi_register.h.
| #define SPI_FLASH_BE (BIT(23)) |
Definition at line 25 of file spi_register.h.
| #define SPI_FLASH_BP0 (BIT(2)) |
Definition at line 68 of file spi_register.h.
| #define SPI_FLASH_BP1 (BIT(3)) |
Definition at line 67 of file spi_register.h.
| #define SPI_FLASH_BP2 (BIT(4)) |
Definition at line 66 of file spi_register.h.
| #define SPI_FLASH_BUSY_FLAG (BIT(0)) |
Definition at line 70 of file spi_register.h.
| #define SPI_FLASH_CE (BIT(22)) |
Definition at line 26 of file spi_register.h.
| #define SPI_FLASH_DP (BIT(21)) |
Definition at line 27 of file spi_register.h.
| #define SPI_FLASH_HPM (BIT(19)) |
Definition at line 29 of file spi_register.h.
| #define SPI_FLASH_MODE (BIT(2)) |
Definition at line 137 of file spi_register.h.
Referenced by ext_spi_init(), and spi_init().
| #define SPI_FLASH_PP (BIT(25)) |
Definition at line 23 of file spi_register.h.
| #define SPI_FLASH_RDID (BIT(28)) |
Definition at line 20 of file spi_register.h.
| #define SPI_FLASH_RDSR (BIT(27)) |
Definition at line 21 of file spi_register.h.
| #define SPI_FLASH_READ (BIT(31)) |
Definition at line 17 of file spi_register.h.
| #define SPI_FLASH_RES (BIT(20)) |
Definition at line 28 of file spi_register.h.
| #define SPI_FLASH_SE (BIT(24)) |
Definition at line 24 of file spi_register.h.
| #define SPI_FLASH_STATUS_PRO_FLAG (BIT(7)) |
Definition at line 64 of file spi_register.h.
| #define SPI_FLASH_TOP_BOT_PRO_FLAG (BIT(5)) |
Definition at line 65 of file spi_register.h.
| #define SPI_FLASH_WRDI (BIT(29)) |
Definition at line 19 of file spi_register.h.
| #define SPI_FLASH_WREN (BIT(30)) |
Definition at line 18 of file spi_register.h.
| #define SPI_FLASH_WRENABLE_FLAG (BIT(1)) |
Definition at line 69 of file spi_register.h.
| #define SPI_FLASH_WRSR (BIT(26)) |
Definition at line 22 of file spi_register.h.
| #define SPI_FWRITE_DIO (BIT(14)) |
Definition at line 125 of file spi_register.h.
| #define SPI_FWRITE_DUAL (BIT(12)) |
Definition at line 127 of file spi_register.h.
| #define SPI_FWRITE_QIO (BIT(15)) |
Definition at line 124 of file spi_register.h.
| #define SPI_FWRITE_QUAD (BIT(13)) |
Definition at line 126 of file spi_register.h.
| #define SPI_HOLD_MODE (BIT(18)) |
Definition at line 43 of file spi_register.h.
| #define SPI_HOLD_TIME 0x0000000F |
Definition at line 91 of file spi_register.h.
| #define SPI_HOLD_TIME_S 4 |
Definition at line 92 of file spi_register.h.
| #define SPI_IDLE_EDGE (BIT(29)) |
Definition at line 164 of file spi_register.h.
Referenced by spi_mode().
| #define SPI_INT_HOLD_ENA 0x00000003 |
Definition at line 276 of file spi_register.h.
| #define SPI_INT_HOLD_ENA_S 0 |
Definition at line 277 of file spi_register.h.
| #define SPI_MISO_DELAY_MODE 0x00000003 |
Definition at line 85 of file spi_register.h.
| #define SPI_MISO_DELAY_MODE_S 16 |
Definition at line 86 of file spi_register.h.
| #define SPI_MISO_DELAY_NUM 0x00000007 |
Definition at line 83 of file spi_register.h.
| #define SPI_MISO_DELAY_NUM_S 18 |
Definition at line 84 of file spi_register.h.
| #define SPI_MOSI_DELAY_MODE 0x00000003 |
Definition at line 79 of file spi_register.h.
| #define SPI_MOSI_DELAY_MODE_S 21 |
Definition at line 82 of file spi_register.h.
| #define SPI_MOSI_DELAY_NUM 0x00000007 |
Definition at line 77 of file spi_register.h.
| #define SPI_MOSI_DELAY_NUM_S 23 |
Definition at line 78 of file spi_register.h.
| #define SPI_PIN | ( | i | ) | (REG_SPI_BASE(i) + 0x2C) |
Definition at line 163 of file spi_register.h.
Referenced by spi_mode().
| #define SPI_QIO_MODE (BIT(24)) |
Definition at line 37 of file spi_register.h.
| #define SPI_QOUT_MODE (BIT(20)) |
Definition at line 41 of file spi_register.h.
| #define SPI_RD_BIT_ORDER (BIT(25)) |
Definition at line 36 of file spi_register.h.
| #define SPI_RD_BYTE_ORDER (BIT(10)) |
Definition at line 129 of file spi_register.h.
Referenced by spi_rx_byte_order(), and spi_transaction().
| #define SPI_RD_STATUS | ( | i | ) | (REG_SPI_BASE(i) + 0x10) |
Definition at line 59 of file spi_register.h.
| #define SPI_RESANDRES (BIT(15)) |
Definition at line 46 of file spi_register.h.
| #define SPI_SETUP_TIME 0x0000000F |
Definition at line 93 of file spi_register.h.
| #define SPI_SETUP_TIME_S 0 |
Definition at line 94 of file spi_register.h.
| #define SPI_SHARE_BUS (BIT(19)) |
Definition at line 42 of file spi_register.h.
| #define SPI_SIO (BIT(16)) |
Definition at line 123 of file spi_register.h.
| #define SPI_SLAVE | ( | i | ) | (REG_SPI_BASE(i) + 0x30) |
Definition at line 169 of file spi_register.h.
| #define SPI_SLAVE1 | ( | i | ) | (REG_SPI_BASE(i) + 0x34) |
Definition at line 196 of file spi_register.h.
| #define SPI_SLAVE2 | ( | i | ) | (REG_SPI_BASE(i) + 0x38) |
Definition at line 214 of file spi_register.h.
| #define SPI_SLAVE3 | ( | i | ) | (REG_SPI_BASE(i) + 0x3C) |
Definition at line 224 of file spi_register.h.
| #define SPI_SLAVE_MODE (BIT(30)) |
Definition at line 171 of file spi_register.h.
| #define SPI_SLV_BUF_BITLEN 0x000001FF |
Definition at line 201 of file spi_register.h.
| #define SPI_SLV_BUF_BITLEN_S 16 |
Definition at line 202 of file spi_register.h.
| #define SPI_SLV_CMD_DEFINE (BIT(27)) |
Definition at line 174 of file spi_register.h.
| #define SPI_SLV_LAST_COMMAND 0x00000007 |
Definition at line 179 of file spi_register.h.
| #define SPI_SLV_LAST_COMMAND_S 17 |
Definition at line 180 of file spi_register.h.
| #define SPI_SLV_LAST_STATE 0x00000007 |
Definition at line 177 of file spi_register.h.
| #define SPI_SLV_LAST_STATE_S 20 |
Definition at line 178 of file spi_register.h.
| #define SPI_SLV_RD_ADDR_BITLEN 0x0000003F |
Definition at line 203 of file spi_register.h.
| #define SPI_SLV_RD_ADDR_BITLEN_S 10 |
Definition at line 204 of file spi_register.h.
| #define SPI_SLV_RD_BUF_DONE (BIT(0)) |
Definition at line 194 of file spi_register.h.
| #define SPI_SLV_RD_BUF_DONE_EN (BIT(5)) |
Definition at line 187 of file spi_register.h.
| #define SPI_SLV_RD_STA_DONE (BIT(2)) |
Definition at line 192 of file spi_register.h.
| #define SPI_SLV_RD_STA_DONE_EN (BIT(7)) |
Definition at line 185 of file spi_register.h.
| #define SPI_SLV_RDBUF_CMD_VALUE 0x000000FF |
Definition at line 231 of file spi_register.h.
| #define SPI_SLV_RDBUF_CMD_VALUE_S 0 |
Definition at line 232 of file spi_register.h.
| #define SPI_SLV_RDBUF_DUMMY_CYCLELEN 0X000000FF |
Definition at line 217 of file spi_register.h.
| #define SPI_SLV_RDBUF_DUMMY_CYCLELEN_S 16 |
Definition at line 218 of file spi_register.h.
| #define SPI_SLV_RDBUF_DUMMY_EN (BIT(0)) |
Definition at line 210 of file spi_register.h.
| #define SPI_SLV_RDSTA_CMD_VALUE 0x000000FF |
Definition at line 227 of file spi_register.h.
| #define SPI_SLV_RDSTA_CMD_VALUE_S 16 |
Definition at line 228 of file spi_register.h.
| #define SPI_SLV_RDSTA_DUMMY_EN (BIT(2)) |
Definition at line 208 of file spi_register.h.
| #define SPI_SLV_RDSTR_DUMMY_CYCLELEN 0x000000FF |
Definition at line 221 of file spi_register.h.
| #define SPI_SLV_RDSTR_DUMMY_CYCLELEN_S 0 |
Definition at line 222 of file spi_register.h.
| #define SPI_SLV_STATUS_BITLEN 0x0000001F |
Definition at line 197 of file spi_register.h.
| #define SPI_SLV_STATUS_BITLEN_S 27 |
Definition at line 198 of file spi_register.h.
| #define SPI_SLV_STATUS_FAST_EN (BIT(26)) |
Definition at line 199 of file spi_register.h.
| #define SPI_SLV_STATUS_READBACK (BIT(25)) |
Definition at line 200 of file spi_register.h.
| #define SPI_SLV_WR_ADDR_BITLEN 0x0000003F |
Definition at line 205 of file spi_register.h.
| #define SPI_SLV_WR_ADDR_BITLEN_S 4 |
Definition at line 206 of file spi_register.h.
| #define SPI_SLV_WR_BUF_DONE (BIT(1)) |
Definition at line 193 of file spi_register.h.
| #define SPI_SLV_WR_BUF_DONE_EN (BIT(6)) |
Definition at line 186 of file spi_register.h.
| #define SPI_SLV_WR_RD_BUF_EN (BIT(29)) |
Definition at line 172 of file spi_register.h.
| #define SPI_SLV_WR_RD_STA_EN (BIT(28)) |
Definition at line 173 of file spi_register.h.
| #define SPI_SLV_WR_STA_DONE (BIT(3)) |
Definition at line 191 of file spi_register.h.
| #define SPI_SLV_WR_STA_DONE_EN (BIT(8)) |
Definition at line 184 of file spi_register.h.
| #define SPI_SLV_WRBUF_CMD_VALUE 0x000000FF |
Definition at line 229 of file spi_register.h.
| #define SPI_SLV_WRBUF_CMD_VALUE_S 8 |
Definition at line 230 of file spi_register.h.
| #define SPI_SLV_WRBUF_DUMMY_CYCLELEN 0X000000FF |
Definition at line 215 of file spi_register.h.
| #define SPI_SLV_WRBUF_DUMMY_CYCLELEN_S 24 |
Definition at line 216 of file spi_register.h.
| #define SPI_SLV_WRBUF_DUMMY_EN (BIT(1)) |
Definition at line 209 of file spi_register.h.
| #define SPI_SLV_WRSTA_CMD_VALUE 0x000000FF |
Definition at line 225 of file spi_register.h.
| #define SPI_SLV_WRSTA_CMD_VALUE_S 24 |
Definition at line 226 of file spi_register.h.
| #define SPI_SLV_WRSTA_DUMMY_EN (BIT(3)) |
Definition at line 207 of file spi_register.h.
| #define SPI_SLV_WRSTR_DUMMY_CYCLELEN 0X000000FF |
Definition at line 219 of file spi_register.h.
| #define SPI_SLV_WRSTR_DUMMY_CYCLELEN_S 8 |
Definition at line 220 of file spi_register.h.
| #define SPI_SST_AAI (BIT(16)) |
Definition at line 45 of file spi_register.h.
| #define SPI_ST 0x00000007 |
Definition at line 272 of file spi_register.h.
| #define SPI_ST_S 0 |
Definition at line 273 of file spi_register.h.
| #define SPI_STATUS_EXT 0x000000FF |
Definition at line 60 of file spi_register.h.
| #define SPI_STATUS_EXT_S 24 |
Definition at line 61 of file spi_register.h.
| #define SPI_SYNC_RESET (BIT(31)) |
Definition at line 170 of file spi_register.h.
| #define SPI_T_ERASE_ENA (BIT(31)) |
Definition at line 265 of file spi_register.h.
| #define SPI_T_ERASE_SHIFT 0x0000000F |
Definition at line 266 of file spi_register.h.
| #define SPI_T_ERASE_SHIFT_S 16 |
Definition at line 267 of file spi_register.h.
| #define SPI_T_ERASE_TIME 0x00000FFF |
Definition at line 268 of file spi_register.h.
| #define SPI_T_ERASE_TIME_S 0 |
Definition at line 269 of file spi_register.h.
| #define SPI_T_PP_ENA (BIT(31)) |
Definition at line 258 of file spi_register.h.
| #define SPI_T_PP_SHIFT 0x0000000F |
Definition at line 259 of file spi_register.h.
| #define SPI_T_PP_SHIFT_S 16 |
Definition at line 260 of file spi_register.h.
| #define SPI_T_PP_TIME 0x00000FFF |
Definition at line 261 of file spi_register.h.
| #define SPI_T_PP_TIME_S 0 |
Definition at line 262 of file spi_register.h.
| #define SPI_TRANS_CNT 0x0000000F |
Definition at line 175 of file spi_register.h.
| #define SPI_TRANS_CNT_S 23 |
Definition at line 176 of file spi_register.h.
| #define SPI_TRANS_DONE (BIT(4)) |
Definition at line 190 of file spi_register.h.
| #define SPI_TRANS_DONE_EN (BIT(9)) |
Definition at line 183 of file spi_register.h.
| #define SPI_TWO_BYTE_STATUS_EN (BIT(22)) |
Definition at line 39 of file spi_register.h.
| #define SPI_USER | ( | i | ) | (REG_SPI_BASE(i) + 0x1C) |
Definition at line 107 of file spi_register.h.
Referenced by ext_spi_init(), spi_init(), spi_mode(), spi_rx_byte_order(), spi_transaction(), and spi_tx_byte_order().
| #define SPI_USER1 | ( | i | ) | (REG_SPI_BASE(i) + 0x20) |
Definition at line 144 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USER2 | ( | i | ) | (REG_SPI_BASE(i) + 0x24) |
Definition at line 154 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR (BIT(18)) |
Definition at line 30 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_ADDR (BIT(30)) |
Definition at line 109 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_ADDR_BITLEN 0x0000003F |
Definition at line 145 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_ADDR_BITLEN_S 26 |
Definition at line 146 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_ADDR_HOLD (BIT(21)) |
Definition at line 118 of file spi_register.h.
| #define SPI_USR_CMD_HOLD (BIT(22)) |
Definition at line 117 of file spi_register.h.
| #define SPI_USR_COMMAND (BIT(31)) |
Definition at line 108 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_COMMAND_BITLEN 0x0000000F |
Definition at line 155 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_COMMAND_BITLEN_S 28 |
Definition at line 156 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_COMMAND_VALUE 0x0000FFFF |
Definition at line 157 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_COMMAND_VALUE_S 0 |
Definition at line 158 of file spi_register.h.
| #define SPI_USR_DIN_HOLD (BIT(19)) |
Definition at line 120 of file spi_register.h.
| #define SPI_USR_DOUT_HOLD (BIT(18)) |
Definition at line 121 of file spi_register.h.
| #define SPI_USR_DUMMY (BIT(29)) |
Definition at line 110 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_DUMMY_CYCLELEN 0x000000FF |
Definition at line 151 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_DUMMY_CYCLELEN_S 0 |
Definition at line 152 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_DUMMY_HOLD (BIT(20)) |
Definition at line 119 of file spi_register.h.
| #define SPI_USR_DUMMY_IDLE (BIT(26)) |
Definition at line 113 of file spi_register.h.
| #define SPI_USR_HOLD_POL (BIT(17)) |
Definition at line 122 of file spi_register.h.
| #define SPI_USR_MISO (BIT(28)) |
Definition at line 111 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_MISO_BITLEN 0x000001FF |
Definition at line 149 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_MISO_BITLEN_S 8 |
Definition at line 150 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_MISO_HIGHPART (BIT(24)) |
Definition at line 115 of file spi_register.h.
| #define SPI_USR_MOSI (BIT(27)) |
Definition at line 112 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_MOSI_BITLEN 0x000001FF |
Definition at line 147 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_MOSI_BITLEN_S 17 |
Definition at line 148 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_USR_MOSI_HIGHPART (BIT(25)) |
Definition at line 114 of file spi_register.h.
| #define SPI_USR_PREP_HOLD (BIT(23)) |
Definition at line 116 of file spi_register.h.
| #define SPI_W0 | ( | i | ) | (REG_SPI_BASE(i) +0x40) |
Definition at line 236 of file spi_register.h.
Referenced by spi_transaction().
| #define SPI_W1 | ( | i | ) | (REG_SPI_BASE(i) +0x44) |
Definition at line 237 of file spi_register.h.
| #define SPI_W10 | ( | i | ) | (REG_SPI_BASE(i) +0x68) |
Definition at line 246 of file spi_register.h.
| #define SPI_W11 | ( | i | ) | (REG_SPI_BASE(i) +0x6C) |
Definition at line 247 of file spi_register.h.
| #define SPI_W12 | ( | i | ) | (REG_SPI_BASE(i) +0x70) |
Definition at line 248 of file spi_register.h.
| #define SPI_W13 | ( | i | ) | (REG_SPI_BASE(i) +0x74) |
Definition at line 249 of file spi_register.h.
| #define SPI_W14 | ( | i | ) | (REG_SPI_BASE(i) +0x78) |
Definition at line 250 of file spi_register.h.
| #define SPI_W15 | ( | i | ) | (REG_SPI_BASE(i) +0x7C) |
Definition at line 251 of file spi_register.h.
| #define SPI_W2 | ( | i | ) | (REG_SPI_BASE(i) +0x48) |
Definition at line 238 of file spi_register.h.
| #define SPI_W3 | ( | i | ) | (REG_SPI_BASE(i) +0x4C) |
Definition at line 239 of file spi_register.h.
| #define SPI_W4 | ( | i | ) | (REG_SPI_BASE(i) +0x50) |
Definition at line 240 of file spi_register.h.
| #define SPI_W5 | ( | i | ) | (REG_SPI_BASE(i) +0x54) |
Definition at line 241 of file spi_register.h.
| #define SPI_W6 | ( | i | ) | (REG_SPI_BASE(i) +0x58) |
Definition at line 242 of file spi_register.h.
| #define SPI_W7 | ( | i | ) | (REG_SPI_BASE(i) +0x5C) |
Definition at line 243 of file spi_register.h.
| #define SPI_W8 | ( | i | ) | (REG_SPI_BASE(i) +0x60) |
Definition at line 244 of file spi_register.h.
| #define SPI_W9 | ( | i | ) | (REG_SPI_BASE(i) +0x64) |
Definition at line 245 of file spi_register.h.
| #define SPI_WB_MODE 0x000000FF |
Definition at line 62 of file spi_register.h.
| #define SPI_WB_MODE_S 16 |
Definition at line 63 of file spi_register.h.
| #define SPI_WP_REG (BIT(21)) |
Definition at line 40 of file spi_register.h.
| #define SPI_WR_BIT_ORDER (BIT(26)) |
Definition at line 35 of file spi_register.h.
| #define SPI_WR_BYTE_ORDER (BIT(11)) |
Definition at line 128 of file spi_register.h.
Referenced by spi_transaction(), and spi_tx_byte_order().
| #define SPI_WR_STATUS | ( | i | ) | (REG_SPI_BASE(i) + 0x28) |
Definition at line 160 of file spi_register.h.


{{ HEAD }}
{{ APP }}
You maybe have disabled JavaScript and Frames, please enable JavaScript or frames in You browser. More info:
How to enable JavaScript
How to enable frames


HelloJS in PhoneGap
Google
Facebook
Windows
Demo HelloJS with PhoneGap Use the services above to signin and display basic account details here


{% extends "layout.html" %} {% block content %} {% if content %}
{{ content.content }}
By popular demand, this totally unique idea that no one has ever implemented before is now publicly available.


--- layout: default ---
{{ post.title }}
The future of fitness wearables, ENSOLE helps empower athletes across the world. Fitting in the sole of any shoe ENSOLE's cheap price and unique feature set makes it a one of kind product.
With the two premiere business clubs merging together, a new brand image was needed. The new brand image expresses both the professional and creative side of business.
Explore Patagonia PA's new marketing plan. Utilizing the strengths of the brand name and its image, this campaign focuses on community and eco-awarness.


Equivalent to clicking the Clear command on the Edit menu. Clears contents, formats, notes, or all of these from the active worksheet or macro sheet. Clears series or formats from the active chart.
Syntax
CLEAR(type_num)
CLEAR?(type_num)
Type_num is a number from 1 to 4 specifying what to clear. Only values 1, 2, and 3 are valid if the selected item is a chart.
On a worksheet or macro sheet, or if an entire chart is selected, the following occurs.
| Type_num | Clears |
| 1 | All |
| 2 | Formats (if a chart, clears the chart format or clears pictures) |
| 3 | Contents (if a chart, clears all data series) |
| 4 | Comments (this does not apply to charts) |
On a chart, if a single point, an entire data series, error bars, or a trend line is selected, the following occurs.
| Type_num | Clears |
| 1 | Selected series, error bars, or trend line |
| 2 | Format in the selected point, series, error bars, or trend line |
If type_num is omitted, the default values are set as shown in the following table.
| Active sheet | Type_num |
| Worksheet | 3 |
| Macro sheet | 3 |
| Chart (with no selection) | 1 |
| Chart (with item selected) | Deletes the selected item |
Related Function
EDIT.DELETE Removes cells from a sheet
Return to index


National Geographic
Forest
TZIPAC 7th Zebra Awards 2019
3rd Place, People & Animals
Grandmother
TZIPAC 7th Zebra Awards 2019
3rd Place, People & Animals
Motion Blur
TZIPAC 7th Zebra Awards 2019
3rd Place, People & Animals
Face Off
TZIPAC 7th Zebra Awards 2019
3rd Place, People & Animals


June 23
And we were in our own sight as grasshoppers, and so we were in their sight. Numbers 13:33
How does the devil see you? Does he see you as a terrifying and mighty warrior of God...or does he see you as a wimp he can whip in a minute? The answer to that question depends on you. I realized that one day as I was studying the children of Israel and their failure to enter the Promised Land. The key to their failure is found in these words: "And we were in our own sight as grasshoppers, and so we were in theirs."
The reason the Israelites were so terrified to fight the giants in Canaan wasn't because those giants were so big. It was because the Israelites saw themselves as so small! It was what they were in their own sight that defeated them.
The same thing is true for you as a believer. It's what you are in your own sight that will make the difference.  But when you begin to see yourself as God sees you, as a conquering son or daughter of the Almighty God equipped with the very power of God Himself, the devil will want to steer clear of you.
 In fact, ever since Jesus came up out of that grave, Satan's heart has melted within him at the sound of that Name in the mouth of one who has faith in it.
If you're not strong in the Lord in your own sight, you need to change that.  Turn the tables on the devil and let him find out what it feels like to be a grasshopper for a change.
Scripture Reading: Numbers 13:17-33


Basic Editing
Once file(s) are selected, they can be edited in the panel at the right hand side. If multiple files are selected, all of the files' tags are edited.
The files are immediately saved after editing is finished. If are in the middle of change the tags and want to discard them, use Undo( ⌘Z).
Multiple Files Editing
Multiple Files can edited at the same time. If any of the tags differ, placeholder values will be shown instead. Any changes will effect all of the selected files.
Artwork
Artwork can added by dragging the artwork to panel in the artwork tab. It can be deleted by using backspace or delete
Artwork can be saved to file by dragging the artwork to an folder or the desktop.


Turning on Synergy through terminal possible?
-
djkinetic
I currently am on an x86 OS X for intel build and unfortunately the system preference pane is not accesible to me and as such i cannot turn on synergy the normal way, my question is, would there be a way to turn the application on through the terminal if so what is the command and where is the application located/installed. i have the app installed for all users, synergy is great however of no use if i can only launch it by constantly installing the application over again, any input would be appreciated thank you.
-
Greg Hurrell
Yes. You could type:
Code:open /Library/PreferencePanes/Synergy.prefPane/Contents/Resources/Synergy.app
You could even define this as an alias (shortcut) or save it as a terminal ".command" file.
I am working on getting Synergy converted into a Universal Binary at the moment.
-
djkinetic
i just purchased the application how would i go about inputting the registration information without being able to access the control panel please PM me wincent if you could with information on how to do this thank you.
-
Greg Hurrell
Well you could do it via the Terminal using the "defaults" command, but I don't think that will be necessary.
I've just put the release candidate for version 2.3 up on the server. It's a Universal Binary. So if you install that you should get full access to the preference pane. More info, including download link here:
http://wincent.com/a/news/archives/2005/11/synergy_23_rele.php
-
Greg Hurrell
Just put a new release candidate up on the server today (30 November):
http://wincent.com/a/news/archives/2005/11/synergy_23_rele_1.php
This fixes a problem with license code validation on the Intel platform.
Reply
This topic is now closed.


Calls and initializes Categorical function
df = Categorical()
Categorical input
Categoricals can only take on only a limited, and usually fixed, number of possible values (categories). In contrast to statistical categorical variables, a Categorical might have an order, but numerical operations (additions, divisions, …) are not possible.


Dear Sir, My name is Hartman Onowu,I am the operational manager in account management section incharge of credit and foreign bills of one of the prime banks here in South Africa. I am writing in respect of a foreign customer of my bank who perished with his whole families on 25TH JULY,2000 CONCORDE PLANE CRASH [ Flight AF4590 ] with the whole passengers aboard. There is an account opened in this bank in 1998 by this great late INDUSTRIALIST who died without a written or oral WILL attatched to the account. Since his death , I personally has watched with keen interest to see the next of kin but all has proved abortive as no one has come to claim his funds and no other person knows about this account or anything concerning it,the account has no other beneficiary and until his death he was the manager of his company. The total amount involved is 16,000,000.00 USD.[Sixteen Million United States Dollar ]. We wish to start the first transfer with $6,000,000.00[Six million] and open successful transaction without any disappointment from your side, we shall re-apply for the transfer of the remaining balance to your account. I have secretly discussed this matter with the general manager of the bank who I must involve in order to have a smooth and a successful transfer of the fund to any foreign bank account which you are going to nominate. On this note, I decided to seek for a reliable foreigner who will act as the foreign beneficiary of the fund from the deceased by providing his/her bank account where the fund will be transferred for immediate investment on any viable project as no one has come up to be the next of kin. The banking ethics here does not allow such money to stay more than six years without claim hence the money will be recalled to the government treasury as unclaimed after this long period of domancy. In view of this I got your contact through my personal search to see if you can assist by providing your safe bank account for the transfer or find a reliable person who will be capable of receiving such amount in his or her personal account. At the conclussion of the transfer 65% of the fund will be for me, I will give you 20% of the total transfer sum, 10% for charity both in Africa and in your country while the remaining 5% will be set aside to settle expenses both parties might incure during the transfer process. Upon the receipt of your reply, I will send to you a detailed information about the transaction.I will not fail to bring to your notice that this business is 100% risk and trouble free and that you should not entertain any fear as all modalities for fund transfer can be finalized within 7 to 9 banking days, after you apply to the bank as the beneficiary of the fund from the deceased. When you receive this letter, Kindly send me an e-mail or you can call me or fax me. You should also include your private fax and phone numbers for easy and safe communication. TEL:870-763-648313 :870-763-648314. FAX:870-763-648315. Respectfully yours, Hartman Onowu. __________________________________ Do you Yahoo!? Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus


{% extends "wagtailbase/base.html" %}
{% block main %}
{{ block.super }}
{% block related_links %}
{% include "wagtailbase/includes/related_links.html" with related_links=self.related_links.all title="Related links" %}
{% endblock %}
{% block attachments %}
{% include "wagtailbase/includes/attachments.html" with attachments=self.attachments.all title="Attachments" %}
{% endblock %}
{% endblock %}


lap detection settings
the duration of the lap detection lock in milliseconds
rssi
current rssi value: 0
receiver
the frequency this tracker unit is listening to, must be between 5362 and 5945 MHz
wifi
only non standalone modethe wifi network this tracker unit is connecting to


{# `csrfmiddlewaretoken` is added back here because the `Redeem` #}
{# javascript component will look for it within the "#redeem-code" #}
{# element. #}
{% trans %}Have a registration code?{% endtrans %}
{# Implementation note: If we use `d-block` instead of #}
{# `style="display: block;"` the dropdown shows even when #}
{# `hasItems` is `False`. #}
{% endblock %}
{% block order_card %}
{% include "saas/_card_use.html" %}


Baffle adds an animated obfuscation effect to any text. Reload page to see effect. Apply these baffling classes!
.baffle - Baffles once upon page load.
.baffle-longer - Baffles once, but for a longer duration (3 seconds).
.baffle-prolonged - Baffles for a prolonged period.
.baffle-forever - .baffle-forever - Baffles endlessly.
Apply these classes to any text for a brutal text effect!
Default brutal (black) text
Brutal monochrome (blue) text
Brutal neon (lime) text
Truncate a paragraph of text to a preset number of characters. Requires start.brutalizing.js. Apply any of these classes to any text to truncate. Also supported: .chop-32 and .chop-512.
Lorem ipsum no facer prompta vim, movet ubique qui ei. Per no regione aliquid, ea mei nulla scribentur liberavisse. Vim cu tale ludus possit, discere suavitate nam ad. No verterem reprimique vix, phaedrum hendrerit an quo. Qui feugait apeirian ut, ne virtute numquam mandamus mea. Eos et enim dicant deterruisset.
Lorem ipsum no facer prompta vim, movet ubique qui ei. Per no regione aliquid, ea mei nulla scribentur liberavisse. Vim cu tale ludus possit, discere suavitate nam ad. No verterem reprimique vix, phaedrum hendrerit an quo. Qui feugait apeirian ut, ne virtute numquam mandamus mea. Eos et enim dicant deterruisset.
Lorem ipsum no facer prompta vim, movet ubique qui ei. Per no regione aliquid, ea mei nulla scribentur liberavisse. Vim cu tale ludus possit, discere suavitate nam ad. No verterem reprimique vix, phaedrum hendrerit an quo. Qui feugait apeirian ut, ne virtute numquam mandamus mea. Eos et enim dicant deterruisset.
Add a glitch effect to any element! Works on images and text, or even entire areas! It is entirely CSS-based. Apply .glitch class to any element.
Glitched Circle Image
Glitched Paragraph
This is a rather glitchy paragraph. You could even baffle all your firking enemies!
This paragraph has just one glitched word, using the span tag.
Blink is back! Apply theses classes to blink any element, even entire areas! Requires brutalist.js and start.brutalizing.js.
ALERT!
ALERT!
ALERT!
////////
WARNING!!!!
////////
Here is a fast-blinking span and image:
Get Your Blinker Fluid NOW!
Apply a throbbing, pulsing effect. It's CSS-based, so no javascript is needed. Simply apply this class to any element:
.throb
Spin any element constantly. Apply these classes:
.spin
.spin-reverse
.spin-fast
.spin-reverse-fast
.spin-cycle
Fittext makes any text aggressively responsive. Re-size your browser window to see them scale!
.fittext - Best scales text to fit within container.
Brutalist Framework
.fittext-compress - Increases compression.
Brutalist Framework
.fittext-uncompress - Decreases compression.
Brutalist Framework
Below are fittext classes that are ideal for H1 - H6 tags.
Rotate Text allows the rotation of text within an element.
Rotate Text requires javascript, and the markup uses data attributes to configure the settings. You will need to apply a unique ID to each individual Rotate Text element. The markup is as follows:

First Text Phrase

Second Phrase of Text

Last Text Phrase

Rotate Interval = 3000 = 3 seconds until next rotation
Rotate Animate - There are numerous animation styles supported. Consult animations.css.
Equal heights makes boxes the same height within a multi-column layout. In the example below, notice how all 3 column boxes have the same height.
.equal-height
Column One
This box has 2 lines of text
Column Two
This box has several lines of text.
Some small text.
Another small text line.
Column Three
This box has 2 lines of text
Apply these classes to add an animated gradient background to any element!
Let's get ready to rumble!
Brutalize any element by making it rumble! Simply apply the following classes to any element.


{% extends 'mail_templates/default_template.html' %}
{% load get_settings %}
{% block subject %}Hi!{% endblock %}
{% block top_running_title %}
{{ task.message.author }}
{{ task.dateCreate }}
{% endblock %}
{% block title %}Credits Hackathon registration!{% endblock %}
{% block content %}
Hi, thanks for registering in the hackathon! Here is a summary of the hax info for your convenience:
Web-page - https://opengift.io/credits-hackathon/
Date and time: 1st of December at 1 pm GMT
To all the Credits developers community out there and everyone who wishes to try out their skills at using the world’s fastest and most scalable blockchain platform! We are glad to announce the first Credits Developers Online Hackathon starting on December, 1.
Moreover, we plan to conduct Technical Webinars to help further understand our technology. Online sessions will be conducted via official Twitch channel (https://www.twitch.tv/creditscom/) and all videos will be uploaded to Youtube channel ( https://www.youtube.com/channel/UC7kjX_jgauCqmf_a4fqLGOQ ). Schedule of the webinars:


{% include 'defaultHead.html' %}
CookieJar is a simple tool that lets you grab cookies from browsers from different users, store them in a local sqlite database, and inject them again into any of the supported browsers. In the future, we will implement a feature to add cookies yourself, edit them, and inject these custom cookies as well.
We currently support Mozilla Firefox, Google Chrome and Chromium on Linux platforms and Mozilla Firefox and Google Chrome on Windows.
As with all tools, it can be used for good or evil. We are not responsible for your actions, so use the tool at own risk. Make sure you follow the privacy and computer laws of your country.


| Edition 2019-20 Edition 2020-21 |
A stochastic game (also: Markov game) is a generalisation of the concept of a repeated game. A stochastic game is a combination of (multi-state) reinforcement learning (as in Sutton and Barto) and Von Neumann game theory. With a stochastic game, the game in the next round (usually only the payoff matrix) depends on what happens in the current round. Stochastic games are perfect tools to model and program multi-agent reinforcement learning, such as learning in games of incomplete information. Card games, poker, backgammon, and simplified models of soccer are studied in this domain.
The theory of stochatic games is steep. This presentation is based on simple examples and merely scratches the surface of a deep subject.
Presented byLecturer. |
SlidesT.B.P. |
ScreencastNot available. |
AssignmentNot this year. |


Toggle navigation
WLM-WLMN
Terms
View all
Add new
Map
By country
By state
By city
Map count
By country
By state
By city
{% block body %}{% endblock %}
{# #} {% block scripts %}{% endblock %}


{% extends 'base-layout.html' %} {% block title %}Confirm delete{% endblock %} {% block content %}
Are you sure you want to delete that document?


This is the article archive of the100dayprojectpost list for the 100dayproject.
The GNU Compiler Collection includes front ends for C, C++, Objective-C, Fortran, Java, Ada, and Go, as well as libraries for these languages (libstdc++, libgcj,...). GCC was originally written as the compiler for the GNU operating system. The GNU system was developed to be 100% free software, free in the sense that it respects the user's freedom.
We strive to provide regular, high quality releases, which we want to work well on a variety of native and cross targets (including GNU/Linux), and encourage everyone to contribute changes or help testing GCC. Our sources are readily and freely available via SVN and weekly snapshots.
Major decisions about GCC are made by the steering committee, guided by the mission statement.


Use Rally Software? do stand-up Daily Scrum?
Remind yourself at a glance what you recently completed, and what's next on your iteration.
Android iPhone


| DOSE: |
2000 mg |
IM |
DXM |
(powder / crystals) |
I saw the experiences section of erowid and I thought I'd share a small warning with all of you on the value of moderation, and how you really shouldn't let emotions cloud your judgement with regards to the extent of the drugs you abuse or use.
My experience was in January 2001, near the end of the month, and my girlfriend of six months to whom I had become very attached split up from me. My mind was a complete wreck with confusion: 'why me?', 'what did I do to deserve this?', 'what did I do wrong, was I too caring, too loving?' and a whole train of similar thoughts and questions.
My weight had dropped drastically because I'd become anxious and depressed, through my job and relationship. I wasn't eating, and I was abusing other drugs quite heavily (namely shooting codeine & heroin intravenously - a source of great contentment and solitude on my part, injecting ketamine and drinking & smoking heavily)
This is where my mistake began - I hadn't eaten anything for 2 days so I was quite tired and lethargic, and I'd previously drank half a small bottle of whiskey.
At around 6pm I looked in my 'box of tricks' (my cute personal name for my small box where I kept all my drugs and paraphernalia) and all I had were some codeine I'd extracted and prepared for injection, and around what I thought was 6 grams of DXM powder in a little baggie, some lemon juice and around 5 .28g insulin syringes.
I took around one gram of DXM in a spoon, added the lj and cooked it up, sucked it into the syringe and put it onto my coffee table. I did the same and lay the two syringes side by side. I gave my ex a call because I felt so upset.
'She won't call', I thought to myself.  I waited a minute for the burning to subside and spiked my other shoulder. I sat on my sofa for what must have been 20 minutes before I felt the drug kicking in, and gave up on the notion that there was even the slightest chance my ex would call, so I took my clothes off and went to bed.
All seemed to be going ok for a while - I lost my grasp of time and place and completely forgot my misery. I felt very drowsy and light as I always do when I do robo.
I entered the world I'd left last week and the flora and fauna were there to welcome me.
Tere was one more entity there. I'd given it the name 'keeper of the gold'. I had to take its gold. It would make me a complete and happy person, not needing love for a while. I saw myself as a group of blue, four armed reptiles and touched this keeper.
I connected with the world, I was everywhere and I was everyone - I had all I needed inside this place and as I circled the planet absorbing enlightenment from all life, there was a very sudden interruption.
The telephone rang.
Having a caller display can be a good thing. Not now. I'll let mum downstairs answer it and I can go back to my world and forget everything.
Shouting from downstairs 'pick the phone up, it's your ex'
Oh christ. What do I do?
Shouting again.

I can't remember what she said. For the months previous she had no knowlege of my drug abuse and I kept it very secret. All I can remember her saying was 'are you sure you're alright'
My reply was 'yeh fine. Bye'
'Bye'
Ok now where was I?
Back to space I go..
I couldn't relax again. This was bad. I realised I'd taken way too much. My arms and legs were completely numb & my hands were twitching.
Am I going to vomit?
No I' fine. Lie there and relax a bit, you'll just have to sweat this out. Once you're capable of moving again take a paracetamol and the fever will go.
I got up and went to the window. My stomach was completely empty but I still managed to vomit and get rid of that awful pain in my stomach. My sister I think came in at that time and said 'hey, you've vomited on my window' (she was on the floor below).
All I said was 'go away' and she left.
The next thing I can remember was being forced to get dressed by my um and her boyfriend. I remember seeing my bedroom lit up with an air of righteousness, thinking of how this reminded me of my childhood and how mum always made me get up and get dressed.
Flashback...
All I saw was swirls for a few minutes. Fascinated by geometric patterns and the three witches who lived at the cliff (my ex, her mum and her sis).
Back to maladjusted reality.
I was in the car, looking around and I asked if I could have a cigarette. I was refused by the alien. It said 'DON'T FALL ASLEEP.
Blackout again...

I dozed off again, but not a dream, not a single vision. Not a thing, just quiet and solitude. 'Now that's what I wanted. I've got the gold. I've never felt so happy. Where is everyone, I have to tell them, to spread my happiness at least just a little, even to the people I hate. Everyone deserves to be happy like this, even if they've hurt me. I love my family, I love everyone I know'
I woke up to a strange being on a seat.
'Spike? Can you hear me?  I just wanted to feel better, please understand'
'I do'
(I remembered how my mum & dad had smoked cannabis in the past, how they'd once tried LSD and how my father in his younger days was constantly stoned. Maybe this would be justified in their minds)
'I'm going outside for a cigarette, now that you're awake. (my mother's boyfriend) can you keep an eye on him please?'
'Yeh' was his reply.
Slept again...
When I woke up, I asked 'where's (my mum's boyfriend)?'
'Out having a cigarette'
'Can I have one?'
'Wait three hours', was the reply
I had another thought. Was this the end of my hedonistic days? It was inevitable that I'd be rumbled sooner or later, because a life devoted to pleasure only holds so much before someone stops caring for that aspect of their lives and gets careless about keeping it a secret. I've been busted.
'I'm going to change. I need your help. I know it's a big favour but wasting my life, or any life for that matter is a big sin and I couldn't live with myself knowing that I'd done that. Please?'
I was told that yes, I was going to change otherwise both my parents would wipe their hands clean of me.
'Why am I so drowsy?'
'The doctors gave you some diazepam and paracetamol. It's the only treatent they could administer'
'When can I go home and have a cigarette?'
'Soon'
The rest I can't remember for the life of me.
For the next 24 hours I had to put up with both parents taunting me and saying how I'd fucked up, poisoning my body to escape from my problems.
And indeed it was true.
 Not their fault. Poison centers should have better resources I guess.
It's now 3 months later and I'm glad I've changed. I have a nice girlfriend I can take it slowly with, I haven't found a new job yet but things are looking hopeful there. When my parents said 'spike, you're a waste of an intensely clever mind', she was absolutely right. I was a waste. But no more. Now's the time to turn my life around and I can return to drugs later.
So what's this taught me? Well after much introspection, this is my conclusion:
1. Drugs are a good thing. If used right. If abused they're still a good thing.
2. NEVER 'eye out' your drug doses, especially when under the influence of another drug. It's at that time the drug becomes a poison.
3. Try first to deal with your problems in a sober manner. Escape is not the best way to do things but sometimes it helps.
4. Don't let drug use interfere with your day to day life. That road leads to one bunch of things: rehab (not nice, I was put into opiate detox and forced to subside on 60mg of methadone a day), counselling, which in itself is intrusive, unpleasant and upsetting, and sickness, I was told I had anorexia as well, which meant I was given marinol to try and increase my appetite. Lay your trust in me, methadone and marinol do not make you feel nice in combination, because you can't do anything else apart from lie around feeling tired and depressed. Methadone in itself is extremely efficant and marinol seemed to double the nausea for me, meaning that eating was still difficult but constant hunger got to me in the end and I put back on 10lbs at least, although I'm still underweight by a long shot.
5. Things don't stay bad. If you've reached your darkest hour then you have two choices - die, or get better: one of these will eventually happen.
6. Anything can be addictive. Anything pleasurable or contenting because people want to do it again and again.
I really hope this gets published. And I hope that whoever reads this if they think on my wavelength will take heed and learn moderation. This is needed because drugs especially are everywhere, from the stressed suit who needs his coffee at 2-hour periods, to the tripped out hippy who's lost touch with reality, to junkies whom I completely sympathise with because my philosophy used to be 'keep on going, shoot up get high, come down, steal, buy more drugs and do it again.'
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.


@import gospeak.core.domain.{Group, User, UserRequest} @import gospeak.web.pages.orga.routes.GroupCtrl @import gospeak.web.utils.UserReq @(invite: UserRequest.GroupInvite, group: Group, orga: User)(implicit req: UserReq[AnyContent])
Hi @orga.name.value,
@req.user.name.value has accepted your invitation to @group.name.value.
Together you are stronger, keep going!
The Gospeak team


|
MFixedPoint
|
Functions | |
| Fp64f & | mn::MFixedPoint::Fp64f< p >::operator+= (Fp64f r) |
| Override for "+=". More... | |
| Fp64f & | mn::MFixedPoint::Fp64f< p >::operator-= (Fp64f r) |
| Override for "-=". More... | |
| Fp64f & | mn::MFixedPoint::Fp64f< p >::operator*= (Fp64f r) |
| Override for "*=". More... | |
| Fp64f & | mn::MFixedPoint::Fp64f< p >::operator/= (Fp64f r) |
| Override for "/=". More... | |
| Fp64f & | mn::MFixedPoint::Fp64f< p >::operator%= (Fp64f r) |
| Override for "%=". More... | |
|
inline |
Override for "%=".
Definition at line 151 of file Fp64f.hpp.
References mn::MFixedPoint::Fp64f< p >::rawVal.
|
inline |
Override for "*=".
Used the FixMul() method.
Definition at line 136 of file Fp64f.hpp.
References mn::MFixedPoint::Fp64f< p >::rawVal.
|
inline |
Override for "+=".
Fixed-point addition and subtractional are done as usual.
Definition at line 120 of file Fp64f.hpp.
References mn::MFixedPoint::Fp64f< p >::rawVal.
|
inline |
Override for "-=".
Fixed-point addition and subtractional are done as usual.
Definition at line 128 of file Fp64f.hpp.
References mn::MFixedPoint::Fp64f< p >::rawVal.
|
inline |
Override for "/=".
Used the FixDiv() method.
Definition at line 144 of file Fp64f.hpp.
References mn::MFixedPoint::Fp64f< p >::rawVal.


| Program Name | Location | Started | Stopped |
|---|---|---|---|
|
Patient is not enrolled in any programs Press START NEW PROGRAM in bar above |
|||
{{department.name}} |
|||
| {{program.program.display}} | {{program.enrolledProgram.location?.display}} | {{program.enrolledProgram.dateEnrolled}} | {{program.enrolledProgram.dateCompleted}} |
Error loading patient program config. Please make sure that your network is working fine.


A great many Helm charts have sailed into the ocean of the internet, and while a growing number of publicly available charts is great for the community, it can be hard to know where they all are. To help solve that, Helm created Helm Hub - a central catalog or index of the growing number of publicly available Helm chart repositories. Browsing the Helm Hub UI, you can see how easy it is to find lots of great Kubernetes-ready apps. Through your browser, you can search for the publicly available charts you need and even find charts created by organizations. With such a large and growing set of listings, wouldn’t it be great if your build automation tools could use Helm Hub as the single central location to pull Helm charts for your entire organization? But that’s not easy to do; you can’t access Helm Hub through the Helm CLI. To remedy, this the JFrog Community Team has created the Helm Center - a free central repository for Helm Charts.
Screenshot
HelmCenter is similar to Helm Hub in the way that it gives access to Helm charts, but it’s a true central repository instead of just a catalog of charts - and it contains additional features such as:
To learn more about HelmCenter, read the blog posted by Helm co-founder Rimas M.


Members of the astronomy community have recently been tracking participation at conferences as a function of gender. This is intended to address some basic questions about behavior at conferences, such as:
In the broader sense, this is intended to measure if our collective behavior at conferences — in choosing speakers, engaging with them, and interacting with the audience — is as inclusive as it should be. If not, then hopefully the community can come up with some ideas of best practices to follow.
Data-gathering efforts were started by James Davenport at the 223rd American Astronomical Society (AAS) meeting in 2014, and repeated at the 225th AAS meeting in 2015 and the National Astronomy Meeting (NAM) in the UK in 2014. The data collected focus on question/answer sessions following oral presentations, since it's public, quantifiable, and one of the main methods of professional interaction. They found that men ask disproportionally more questions than women, and that the gender of the session chair has a strong impact on the gender ratio of questioners. However, there aren't any data (yet) on whether smaller, more specialized meetings follow the same trends as AAS and NAM, which are much larger and thematically broader.
I tracked this for a recent conference on "Unveiling the AGN-Galaxy Evolution Connection", held in Puerto Varas, Chile from 9-13 March 2015. A one-person team (me) kept track of the gender of speakers, chairs, and questioners for all of the 72 talks given at the conference (hereafter referred to as AGN2015).
The full data and analysis are openly available as a Github repo and iPython notebook. My short version of the conclusions:
I'm not sure what my expectations were in looking at data for a smaller, specialized meeting vs. a large general meeting like the AAS or NAM. I might have guessed that a smaller, specialized meeting would more subject to the whims of an SOC (who could be more likely to be senior and thus might tend to invite their peers, which would presumably skew the gender ratio). On the other hand, postdocs and early-career researchers might travel more (fewer teaching responsibilities mid-semester) and be more invested in giving talks to establish themselves for permanent jobs, which would skew toward younger people and a higher female-male ratio. The demographics of the AGN/galaxy community, the relatively remote conference location in South America, and the timing of the meeting are all priors that should probably be taken into account.
The main negative was that the session chairs were overwhelmingly male (a possible reflection of a seniority bias). However, this is presumably simpler to correct for an SOC/LOC, is subject to small sample size variance, and doesn't appear to have affected the engagement with the audience, which is good. I also want to note for AGN2015, all the three end-of-day discussions were moderated by women, as was the conference summary. My unofficial impression is that this conference had a moderately younger-than-average age, especially among speakers. The targeted talks at this conference were unofficially designated as being reserved for "young people doing cool things" by the SOC. I'd love to see more of that in every conference, since I think it'd help with both scientific output and participant balance.
One extremely important point is that this is a sample size of N=1. We need similar data on other conferences, in different subfields, different parts of the world, and different conference structures. Unlike at the large meetings, data collection can pretty easily be done by one person, and I want to develop some standard plots and questions we can ask through open data sets (all of this data/analysis is available online). I hope other astronomers are willing to track this at future conferences; if so, please feel free to clone this dataset and analysis tools we can keep tracking this. I'm happy to help anyone who's interested in taking part.
So maybe smaller conferences are better at gender balance and engagement than larger meetings? Maybe — but we need lots more data to see if this effect is real, and to help guide what the astro community can do in the future.
Thanks to Ezequiel Triester and the conference organizers of AGN2015 for having me at the meeting, to Meg Urry for presenting some of these results in her conference summary, and to James Davenport, Jonathan Pritchard, and Karen Masters for their previous hard work at the AAS and NAM meetings. -KW
I tracked gender participation for five aspects of the question/answer sessions:
Every one of these categories had more male than female participants. The gender ratio of the speakers closely matched that of the attendees as a whole (45% and 43%, respectively).
Women were slightly less likely to ask questions than men; women constituted 43% of the attendees, but only 35% of the people asking questions.
The gender of people who asked the first question in a given session is close to that of the overall gender of questioners (38% vs 35%).
The data from the 225th AAS meeting did not track the gender of either the session chair or the total number of attendees. The AGN2015 meeting had a higher proportion of women for both the speakers (45% to 38%) and the people asking questions (35% to 19%).
The NAM 2014 meeting tracked data in an identical format to AGN2015. The AGN2015 meeting had a higher percentage of women for speakers, attendees, and question askers. In particular, the gender distribution of people asking questions is twice as high for AGN2015 (35%) as for NAM (17%). This is driven by the large disparity in gender distribution between attendees and questioners at NAM. The gender of the session chairs is the only category in which NAM has a higher percentage of females than AGN2015. However, there were only 14 sessions at AGN2015, compared to 64 sessions at NAM. Some (although likely not all) of the high fraction of males at AGN2015 may be due to the smaller sample size.
Finally, I looked at the gender representation compared to the most recent data for members of the International Astronomical Union (IAU). The IAU is 85% male/15% female, a distribution significantly in excess of every demographic category measured for AGN2015. Membership in the IAU is likely not indicative of the astronomical community, especially since the requirements involve nominations by national professional organizations and thus skew toward more senior astronomers (which are more likely to be male).
Engagement with the speakers was nicely high at the AGN2015 conference, with an average of 3 questions per talk being asked. This was higher than the averages for both the NAM (2.2±1.1) and AAS (2.8±1.5) meetings. The number of questions per talk was slightly higher when the speaker was female instead of male, with 3.3 compared to 2.8. However, a two-sided Kolmogorov-Smirnov test gives a 41% chance that the two samples are drawn from the same distribution, with no indication of a statistically significant difference.
A difference in the number of questions per talk depending on the speaker might be interpreted as either a positive or negative effect (preferentially ignoring speakers of certain genders, overaggressively questioning/harassing them, paying attention and engaging with them, etc). More analysis on this data would be pure speculation from me as to which might be responsible.
When women ask the first question in a session, women ask on average 40% of the total number of questions in such sessions. However, when men ask the first question in a session, women only ask 31% of the total questions in the session.
But this is clearly affected by the fact that the gender of the first question is fixed. To isolate that effect, let's look at the remaining questions in the session.
When the first question is eliminated from the data, the fraction of questions asked by females are nearly identical for females and males (33% and 36%, respectively). A two-proportion z-test indicates the distributions cannot reject the null hypothesis at <1σ.
This result differs from the AAS meeting data, who found an extremely strong difference between the two. If the first question was asked by a male, then only 10% of the remaining questions were asked by a female. If the first question was asked by a female, 49% of the remaining questions were asked by a female.
When looking at the gender of the session chair (who might have selection biases when there are more questions than time permits), there is no difference in the gender distribution of questioners. In this case the data are nearly identical for male vs. female chairs, at 36% and 35% females respectively.
This null result differs from the NAM data, who saw a small but significant decrease in the fraction of females asking questions when the chair was male (16%) as opposed to a female chair (22%).


W3C
In 1993 the World Wide Web Consortium (W3C) by Tim Berners-Lee (inventor of the internet). The idea of the W3C was to standardize protocols and the technologies used to create the web. The idea of HTML 4.01, PNG images and Cascading Style Sheets (CSS) were all part of the W3C.
By 2000 Internet Explorer 5 was released and featured great support for HMTL and CSS. The W3C changed to the use of XHTML which features much greater capabilities to web pages. XHTML had many flaws, it was not backwards compatible and it did not work properly on Internet Explorer.
In 2004 many representatives from Apple, Opera and Firefox gathered to make a HTML system that would add even more features but also make it backwards compatible. By 2007 about 3,000 people had come together to build what is now HTML 5.
HTML 5 was designed to make an innovative and standard web creation process for all developers. This allows many more features to be used by anyone on any web browser. They work by allowing the users and developers to speak up and contribute to make a standardized HTML web.
Features of HTML 5
Backwards compatibility
Ability to code games without the need for flash or JavaScript
Better for dynamic apps, websites with moving and interactive elements
Cleaner code, less is needed for the same code in HTML 4


Numbers 14:37
Even those men that did bring up the evil report upon the land, died by the plague before the LORD.


He was born on December 4, 1991. A graduate with a bachelor’s degree in Culinary Arts at De La Salle-College of Saint Benilde. He has worked in The Aristocrat Restaurant in Manila as an assistant chef. He decided to go back to Laguna to start his own business which led to him being the co-founder of Confection Room. He, along with Mr. Rebong, is responsible with the creation of the macarons that will be sold.
To know more about him click the link below and don't hesitate to ask some question.


django-oscar-sagepay ships with an optional custom tag that displays a banner dictating what checkout mode you are running. For example, if you are running in simulator mode i.e. SAGEPAY_MODE = 'Simulator' a message banner could be displayed on the payment details view.
The banner is not installed by default and is entirely optional. To add the checkout banner simply add the tage to the required view:
{% load checkout_mode_tag %}
{{ bankcard_form.as_table }}
Another example would be to add the custom tag the payment details template:
{% load checkout_mode_tag %}
{% block payment_details_content %}
{% banner %}
<form action="{% url 'checkout:preview' %}" class="form-stacked" method="POST">
{% csrf_token %}
{{ bankcard_form.as_table }}
</form>
{% endblock %}


1
go to
Step:
0
Debug load address:
Random
Fixed
Seed:
Pause
Step
Speed:
0
Hex
Dec
AX:
BX:
CX:
DX:
SI:
DI:
BP:
SP:
CS:
DS:
SS:
ES:
IP:
Energy:
Flags:
OF
DF
IF
TF
SF
ZF
AF
PF
CF
Stack
Shared Memory
Watch
Competition
Debug
Zombies
Competition
Start!
Battles to run:


--- title: 'Committer Panel from PhoneGap Day EU 2012' author: Steve Gill format: html tags: - Video - Event - PhoneGap Day ---
Thank you to everyone who attended PhoneGap Day EU and made it such a huge success. Here's the next video in our series.
Cordova committers Brian LeRoux, Pat Mueller, Dave Johnson, Gord Tanner and others come on stage to answer all questions from the audience. Learn more by watching the recording from PhoneGap Day EU below


The terms "enqueue" and "dequeue" are associated with which data structure?
What does "enqueue" and "dequeue" mean?


The four file lists on CIX relevant to file list maintenance are:
The File Directory
Commonly known as the fdir. This is the actual directory on CIX where files uploaded to a topic are stored; CIX creates the list dynamically every time Moderate requests it to be downloaded. When you are editing the file list in Moderate, you can choose files from here to add to the file list visible to users.
The fdir is stored on your computer as <topic root>.fld in the flist subdirectory of you Ameol data directory.
The Filepool
This is a pool of files held on CIX that is accessible from any topic file list. Files of general interest can be exported here from a topic file list whereupon they can be included in the file list of any other topic.
The CIX forum filepool maps directly onto the filepool; if a user uploads a file to the 2newfiles topic of this forum, it can be accessed by moderators of any forum on CIX.
Moderate doesn't keep a copy of the filepool fdir on your computer; if you want to add filepool files to your topic file list, you have to type the file's name in yourself.
The Moderator's File List
This is the file list you actually edit in Moderate. CIX uses it to create the users' file list whenever a copy is requested; the file references in the moderator's file list are matched against the files in the fdir or filepool and the list as displayed by Topic File List in Ameol is created.
The moderator's file list is stored on your computer as <topic root>.flm in the flist subdirectory of you Ameol data directory; a single backup copy is also kept by Moderate as <topic root>.flb.
The Users' File List
This is the file list that is displayed by Ameol's Topic File List command, and the only list from which your forum participants can download files. CIX generates it dynamically from the moderator's file list, the fdir and the filepool whenever Ameol requests a copy.
The users' file list is stored on your computer as <topic root>.fls in the flist subdirectory of your Ameol data directory.


The first function of the package is m1_emissions_rescale
. It re-scales emissions from GCAM regions to TM5-FASST regions which is the purpose of Module 1.
The function processes emissions outputs from GCAM to make them match with the regional disaggregation of TM5-FASST. Concretely, GCAM emissions are downscaled to country level, using a static downscaling approach based on the pollutant-specific country-level emissions in year 2000 reported in the RCP database. This approach is planned to be revised in the future, for example with the implementation a dynamic GDP-based downscaling procedure linked with the scenario-specific socioeconomic data in GCAM.
Apart from the regional adjustments, this function makes some additional pollutant-related changes such as the transformation of organic carbon into organic matter.
Inputs:
Outputs:
The function produces re-scaled emissions of the main pollutants for each period and TM5-FASST region. If saveOutput
is set to TRUE
, the function writes the following csv files in the output/m1
sub-directory: [scenario]_[year].csv
The outputs from this module generated with the function m1_emissions_rescale
are going to read by the set of functions in Module 2, which calculate PM2.5 and O3 average concentration levels based on these emission sets.
library(rfasst)
library(magrittr)
# db_path<-"path_to_your_gcam_database"
# query_path<-"path_to_your_gcam_queries_file"
# db_name<-"name of the database"
# prj_name<-"name for a Project to add extracted results to" (any name should work, avoid spaces just in case)
# scen_name<-"name of the GCAM scenario",
# queries<-"Name of the query file" (the package includes a default query file that includes all the queries required in every function in the packae, "queries_rfasst.xml")
# To write the re-scaled emissions (csv files) for all years into the output folder:
# m1_emissions_rescale(db_path,query_path,db_name,prj_name,scen_name,queries,saveOutput=T)
# To save as data frame emisions of main pollutants by TM5-FASST region in 2050:
# em.2050<-dplyr::bind_rows(m1_emissions_rescale(db_path,query_path,db_name,prj_name,scen_name,queries,saveOutput=F)) %>% dplyr::filter(year==2050)
# head(m1_emissions_rescale)


constructor Create(AOwner: TComponent); override;
Creates an instance of TCustomImage32.
After calling the inherited constructor, Create initializes the following properties:
[See also]:


--- layout: post esbma_id: 1167 title: Going to a Trade Show date: 2004-05-28 15:53:45 keywords: mfg_marcomm bos teaser: Trade shows are my favorite of the basic "marcomm" tools because they are so interactive. Advertising and PR are primarily one-way communication, from you to the customer, without much chance for information to flow the other way. Other marcomm tools certainly have their place, but there is nothing like a trade show. ---
Summary: Writing daily from Tech-Ed 2004, Eric gives you tips and advice about exhibiting at trade shows, drawing from his experiences at this show, as well as past events.
I arrived in San Diego yesterday for Tech Ed 2004 where SourceGear will be an exhibitor. Like most events of this kind, Tech-Ed is both a "conference" and a "trade show". The conference portion consists of scores of Microsoft product managers telling the attendees how great Microsoft technologies are. The trade show portion consists of scores of companies telling the attendees how great their products are. The mixture of these two ingredients has attracted over 10,000 geeks like me who are now swarming around downtown San Diego wearing really dorky badges around our necks.
I'm still sitting in my hotel room at the US Grant. The exhibit hall opens at noon. We did most of the setup of our booth yesterday afternoon, so we're pretty much ready to go. I've got a few hours this morning so I need to spend some time working on this article. It's due Thursday.
Trade shows are my favorite of the basic "marcomm" (marketing communications) tools because they are so interactive. Advertising and PR are primarily one-way communication, from you to the customer, without much chance for information to flow the other way. In contrast, a trade show offers face time. Coming to the show this week will give us the opportunity to meet in person with prospective customers. They will tell us their opinion of our product. They'll ask for features we don't have. We'll have the increasingly rare opportunity to experience the people in our market segment as real people.
We also get face time with our competitors and partners. We get the chance to see a broad spectrum of companies in our space and observe what they are all doing.
We also get face time with some of our existing customers. Throughout this week, people who already use our products will be stopping by the booth to chat. Some will simply want to meet us in person. Some will tell us how happy they are with the product. Some will tell us how we have disappointed them in some way.
The entire package provides us a perspective that cannot be obtained in any other way. Other marcomm tools certainly have their place, but there is nothing like a trade show. In this column, I will talk about trade shows as a marketing tool for your small ISV. I will share several stories from my own experience, as well as some tips for how to get started in trade shows.
After you decide you want to try exhibiting at a trade show, your next decision is to figure out which one. Regardless of your particular market segment, there are almost certainly a variety of shows from which you can choose. SourceGear is a developer tools company in the Microsoft ecosystem, so we choose our shows accordingly. We basically always have a booth at Tech-Ed and at the Professional Developers Conference (PDC). Sometimes we do a booth at VSLive as well.
I recommend that you attend a trade show before you commit to being an exhibitor. Spend plenty of time walking around the show floor and observing carefully. Bring a digital camera and take lots of pictures. Critique the booths of other vendors. Pay attention to what they are doing and whether or not it seems to be working well for them.
Exhibiting at a trade show is both cheap and expensive.
It's cheap because it is a one-shot expense. Contrast this with advertising where the magazine's sales guy is going to try to convince you to buy an ad every month for an entire year. A trade show is a single event, with no lingering commitments to annoy you later.
But trade shows are still awfully expensive. If the idea of spending $10,000 on a trade show appearance sounds scary, then you may want to look elsewhere. At some shows you can probably spend less, but not by much.
Over the last few years, SourceGear usually spends between $25,000--30,000 (US) for each trade show appearance. This week, we wanted to simplify things a bit, so we chose to have a 10-ft.-by-10-ft. booth (10x10) instead of our usual 10x20. I think we'll end up spending between $15,000--20,000 dollars for this show.
But the opportunity to spend more is almost unlimited. The "gold" sponsors at this show probably spent several hundred thousand dollars this week.
I still remember one show where we probably spent a little too much. People at the company started getting crabby as the expenses kept rising. When it came time to make the travel arrangements, I asked if we needed a rental car in Los Angeles. One of my partners sarcastically asked why we didn't just wait till we got out there and buy one.
Preparation for this event started several months ago. We registered as an exhibitor on January 26th. Payment for the booth space itself was due immediately. The cost was $6,995 for the booth itself, plus $300 rental fee for a table and two chairs. If the pricing of that furniture seems outrageous, get used to it. You can rent all kinds of stuff for your booth, including furniture, equipment, and more. The rule of thumb is that the weekly rental fee will be approximately the same as the price of buying the item new. It stings, but the principle here is the same as the reason you pay five bucks for a hot dog at a baseball game--it's their convention center, not yours.
After we have registered as an exhibitor, we know that we have reserved our booth space, but we do not know yet where it will be. Booth selection usually takes place several weeks after registration. This year, Tech-Ed allowed exhibitors to choose booths in approximately the order that we registered. SourceGear ended up in the third wave of booth selection, which opened at 11:00 a.m. Pacific Time on February 25th.
Considering the amount of money you're paying, it makes sense to try and get the best booth location you can. Usually you can see the map of the trade show floor in advance and identify two or three desirable locations. It's usually better to try and get a booth on the end of a row. Try to be in a high traffic location, such as near an entrance or other item of interest.
If the booth selection Web site opens at 11:00 a.m., you should be there at 10:55 a.m. with your finger poised over the mouse. Our booth selection opened right on time, and I grabbed our desired booth within seconds. We ended up with booth 1743, directly across from the Visual Studio kiosks in the Microsoft pavilion. Except for the giant pillar which somewhat impairs the visibility of our booth, this location is perfect for us.
After booth selection, you will receive an exhibitor's guide of some kind. This is usually a small book containing all kinds of information you need to be prepared for the show. The most important thing in that guide is the calendar of deadlines. This will tell you the last day for each thing you need to do. For example, if you want to purchase an advertisement in the conference guide, there will be a deadline for registering for this additional service.
The job description for people who deliver the San Diego weather report on television involves two simple responsibilities:
Today is one of those days when it is 68 degrees and cloudy. In Illinois, we get three days a year where the weather is this nice, but since this is approximately the worst weather San Diego has to offer, the locals describe this as "bad weather". Nonetheless, the walk from my hotel to the convention center was unbelievably pleasant. I am now sitting in the SourceGear booth drinking coffee. I still need to finish a couple more details on the setup of our booth.
When I stop to think about it, the word "booth" is a strange term for the piece of floor space we have rented. It is a square, 10 feet long and 10 feet deep, with blue carpeting covering the floor. The back of the booth is a black curtain, approximately eight feet tall. Another much shorter curtain marks the boundary between our booth and the one next door. There is an electrical cord and an Ethernet cable.
Everything else is in the booth is your responsibility, and there is a wide range of choices available. If you want furniture, banners, signs, computers or televisions, you have to rent them or bring them with you. Most of the booths larger than 10x10 are filled with professional systems that integrate furniture and visuals. The PatchLink booth here is really outrageous. It has a stairway to a second floor that contains an observation deck of some kind.
Many of the 10x10 booths use a professional system as well, albeit on a smaller scale. Our booth has a folding backdrop with vertical panels that we printed with our company graphics. This system set us back around $10,000 or so, but we've been able to use it many times.
Some of the 10x10 booths are much simpler. Many companies simply rent furniture from the convention center and hang up printed banners and signs. We've done quite a few shows this way. This approach is cheap but the results can be very professional. I always recommend people start out this way for their first show. Keep it simple until you are really comfortable with how things are done at these events.
If your booth is going to have computers or fancy backdrops, you will have more stuff than you can carry in your luggage, so you'll have to ship things to the show site in advance. For this show, we shipped three crates and two boxes, totaling about 500 pounds or so. I haven't seen the actual shipping costs yet, but we did get our stuff shipped out by the first shipping deadline. Waiting until the very last shipping deadline will cost you more.
The exhibitor guide will tell you whom to call to schedule the pickup of your stuff. A big truck will show up and take your boxes and crates away. From that moment until the moment you arrive on the trade show floor, you will worry about whether your stuff will be there complete, intact, and on time. This actually happened to us at the PDC last fall. Most of our boxes were missing in action when we arrived at the booth for setup. Don't plan to arrive at the show at the last minute. If your boxes got lost, you'll need extra time to track them down.
The worst thing you can do at a trade show is to be boring. I won't name names, but there are some booths here that are really easy to ignore. I always find this to be somewhat sad. Renting space here is not cheap. It's important to find a way to be interesting.
Companies do all kinds of things to draw attention to their booths, with varying results. In the sections below, I describe a few things which have worked for us and a few things that don't seem very effective.
At Tech-Ed two years ago we made our first announcement of SourceGear Vault. Because we made this announcement over six months before shipping the product, we knew we would be criticized for hyping our "vaporware". So we decided that it would be easier if we made the joke ourselves. We bought a fog machine and spent the week standing in a booth filled with wispy vapor rolling around. Our booth was awfully hard to ignore, and we got the opportunity to tell lots of people about our upcoming product.
Self-deprecation is safer, but sometimes you can make use of a good-natured joke at someone else's expense.
At Tech-Ed last year, somebody at Microsoft introduced a marketing campaign that simply had to be the target of a parody. They selected several well-known gurus and declared them to be "Software Legends". The convention center was filled with life-sized cardboard cutouts of these legends, each of which directed people to visit the Web site at softwarelegends.com.
I tried to resist the temptation, but in the end, this target was just too easy. We created a parody Web site at notalegend.com and showed up at Gnomedex with a life-sized cardboard cut-out of me. This joke ended up being a huge hit. Even now, almost a year later, about a dozen people approached me this week to tell me how funny that was.
But do be careful about causing offense. Burning bridges is always a mistake. I have had the chance to speak with several of the software legends and the people who produced the campaign. I am delighted to report that no one was offended by our spoof.
The concept for the promotional campaign for Vault was to advertise the product as if it were a movie. The product packaging is a DVD-style case. We made movie posters with that distinctive typeface at the bottom. The magazine advertisement was a variant of the poster. But most importantly, we produced a brief movie trailer that we have shown on a plasma screen at several trade shows.
Although we often hear glowing praise for this campaign, not everything about it was as successful as we hoped. Some trade show attendees didn't want to stand still long enough to watch the trailer. Some people didn't accept our poster giveaway because it was too big to carry around.
But in general, this effort has brought outstanding results. The best part of the whole campaign was the voice-over for the trailer. As people stand in our booth and watch the video, they suddenly realize they have heard the voice before. The voice in our trailer is Hal Douglas, the same voice that is heard in many of the actual Hollywood movie trailers. He is also the guy who appears in the movie trailer for Comedian, which, incidentally, is truly hilarious.
The original budget for the Vault promotion and launch was $85,000, but we ended up spending about $89,200. The difference was Hal's fee for 20 minutes of work, and it was worth every penny. His voice eliminated all chance of our movie trailer being cheesy or amateurish. We've used it for several shows now, and the Vault movie trailer has been a great tool in making our booth interesting.
People go to all kinds of measures to counteract the sheer boredom factor of their booth. The most common approach is to give stuff away. As I look around the show floor, I see the usual array of people who visit booths for the specific purpose of collection T-shirts, rubber balls, hats, and everything else they can find. We've done this in the past, but I have always had questions about the effectiveness of this approach. The obvious concern is that freebies do little more than attract people who are simply searching for freebies.
Yesterday, somebody walked slowly by our booth, carefully keeping his distance to ensure that we did not speak to him. As he walked by, he scanned our signs and materials and apparently decided quite clearly that he was not interested in our products. He maintained his speed and proceeded to the next booth.
And then he noticed the baseball cap sitting on our table. Baseball caps are a popular freebie this year, so he assumed we must be giving them away. He stopped, turned around, approached our table and asked us what he had to do in order to get a free cap. Ironically, that baseball cap wasn't even ours. It belonged to a customer who had simply placed it on the table as he was talking with us.
Another popular alternative to being interesting is to collect business cards for a prize drawing. I'll confess that this approach usually seems downright silly to me. For example, the booth next to ours is giving away an iPod. Drop your business card in a fishbowl. At the end of the week, one card will be drawn and the winner will get the prize. Later, all those business cards will probably get handed to some sales guy who will use them to pester people.
If this technique works for them, great, but I am honestly not fond of it. In this case, the iPod has absolutely nothing to do with their business. They have artificially increased the quantity of their booth traffic, but not the quality.
In my opinion, the absolute worst way to generate artificial interest is the tactic that is commonly known as the "booth babe". The basic idea is to staff the booth with an extraordinarily attractive woman. In many cases, the woman is a little-known model or actress who was hired for the week and knows absolutely nothing about the company's products.
Thankfully, I don't see this classless tactic happening here at Tech-Ed this week, but I've seen it at various shows before. Please don't do it. I'm not saying you have to go out of your way to staff your booth with ugly people. I just think people like companies who recognize that their customers are smart. Staff your booth with the right people to talk about your products.
So far, the show is working out pretty well for us. The traffic in our booth has been okay, but not extraordinary. Tech-Ed usually isn't a truly high-traffic show for us. The crowd here is a mix of developers and information technology (IT) people, but our product only appeals to the developer side. This illustrates a point about trade show audiences that ends up being true more often than not: rare is the show that can deliver you several thousand people with absolutely all of them being potential customers.
Since SourceGear is a developer tools company, we only attend shows where a significant percentage of the attendees are software developers. We further constrain our choices to the shows which are Microsoft-centric, since that fits our product positioning.
However, I suspect that at least some of my readers are selling products intended for normal people. I don't know the landscape for other shows, but I do know that basically every significant market uses trade-show events. For example, I recently attended a woodworking trade show. In many ways, it was very similar to my own experiences, albeit with fewer laptops and more sawdust.
I really like to use trade shows as deadlines for project milestones. Sometimes we tie the actual product ship date to the date of the show. On other occasions we simply use the show date as an interim milestone. Either way, the opportunity to show a product to customers provides a nice incentive to get things completed and polished. This week, we decided to begin telling people about our upcoming bug-tracking product here at Tech-Ed.
I don't believe in project scheduling that is 100% date-constrained. However, a little date pressure can help drive things to closure. The trade-show date is completely immovable. Ludicrous as it may sound, I remember a couple of times where I wanted very badly to call Microsoft people and ask them to push an event back a week to give us more time.
Attaching this milestone to Tech-Ed forced us to make a decision about the official product name for our bug-tracking system. We've had an internal code name all along, but we really wanted to finalize the actual name before we showed it to customers. At the last possible moment, we decided Friday morning the name would be "Dragnet". We rushed our data sheets to the printers, picked them up later Friday afternoon, and I brought them to the show in my luggage.
When I first got started writing for MSDN, I was unaccustomed to working under a deadline. For my first article, the due date arrived and I think my editors expected me to submit the article that morning. By now they understand that when I said I would submit my article today, I meant that it would sent by the end of the business day as defined in the Hawaiian time zone. So I've still got several hours left to get this wrapped up, but at this point, I think I will make it without having to ask for an extension (again).
This is the last day of the show. I am reminded once again why I like trade shows so much. Just as I mentioned last month, there is an old saying about pizza and sex: "When it's good, it's good, and when it's bad, it's still pretty good". I think the same thing can be said of trade shows. This week's event has frankly not been our most successful show. Booth traffic has been okay, but not great.
But the show has still been pretty good. We talked to lots of potential customers and told them about our products. Some of our current customers stopped by to say hello. We got to see a whole bunch of interesting people from blogspace, including Chris Kinsman, Julia Lerman, John Bristowe, and Korby Parnell. We had some great conversations with folks on the Visual Studio team. We took a walk and saw a seagull. We ate dinner at an unbelievably good Brazilian restaurant. We had a nice chat with one of our competitors.
My point here is this: There is a strong temptation to try to measure the success of a trade show appearance strictly in dollars from new sales leads generated at the show. If you really want to do it this way, I won't stop you, but I think you're missing the point. There are intangible benefits to appearing at a trade show that are very hard to quantify. If we talked ourselves out of future trade show appearances simply because we didn't generate enough sales to cover our direct costs, we would miss out on those intangibles.
The show will officially close at 3:30 p.m. this afternoon. At 3:31 p.m., things will be crazy. People will start tearing down their booths immediately. The carpets will be rolled up and carried away. Table covers will be removed, revealing that the $300 rented table underneath is actually worth about twenty bucks.
Luckily, teardown is a lot easier than setup.
My favorite part of teardown is folding the backdrop. When fully extended, our backdrop is about ten feet wide and seven feet tall. This afternoon I will unhook three connectors and then give the whole structure a little nudge and watch as it quietly collapses to something about the size of a bed pillow. It's so cool.
The very last step is to put shipping labels on our crates and walk away. It always feels strange to just abandon them there on the floor, but somehow they always seem to make it back to our office.
Eric Sink is the non-legendary founder of SourceGear, a developer tools ISV located in Illinois. Despite his obvious disdain for Illinois weather, Eric still thinks the best part of every trade show is coming home to his wife and daughters. Eric's weblog is at https://ericsink.com/.
This article originally appeared on the MSDN website.


|
CUTLASS
CUDA Templates for Linear Algebra Subroutines and Solvers
|
#include <matrix_coord.h>
Public Types | |
| using | Index = int |
| Integer-valued index. More... | |
| using | Base = Coord< 2, Index > |
| Base type is a Coord of rank=2. More... | |
| Public Types inherited from cutlass::Coord< 2, int > | |
| using | Index = int |
| Index type used to store elements. More... | |
| using | LongIndex = int64_t |
| Type used to represent linear offsets. More... | |
Public Member Functions | |
| CUTLASS_HOST_DEVICE | MatrixCoord () |
| Default ctor. More... | |
| CUTLASS_HOST_DEVICE | MatrixCoord (Coord< 2, Index > const &coord) |
| Constructs from Coord<2> More... | |
| CUTLASS_HOST_DEVICE | MatrixCoord (Index row, Index column) |
| Helper to construct from a row and column. More... | |
| CUTLASS_HOST_DEVICE Index const & | row () const |
| Returns the row of the coordinate. More... | |
| CUTLASS_HOST_DEVICE Index & | row () |
| Returns the row of the coordinate. More... | |
| CUTLASS_HOST_DEVICE Index const & | column () const |
| Returns the column of the coordinate. More... | |
| CUTLASS_HOST_DEVICE Index & | column () |
| Returns the column of the coordinate. More... | |
| CUTLASS_HOST_DEVICE MatrixCoord | operator+ (Base const &b) const |
| Element-wise addition. More... | |
| CUTLASS_HOST_DEVICE MatrixCoord | operator- (Base const &b) const |
| Element-wise subtraction. More... | |
| CUTLASS_HOST_DEVICE MatrixCoord | operator* (Base const &b) const |
| Element-wise multiplication. More... | |
| CUTLASS_HOST_DEVICE MatrixCoord | operator/ (Base const &b) const |
| Element-wise division. More... | |
| CUTLASS_HOST_DEVICE MatrixCoord & | operator+= (Base const &b) |
| In-place addition. More... | |
| CUTLASS_HOST_DEVICE MatrixCoord & | operator-= (Base const &b) |
| In-place subtraction. More... | |
| CUTLASS_HOST_DEVICE MatrixCoord & | operator*= (Base const &b) |
| In-place multiplication. More... | |
| CUTLASS_HOST_DEVICE MatrixCoord & | operator/= (Base const &b) |
| In-place division. More... | |
| Public Member Functions inherited from cutlass::Coord< 2, int > | |
| CUTLASS_HOST_DEVICE | Coord (Index value=Index(0)) |
| Default ctor initializes uniformly. More... | |
| CUTLASS_HOST_DEVICE | Coord (Index const (&_idx)[kRank]) |
| Constructs from an array of integers. More... | |
| CUTLASS_HOST_DEVICE | Coord (Coord< kRank, Index, LongIndex > const &coord) |
| Copy constructor. More... | |
| CUTLASS_HOST_DEVICE Coord< Slice > | slice (int start=0, Index identity=0) const |
| CUTLASS_HOST_DEVICE int | min_dim_index () const |
| Returns the index of the dimension with least value. More... | |
| CUTLASS_HOST_DEVICE int | max_dim_index () const |
| Returns the index of the dimension with greatest value. More... | |
| CUTLASS_HOST_DEVICE | operator bool () const |
| Returns true if Coord is non-zero. More... | |
| CUTLASS_HOST_DEVICE bool | operator! () const |
| Returns true if Coord is uniformly zero. More... | |
| CUTLASS_HOST_DEVICE Coord | operator+ (Coord const &b) const |
| Element-wise addition. More... | |
| CUTLASS_HOST_DEVICE Coord | operator- (Coord const &b) const |
| Element-wise subtraction. More... | |
| CUTLASS_HOST_DEVICE Coord | operator* (Coord const &b) const |
| Element-wise multiplication. More... | |
| CUTLASS_HOST_DEVICE Coord | operator/ (Coord const &b) const |
| Element-wise division. More... | |
| CUTLASS_HOST_DEVICE Coord & | operator+= (Coord const &b) |
| In-place addition. More... | |
| CUTLASS_HOST_DEVICE Coord & | operator-= (Coord const &b) |
| In-place subtraction. More... | |
| CUTLASS_HOST_DEVICE Coord & | operator*= (Coord const &b) |
| In-place multiplication. More... | |
| CUTLASS_HOST_DEVICE Coord & | operator/= (Coord const &b) |
| In-place division. More... | |
| CUTLASS_HOST_DEVICE Index & | operator[] (int dim) |
| Member access operator. More... | |
| CUTLASS_HOST_DEVICE Index const & | operator[] (int dim) const |
| Member access operator. More... | |
| CUTLASS_HOST_DEVICE LongIndex | dot (Coord const &b, LongIndex sum=LongIndex(0)) const |
| Computes the dot product with anotherCoord object. More... | |
| CUTLASS_HOST_DEVICE Index & | at () |
| Gets the index of a given Coord element. More... | |
| CUTLASS_HOST_DEVICE Index & | at (int dim) |
| Access via index; may limit unrolling potential. More... | |
| CUTLASS_HOST_DEVICE Index const & | at () const |
| Gets the index of a given Coord element. More... | |
| CUTLASS_HOST_DEVICE Index const & | at (int dim) const |
| Access via index; may limit unrolling potential. More... | |
| CUTLASS_HOST_DEVICE bool | operator== (Coord const &b) const |
| Determines if two Coord<> objects are equal. More... | |
| CUTLASS_HOST_DEVICE bool | operator!= (Coord const &b) const |
| Not equal. More... | |
| CUTLASS_HOST_DEVICE Coord & | clamp (Coord const &max, Coord const &min=Coord()) |
| Clamps a coordinate to a range specified by maximum and minimum values. More... | |
| CUTLASS_HOST_DEVICE Index | sum () const |
| Returns the sum of all elements. More... | |
| CUTLASS_HOST_DEVICE LongIndex | product () const |
| Returns the product of all elements. More... | |
| CUTLASS_HOST_DEVICE bool | operator< (Coord const &b) const |
| Less than operator. More... | |
| CUTLASS_HOST_DEVICE bool | operator<= (Coord const &b) const |
| Less than or equals operator. More... | |
| CUTLASS_HOST_DEVICE bool | operator> (Coord const &b) const |
| Greater than operator. More... | |
| CUTLASS_HOST_DEVICE bool | operator>= (Coord const &b) const |
| Greater than or equals operator. More... | |
Additional Inherited Members | |
| Static Public Attributes inherited from cutlass::Coord< 2, int > | |
| static int const | kRank |
| Number of elements in Coord. More... | |
MatrixCoord wraps Coord<2, int> to provide a helper for accessing named dimensions. Classes expecting a coordinate in the rank=2 index space of a matrix should use MatrixCoord.
| using cutlass::MatrixCoord::Base = Coord<2, Index> |
| using cutlass::MatrixCoord::Index = int |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |
|
inline |