約 2,860,671 件
https://w.atwiki.jp/anime_wiki/pages/10286.html
Blu-ray 逮捕しちゃうぞ the MOVIE Blu-ray発売日：７月２３日 藤島康介原作 最強美人スーパーポリスコンビ夏実 美幸の痛快ポリスアクションの劇場版! 劇場を包み込んだあの迫力と興奮が、DTS(5.1ch)のBlu-rayになって遂に登場! シリーズ史上最大級の危機!走れTODAY、東京を駆け抜けろ!! 毎回映像特典 キャスト スタッフによるオーディオコメンタリー ここを編集 1999年4月公開。逮捕しちゃうぞの劇場版。2010年7月23日、Blu-ray版発売。 監督 西村純二 原作 藤島康介 脚本 十川誠志 キャラクターデザイン 中嶋敦子 メカニックデザイン 村田峻治 美術設定 加藤浩、平澤晃弘、塩澤良憲、村山衣絵、服部由美子 美術監督 吉原俊一郎 色彩設計 もちだたけし 撮影監督 吉田光伸 特殊効果 斎藤丈史、上原将一 3Dモデリング・3D撮影 近藤慎与 3Dテクスチャー・背景効果 椎野隆介 編集 森田清次 音響監督 鶴岡陽太 録音 はたしょうじ サウンドデザイン 山田稔 フォーリー 森川永子、古川諭志 音楽 川井憲次 SPECIAL THANKS 平田智浩、則座誠 アニメーション制作 スタジオディーン 演出 守岡博 作画監督 中嶋敦子 メカ作画監督 水村良男 作画監督補佐 小島正士 斎藤哲人 佐藤和巳 石川洋一 レイアウト作監 渡辺純央 レイアウト協力 小島正士 鈴木俊二 渡部隆 ■関連タイトル Blu-ray 逮捕しちゃうぞ the MOVIE 逮捕しちゃうぞ the MOVIE ― オリジナル・サウンドトラック ムック 逮捕しちゃうぞthe MOVIE フィルムコミック 逮捕しちゃうぞthe MOVIE 1 映画パンフレット 逮捕しちゃうぞ the MOVIE DVD 逮捕しちゃうぞ the MOVIE【劇場版】 藤島康介画集『ああっ女神さまっ』1988‐2008 フィギュア・ホビー：逮捕しちゃうぞ 原作コミック 藤島康介／逮捕しちゃうぞ １ rakuten_design= slide ;rakuten_affiliateId= 053df7e0.7c451bd1.0c852203.190c5695 ;rakuten_items= ctsmatch ;rakuten_genreId=0;rakuten_size= 468x160 ;rakuten_target= _blank ;rakuten_theme= gray ;rakuten_border= on ;rakuten_auto_mode= on ;rakuten_genre_title= off ;rakuten_recommend= on ; 随時更新！ pixivFANBOX アニメ@wiki ご支援お待ちしています！ ムック本＆画集新刊／個人画集新刊／新作Blu-ray単巻／新作Blu-ray DVD-BOX アニメ原画集全リスト スタッフインタビューwebリンク集 最新登録アイテム Switch ゼルダの伝説 Tears of the Kingdom Switch 世界樹の迷宮Ⅰ･Ⅱ･Ⅲ HD REMASTER Switch ピクミン 4 大友克洋 Animation AKIRA Layouts Key Frames 2 小説 機動戦士ガンダム 水星の魔女 1 ONE PIECE FILM REDデラックス・リミテッド・エディション 4K ULTRA HD Blu-ray Blu-ray 劇場版 ソードアート・オンライン -プログレッシブ- 冥き夕闇のスケルツォ 完全生産限定版 Blu-ray 映画『ゆるキャン△』 Blu-ray 【コレクターズ版】 Blu-ray ウマ娘 プリティーダービー 4th EVENT SPECIAL DREAMERS!! Blu-ray 天地無用！GXP パラダイス始動編 Blu-ray第1巻 特装版 天地無用！魎皇鬼 第伍期 Blu-ray SET 「GS美神」全話いっき見ブルーレイ Blu-ray ソードアート・オンライン -フルダイブ- メーカー特典：「イベントビジュアル使用A3クリアポスター」付 ラブライブ！虹ヶ咲学園スクールアイドル同好会 5th Live! 虹が咲く場所 Blu-ray Memorial BOX 宇宙戦艦ヤマト2202 愛の戦士たち Blu-ray BOX 特装限定版 地球へ… Blu-ray Disc BOX 完全生産限定版 神風怪盗ジャンヌ Complete Blu-ray BOX HUNTER×HUNTER ハンター試験編・ゾルディック家編Blu-ray BOX BLEACH Blu-ray Disc BOX 破面篇セレクション1＋過去篇 完全生産限定版 MAZINGER THE MOVIE 1973-1976 4Kリマスター版 アニメ・ゲームのロゴデザイン シン・仮面ライダー 音楽集 テレビマガジン特別編集 仮面ライダー 完全版 EPISODE No.1~No.98 MOVIE リスアニ！Vol.50.5 ぼっち・ざ・ろっく！号デラックスエディション ヤマノススメ Next Summit アニメガイド おもいでビヨリ アニメ「魔入りました！入間くん」オフィシャルファンブック 『超時空要塞マクロス』パッケージアート集 CLAMP PREMIUM COLLECTION X 1 トーマの心臓 プレミアムエディション パズル ドラゴンズ 10th Anniversary Art Works はんざわかおり こみっくがーるず画集 ~あばばーさりー!~ あすぱら画集 すいみゃ Art Works trim polka-トリムポルカ- つぐもも裏 超！限界突破イラスト＆激！すじ供養漫画集 開田裕治ウルトラマンシリーズ画集 井澤詩織1st写真集 mascotte 鬼頭明里写真集 my pace 内田真礼 1st photobook 「まあやドキ」 進藤あまね1st写真集 翠~Midori~ 声優 宮村優子 対談集 アスカライソジ 三石琴乃 ことのは 亀田祥倫アートワークス 100％ 庵野秀明責任編集 仮面ライダー 資料写真集 1971－1973 金子雄司アニメーション背景美術画集 タローマン・クロニクル ラブライブ!サンシャイン!! Find Our 沼津~Aqoursのいる風景~ 機動戦士ガンダム 逆襲のシャア 友の会［復刻版］ 梅津泰臣 KISS AND CRY 資料集 安彦良和 マイ・バック・ページズ 『機動戦士ガンダム ククルス・ドアンの島』編 氷川竜介 日本アニメの革新 歴史の転換点となった変化の構造分析 Blu-ray THE IDOLM@STER CINDERELLA GIRLS 10th Anniversary Celebration Animation ETERNITY MEMORIES Blu-ray おいら宇宙の探鉱夫 ブルーレイ版 Blu-ray 映画 バクテン!! 完全生産限定版 アイカツ！ 10th STORY ～未来へのSTARWAY～ Blu-ray BOX 初回生産限定版 はたらく細胞 Blu-ray Disc BOX 完全生産限定版 Blu-ray 長靴をはいた猫 3作品収録 Blu-ray わんぱく王子の大蛇退治 Blu-ray 魔道祖師 完結編 完全生産限定版 魔道祖師Q Blu-ray Disc BOX 完全生産限定盤 にじよん あにめーしょん Blu-ray BOX 【特装限定版】 Blu-ray 鋼の錬金術師 完結編 プレミアム・エディション Blu-ray付き やはりゲームでも俺の青春ラブコメはまちがっている。完 限定版【同梱物】オリジナルアニメ Blu-ray「だから、思春期は終わらずに、青春は続いていく。」
https://w.atwiki.jp/natsutan/pages/51.html
概要 名前空間にあるそれぞれのコマンドの構造体。 /* * Flag bits for commands. * * CMD_IS_DELETED -Means that the command is in the process of *being deleted (its deleteProc is currently *executing). Other attempts to delete the *command should be ignored. * CMD_TRACE_ACTIVE -1 means that trace processing is currently *underway for a rename/delete change. See the *two flags below for which is currently being *processed. * CMD_HAS_EXEC_TRACES -1 means that this command has at least one *execution trace (as opposed to simple *delete/rename traces) in its tracePtr list. * TCL_TRACE_RENAME -A rename trace is in progress. Further *recursive renames will not be traced. * TCL_TRACE_DELETE -A delete trace is in progress. Further *recursive deletes will not be traced. * (these last two flags are defined in tcl.h) */ #define CMD_IS_DELETED 0x1 #define CMD_TRACE_ACTIVE 0x2 #define CMD_HAS_EXEC_TRACES 0x4 typedef Tcl_CmdProc *TclCmdProcType; typedef Tcl_ObjCmdProc *TclObjCmdProcType; typedef void (Tcl_CmdDeleteProc) _ANSI_ARGS_(*1); tcl/generic/tclInt.h メンバー Tcl_HashEntry *hPtr; このコマンドを参照しているハッシュテーブルへのポインタ。名前空間のコマンドテーブルか、hidden command のコマンドテーブルのどちらか。NULLは、ハッシュテーブルのエントリーが削除済みであることを示す。 Namespace *nsPtr;コマンドを含む名前空間へのポインタ int refCount; リファレンスカウント int cmdEpoch; リファレンスが無効になるとインクリメントする CompileProc *compileProc;コンパイルコマンドを呼び出す手続き。コンパイル手続きが無い場合NULL。 Tcl_ObjCmdProc *objProc;オブジェクト形式の手続き ClientData objClientData; Arbitrary value passed to object proc. Tcl_CmdProc *proc;文字列ベースの手続き ClientData clientData;/* Arbitrary value passed to string proc. */ Tcl_CmdDeleteProc *deleteProc; コマンドが削除されるときに呼び出す関数。 ClientData deleteData;/* Arbitrary value passed to deleteProc. */ int flags;コマンドのフラグ ImportRef *importRefPtr;このコマンドがimportされたとき、別の名前空間で作られたコマンドのList CommandTrace *tracePtr;トレース用リストの先頭を指すポインタ ソース typedef struct Command { [[Tcl_HashEntry]] *hPtr;/* Pointer to the hash table entry that refers * to this command. The hash table is either a * namespace's command table or an * interpreter's hidden command table. This * pointer is used to get a command's name * from its Tcl_Command handle. NULL means * that the hash table entry has been removed * already (this can happen if deleteProc * causes the command to be deleted or * recreated). */ [[Namespace]] *nsPtr;/* Points to the namespace containing this * command. */ int refCount;/* 1 if in command hashtable plus 1 for each * reference from a CmdName Tcl object * representing a command's name in a ByteCode * instruction sequence. This structure can be * freed when refCount becomes zero. */ int cmdEpoch;/* Incremented to invalidate any references * that point to this command when it is * renamed, deleted, hidden, or exposed. */ CompileProc *compileProc;/* Procedure called to compile command. NULL * if no compile proc exists for command. */ Tcl_ObjCmdProc *objProc;/* Object-based command procedure. */ ClientData objClientData;/* Arbitrary value passed to object proc. */ Tcl_CmdProc *proc;/* String-based command procedure. */ ClientData clientData;/* Arbitrary value passed to string proc. */ Tcl_CmdDeleteProc *deleteProc; /* Procedure invoked when deleting command to, * e.g., free all client data. */ ClientData deleteData;/* Arbitrary value passed to deleteProc. */ int flags;/* Miscellaneous bits of information about * command. See below for definitions. */ [[ImportRef]] *importRefPtr;/* List of each imported Command created in * another namespace when this command is * imported. These imported commands redirect * invocations back to this command. The list * is used to remove all those imported * commands when deleting this "real" * command. */ [[CommandTrace]] *tracePtr;/* First in list of all traces set for this * command. */ } Command; /* * Flag bits for commands. * * CMD_IS_DELETED -Means that the command is in the process of *being deleted (its deleteProc is currently *executing). Other attempts to delete the *command should be ignored. * CMD_TRACE_ACTIVE -1 means that trace processing is currently *underway for a rename/delete change. See the *two flags below for which is currently being *processed. * CMD_HAS_EXEC_TRACES -1 means that this command has at least one *execution trace (as opposed to simple *delete/rename traces) in its tracePtr list. * TCL_TRACE_RENAME -A rename trace is in progress. Further *recursive renames will not be traced. * TCL_TRACE_DELETE -A delete trace is in progress. Further *recursive deletes will not be traced. * (these last two flags are defined in tcl.h) */ #define CMD_IS_DELETED 0x1 #define CMD_TRACE_ACTIVE 0x2 #define CMD_HAS_EXEC_TRACES 0x4
https://w.atwiki.jp/gayaradio/pages/206.html
知ったかぶりをしたパーソナリティやゲストの嘘がバレた瞬間、GAYAラジ警察に逮捕されること。 主に逮捕されるのはきくぞうさんだが、ゲストで逮捕された人もいる。 きくぞうさんの逮捕についてはきくぞう現行犯逮捕を参照のこと。
https://w.atwiki.jp/cod4mod/pages/43.html
The following link contains a list of script commands available to use while scripting, and their valid parameters and descriptions. This list represents the code commands available, not script functions that are written in other script files. 書くことと（彼・それ）らの有効パラメータと解説である間に、次のリンクは使うのにすぐ利用できるスクリプトコマンドのリストを含んでいます。 このリストは、他のスクリプトファイルに書かれるスクリプトファンクションではなく、利用可能なコード化コマンドを表します。 Script Commands (Original "http //www.infinityward.com/wiki/index.php?title=Script_Commands") 名前 すべて読む
https://w.atwiki.jp/nostradamus/pages/1163.html
comment は現代フランス語の名詞としては「方法」などの意味。中期フランス語では commentaire （説明、註解）の意味があった(*1)。 command の誤記と見なすピーター・ラメジャラーのような見解もある。 登場箇所 百詩篇第7巻1番 名前 コメント
https://w.atwiki.jp/ookareeda/pages/93.html
逮捕積み 英名 考案 作成時期 概要 1巡目 テト譜 片側のみのセットアップ率 36.51% 反転込みのセットアップ率 53.89% 2巡目 + TSDパフェ率重視組分け テト譜 パフェ率(%) TSDパフェ率(%) TSS-Tetrisパフェ率(%) その地形のセットアップ率(%) その地形までのセットアップ率(%) 補完 TST1 TST2 TST3 100.00 必須 1巡目を含む理論TSDパフェ率 % 1巡目を含まない理論TSDパフェ率 % + パフェ率重視組分け テト譜 補完 TSDパフェ率(%) パフェ率(%) TSS-Tetrisパフェ率(%) その地形までのセットアップ率(%) その地形を必要とする確率(%) TST-1 99.09 35.00 0.00 40.00 40.00 TST-2 98.57 36.98 16.47 60.83 20.83 TST-3 96.94 39.01 0.00 67.78 6.94 TST-4 必須 86.59 10.16 0.00 81.39 13.61 TST-5 必須 84.76 15.28 0.00 91.67 10.28 TST-6 必須 81.79 0.00 0.00 100.00 8.33 1巡目を含む理論パフェ率 50.772% 1巡目を含まない理論パフェ率 94.215% 類似テンプレ Riif積み v2 ガムシロ積み 他のwikiで見る テトリステンプレ整理Wiki テトリスTDアタック8段まとめwiki 銀山のテトリス開幕テンプレwiki
https://w.atwiki.jp/rokurokubi/pages/130.html
逮捕 逮捕には通常逮捕・現行犯逮捕等がありますが、医療行為の業務上過失致死事件では通常逮捕が問題となるため、この点について記述します。 通常逮捕とは、裁判官の発する逮捕状によって身柄を拘束し、引き続いて拘束の状態を続けることをいいます。 この、通常逮捕は①被疑者が罪を犯したと疑うに足りる相当な理由があること(逮捕の理由、刑事訴訟法199条1項・2項)、②逃亡または罪証隠滅のおそれがない等明らかに逮捕の必要がない場合でないこと(刑事訴訟法199条2項・刑事訴訟規則143条の3)、が必要です。 もっとも、裁判所の逮捕状発行の際の審査はかなり緩い、と指摘されており、警察や検察による逮捕状の請求があった場合、これを却下することはめったにありません(平成19年度では逮捕状請求の却下率は１％を切っています→勾留・保釈関係の手続及び終局前後別人員 全裁判所及び最高，全高等・地方・簡易裁判所)こうした運用に対しては、従来から一部から強い批判がされています。 勾留 勾留とは、被疑者もしくは被告人を刑事施設に拘禁する旨の裁判官もしくは裁判所の裁判（刑事訴訟法62条、79条などにいう「勾留」）、または、当該決定に基づき被疑者もしくは被告人を拘禁すること（同法80条、88条などにいう「勾留」）をいいます。 勾留が認められるためには、①被疑者が罪を犯したことを疑うに足りる相当の理由があること、②被疑者が住所不定のとき、または被疑者に罪証隠滅のおそれがあるとき、または被疑者に逃亡のおそれがあるとき、のいずれかの事由があること、③事案の軽重、被疑者の年齢･状況を考慮して、相当性が認められること(勾留の必要性)、が必要とされる。 しかし、勾留状の審査についても、これを却下されることはめったにありません(平成19年度では勾留状請求の却下率は１％を切っています→勾留・保釈関係の手続及び終局前後別人員 全裁判所及び最高，全高等・地方・簡易裁判所)。 被疑者が否認している場合、拘束が長期化することが多い、という点については｢人質司法｣と言う呼称で批判がされています。 勾留と拘留 よく、｢拘留｣というものと勾留が混同されますが、拘留は刑罰の一種で、勾留とは異なる点にご注意ください。 福島大野病院事件での逮捕･勾留について
https://w.atwiki.jp/objcmemo/pages/16.html
/** * xxxxxxxxxxxxxxxx * @param xxxxxxxx xxxxxxxx * @return xxxxxxxx */ /** * xxxxxxxxxx */ /* * xxxxxxxxxx */ #pragma mark - UITableViewDelegate #pragma mark - UITextFieldDelegate #pragma mark - IBAction #pragma mark - Class Method #pragma mark - Instance Method #pragma mark - Private Method #pragma mark - Public Method #pragma mark - UITapGestureRecognizerSelector /// xxxxxxxxxx @property (strong, nonatomic) NSMutableArray *tableItems; /// xxxxxxxxxx @property (assign, nonatomic) BOOL enabled;
https://w.atwiki.jp/qtmemo/pages/20.html
QDomComment コメントノードを表します 継承元 QDomNode QDomCharacterData 公式リファレンス http //qt-project.org/doc/qt-5/qdomcomment.html 基本 コンストラクタ QDomComment QDomComment() 空の QDomComment オブジェクトを生成します コピーコンストラクタ QDomComment QDomComment(const QDomComment x) オブジェクトはシャローコピーされます ディープコピーをする場合は cloneNode() を使用します 型を取得する QDomNode NodeType QDomComment nodeType() const ノードタイプ(CommentNode)を取得します 演算子 QDomComment QDomComment operator=(const QDomComment x)
https://w.atwiki.jp/coinwiki/pages/53.html
This is a multi-threaded multi-pool FPGA and ASIC miner for bitcoin. This code is provided entirely free of charge by the programmer in his spare time so donations would be greatly appreciated. Please consider donating to the address below. Con Kolivas kernel@kolivas.org 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ DOWNLOADS http //ck.kolivas.org/apps/cgminer GIT TREE https //github.com/ckolivas/cgminer Support thread http //bitcointalk.org/index.php?topic=28402.0 IRC Channel irc //irc.freenode.net/cgminer License GPLv3. See COPYING for details. SEE ALSO API-README, ASIC-README and FGPA-README FOR MORE INFORMATION ON EACH. EXECUTIVE SUMMARY ON USAGE Single pool cgminer -o http //pool port -u username -p password Multiple pools cgminer -o http //pool1 port -u pool1username -p pool1password -o http //pool2 port -u pool2usernmae -p pool2password Single pool with a standard http proxy cgminer -o "http proxy port|http //pool port" -u username -p password Single pool with a socks5 proxy cgminer -o "socks5 proxy port|http //pool port" -u username -p password Single pool with stratum protocol support cgminer -o stratum+tcp //pool port -u username -p password The list of proxy types are http standard http 1.1 proxy http0 http 1.0 proxy socks4 socks4 proxy socks5 socks5 proxy socks4a socks4a proxy socks5h socks5 proxy using a hostname If you compile cgminer with a version of CURL before 7.19.4 then some of the above will not be available. All are available since CURL version 7.19.4 If you specify the --socks-proxy option to cgminer, it will only be applied to all pools that don't specify their own proxy setting like above After saving configuration from the menu, you do not need to give cgminer any arguments and it will load your configuration. Any configuration file may also contain a single "include" "filename" to recursively include another configuration file. Writing the configuration will save all settings from all files in the output. BUILDING CGMINER FOR YOURSELF DEPENDENCIES Mandatory pkg-confighttp //www.freedesktop.org/wiki/Software/pkg-config libtoolhttp //www.gnu.org/software/libtool/ Optional curl dev library http //curl.haxx.se/libcurl/ (libcurl4-openssl-dev - Must tell configure --disable-libcurl otherwise it will attempt to compile it in) curses dev library (libncurses5-dev or libpdcurses on WIN32 for text user interface) libudev dev library (libudev-dev) (This is only required for USB device support and is linux only) If building from git autoconf automake If building on Red Hat sudo yum install autoconf automake autoreconf libtool openssl-compat-bitcoin-devel.x86_64 \ curl libcurl libcurl-devel openssh CGMiner specific configuration options --enable-avalon Compile support for Avalon (default disabled) --enable-bflsc Compile support for BFL ASICs (default disabled) --enable-bitforce Compile support for BitForce FPGAs (default disabled) --enable-bitfury Compile support for BitFury ASICs (default disabled) --enable-hashfast Compile support for Hashfast (default disabled) --enable-icarus Compile support for Icarus (default disabled) --enable-knc Compile support for KnC miners (default disabled) --enable-bab Compile support for BlackArrow Bitfury (default disabled) --enable-klondike Compile support for Klondike (default disabled) --enable-modminer Compile support for ModMiner FPGAs(default disabled) --without-curses Compile support for curses TUI (default enabled) --with-system-libusb Compile against dynamic system libusb (default use included static libusb) Basic *nix build instructions To actually build ./autogen.sh# only needed if building from git repo CFLAGS="-O2 -Wall -march=native" ./configure options make No installation is necessary. You may run cgminer from the build directory directly, but you may do make install if you wish to install cgminer to a system location or location you specified. Native WIN32 build instructions see windows-build.txt Usage instructions Run "cgminer --help" to see options Usage cgminer [-DdElmpPQqUsTouOchnV] Options for both config file and command line api-allow Allow API access (if enabled) only to the given list of [W ]IP[/Prefix] address[/subnets] This overrides --api-network and you must specify 127.0.0.1 if it is required W in front of the IP address gives that address privileged access to all api commands api-description Description placed in the API status header (default cgminer version) api-groups API one letter groups G cmd cmd[,P cmd *...] See API-README for usage api-listen Listen for API requests (default disabled) By default any command that does not just display data returns access denied See --api-allow to overcome this api-network Allow API (if enabled) to listen on/for any address (default only 127.0.0.1) api-mcast Enable API Multicast listener, (default disabled) The listener will only run if the API is also enabled api-mcast-addr arg API Multicast listen address, (default 224.0.0.75) api-mcast-code arg Code expected in the API Multicast message, don't use '-' (default "FTW") api-mcast-port arg API Multicast listen port, (default 4028) api-port Port number of miner API (default 4028) balance Change multipool strategy from failover to even share balance benchmark Run cgminer in benchmark mode - produces no shares compact Use compact display without per device statistics debug|-D Enable debug output device|-d arg Select device to use, one value, range and/or comma separated (e.g. 0-2,4) default all disable-rejecting Automatically disable pools that continually reject shares expiry|-E arg Upper bound on how many seconds after getting work we consider a share from it stale (default 120) failover-only Don't leak work to backup pools when primary pool is lagging fix-protocol Do not redirect to a different getwork protocol (eg. stratum) hotplug arg Set hotplug check time to arg seconds (0=never default 5) - only with libusb kernel-path|-K arg Specify a path to where bitstream files are (default "/usr/local/bin") load-balance Change multipool strategy from failover to quota based balance log|-l arg Interval in seconds between log output (default 5) lowmem Minimise caching of shares for low memory applications monitor|-m arg Use custom pipe cmd for output messages net-delay Impose small delays in networking to not overload slow routers no-submit-stale Don't submit shares if they are detected as stale pass|-p arg Password for bitcoin JSON-RPC server per-device-stats Force verbose mode and output per-device statistics protocol-dump|-P Verbose dump of protocol-level activities queue|-Q arg Minimum number of work items to have queued (0 - 10) (default 1) quiet|-q Disable logging output, display status and errors real-quiet Disable all output remove-disabled Remove disabled devices entirely, as if they didn't exist rotate arg Change multipool strategy from failover to regularly rotate at N minutes (default 0) round-robin Change multipool strategy from failover to round robin on failure scan-time|-s arg Upper bound on time spent scanning current work, in seconds (default 60) sched-start arg Set a time of day in HH MM to start mining (a once off without a stop time) sched-stop arg Set a time of day in HH MM to stop mining (will quit without a start time) sharelog arg Append share log to file shares arg Quit after mining N shares (default unlimited) socks-proxy arg Set socks4 proxy (host port) for all pools without a proxy specified syslog Use system log for output messages (default standard error) temp-cutoff arg Temperature where a device will be automatically disabled, one value or comma separated list (default 95) text-only|-T Disable ncurses formatted screen output url|-o arg URL for bitcoin JSON-RPC server user|-u arg Username for bitcoin JSON-RPC server verbose Log verbose output to stderr as well as status output userpass|-O arg Username Password pair for bitcoin JSON-RPC server Options for command line only config|-c arg Load a JSON-format configuration file See example.conf for an example configuration. help|-h Print this message version|-V Display version and exit USB device (ASIC and FPGA) options icarus-options arg Set specific FPGA board configurations - one set of values for all or comma separated icarus-timing arg Set how the Icarus timing is calculated - one setting/value for all or comma separated usb arg USB device selection (See below) usb-dump (See FPGA-README) See FGPA-README or ASIC-README for more information regarding these. ASIC only options avalon-auto Adjust avalon overclock frequency dynamically for best hashrate avalon-fan arg Set fanspeed percentage for avalon, single value or range (default 20-100) avalon-freq arg Set frequency range for avalon-auto, single value or range avalon-cutoff arg Set avalon overheat cut off temperature (default 60) avalon-options arg Set avalon options baud miners asic timeout freq avalon-temp arg Set avalon target temperature (default 50) bflsc-overheat arg Set overheat temperature where BFLSC devices throttle, 0 to disable (default 90) bitburner-fury-options arg Override avalon-options for BitBurner Fury boards baud miners asic timeout freq bitburner-fury-voltage arg Set BitBurner Fury core voltage, in millivolts bitburner-voltage arg Set BitBurner (Avalon) core voltage, in millivolts klondike-options arg Set klondike options clock temptarget See ASIC-README for more information regarding these. FPGA only options bfl-range Use nonce range on bitforce devices if supported See FGPA-README for more information regarding this. Cgminer should automatically find all of your Avalon ASIC, BFL ASIC, BitForce FPGAs, Icarus bitstream FPGAs, Klondike ASIC, ASICMINER usb block erupters, KnC ASICs, BaB ASICs, Hashfast ASICs, ModMiner FPGAs, BPMC/BGMC BF1 USB ASICs and Bi*fury USB ASICs. SETTING UP USB DEVICES WINDOWS On windows, the direct USB support requires the installation of a WinUSB driver (NOT the ftdi_sio driver), and attach it to the chosen USB device. When configuring your device, plug it in and wait for windows to attempt to install a driver on its own. It may think it has succeeded or failed but wait for it to finish regardless. This is NOT the driver you want installed. At this point you need to associate your device with the WinUSB driver. The easiest way to do this is to use the zadig utility which you must right click on and run as administrator. Then once you plug in your device you can choose the "list all devices" from the "option" menu and you should be able to see the device as something like "BitFORCE SHA256 SC". Choose the install or replace driver option and select WinUSB. You can either google for zadig or download it from the cgminer directory in the DOWNLOADS link above. When you first switch a device over to WinUSB with zadig and it shows that correctly on the left of the zadig window, but it still gives permission errors, you may need to unplug the USB miner and then plug it back in. Some users may need to reboot at this point. LINUX On linux, the direct USB support requires no drivers at all. However due to permissions issues, you may not be able to mine directly on the devices as a regular user without giving the user access to the device or by mining as root (administrator). In order to give your regular user access, you can make him a member of the plugdev group with the following commands sudo usermod -G plugdev -a `whoami` If your distribution does not have the plugdev group you can create it with sudo groupadd plugdev In order for the BFL devices to instantly be owned by the plugdev group and accessible by anyone from the plugdev group you can copy the file "01-cgminer.rules" from the cgminer archive into the /etc/udev/rules.d directory with the following command sudo cp 01-cgminer.rules /etc/udev/rules.d/ After this you can either manually restart udev and re-login, or more easily just reboot. OSX On OSX, like Linux, no drivers need to be installed. However some devices like the bitfury USB sticks automatically load a driver thinking they're a modem and the driver needs to be unloaded for cgminer to work sudo kextunload -b com.apple.driver.AppleUSBCDC sudo kextunload -b com.apple.driver.AppleUSBCDCACMData Advanced USB options The --usb option can restrict how many Avalon, BFL ASIC, BitForce FPGAs, Klondike ASIC, ModMiner FPGAs or Icarus bitstream FPGAs it finds --usb 1 2,1 3,1 4,1 * or --usb BAS 1,BFL 1,MMQ 0,ICA 0,KLN 0 or --usb 10 You can only use one of the above 3 The first version --usb 1 2,1 3,1 4,1 * allows you to select which devices to mine on with a list of USB bus_number device_address All other USB devices will be ignored Hotplug will also only look at the devices matching the list specified and find nothing new if they are all in use You can specify just the USB bus_number to find all devices like 1 * which means any devices on USB bus_number 1 This is useful if you unplug a device then plug it back in the same port, it usually reappears with the same bus_number but a different device_address You can see the list of all USB devices on linux with 'sudo lsusb' Cgminer will list the recognised USB devices with the '-n' option or the '--usb-dump 0' option The '--usb-dump N' option with a value of N greater than 0 will dump a lot of details about each recognised USB device If you wish to see all USB devices, include the --usb-list-all option The second version --usb BAS 1,BFL 1,MMQ 0,ICA 0,KLN 0 allows you to specify how many devices to choose based on each device driver cgminer has - there are currently 5 USB drivers BAS, BFL, MMQ. ICA KLN N.B. you can only specify which device driver to limit, not the type of each device, e.g. with BAS n you can limit how many BFL ASIC devices will be checked, but you cannot limit the number of each type of BFL ASIC Also note that the MMQ count is the number of MMQ backplanes you have not the number of MMQ FPGAs The third version --usb 10 means only use a maximum of 10 devices of any supported USB devices Once cgminer has 10 devices it will not configure any more and hotplug will not scan for any more If one of the 10 devices stops working, hotplug - if enabled, as is default will scan normally again until it has 10 devices --usb 0 will disable all USB I/O other than to initialise libusb NOTE The --device option will limit which devices are in use based on their numbering order of the total devices, so if you hotplug USB devices regularly, it will not reliably be the same devices. WHILE RUNNING The following options are available while running with a single keypress [P]ool management [S]ettings [D]isplay options [Q]uit P gives you Current pool management strategy Failover [F]ailover only disabled [A]dd pool [R]emove pool [D]isable pool [E]nable pool [C]hange management strategy [S]witch pool [I]nformation S gives you [Q]ueue 1 [S]cantime 60 [E]xpiry 120 [W]rite config file [C]gminer restart D gives you [N]ormal [C]lear [S]ilent mode (disable all output) [D]ebug off [P]er-device off [Q]uiet off [V]erbose off [R]PC debug off [W]orkTime details off co[M]pact off [L]og interval 5 Q quits the application. The running log shows output like this [2013-11-09 11 04 41] Accepted 01b3bde7 Diff 150/128 AVA 1 pool 0 [2013-11-09 11 04 49] Accepted 015df995 Diff 187/128 AVA 1 pool 0 [2013-11-09 11 04 50] Accepted 01163b68 Diff 236/128 AVA 1 pool 0 [2013-11-09 11 04 53] Accepted 9f745840 Diff 411/128 BAS 1 pool 0 The 8 byte hex value are the 1st nonzero bytes of the share being submitted to the pool. The 2 diff values are the actual difficulty target that share reached followed by the difficulty target the pool is currently asking for. Also many issues and FAQs are covered in the forum thread dedicated to this program, http //forum.bitcoin.org/index.php?topic=28402.0 The output line shows the following (5s) 1713.6 (avg) 1707.8 Mh/s | A 729 R 8 HW 0 WU 22.53/m Each column is as follows 5s A 5 second exponentially decaying average hash rate avg An all time average hash rate A The total difficulty of Accepted shares R The total difficulty of Rejected shares HW The number of HardWare errors WU The Work Utility defined as the number of diff1 shares work / minute (accepted or rejected). BAS 1 max 67C 3.27V | 62.29G/62.19Gh/s | A 140813 R 256 HW 2860 WU 852.0/m Each column is as follows Temperature (if supported) Fanspeed (if supported) A 5 second exponentially decaying average hash rate An all time average hash rate The total difficulty of accepted shares The total difficulty of rejected shares The number of hardware erorrs The work utility defined as the number of diff1 shares work / minute The cgminer status line shows ST 1 SS 0 NB 1 LW 8 GF 1 RF 1 ST is STaged work items (ready to use). SS is Stale Shares discarded (detected and not submitted so don't count as rejects) NB is New Blocks detected on the network LW is Locally generated Work items GF is Getwork Fail Occasions (server slow to provide work) RF is Remote Fail occasions (server slow to accept work) The block display shows Block 0074c5e482e34a506d2a051a... Started [17 17 22] Best share 2.71K This shows a short stretch of the current block, when the new block started, and the all time best difficulty share you've found since starting cgminer this time. MULTIPOOL FAILOVER STRATEGIES WITH MULTIPOOL A number of different strategies for dealing with multipool setups are available. Each has their advantages and disadvantages so multiple strategies are available by user choice, as per the following list FAILOVER The default strategy is failover. This means that if you input a number of pools, it will try to use them as a priority list, moving away from the 1st to the 2nd, 2nd to 3rd and so on. If any of the earlier pools recover, it will move back to the higher priority ones. ROUND ROBIN This strategy only moves from one pool to the next when the current one falls idle and makes no attempt to move otherwise. ROTATE This strategy moves at user-defined intervals from one active pool to the next, skipping pools that are idle. LOAD BALANCE This strategy sends work to all the pools on a quota basis. By default, all pools are allocated equal quotas unless specified with --quota. This apportioning of work is based on work handed out, not shares returned so is independent of difficulty targets or rejected shares. While a pool is disabled or dead, its quota is dropped until it is re-enabled. Quotas are forward looking, so if the quota is changed on the fly, it only affects future work. If all pools are set to zero quota or all pools with quota are dead, it will fall back to a failover mode. See quota below for more information. The failover-only flag has special meaning in combination with load-balance mode and it will distribute quota back to priority pool 0 from any pools that are unable to provide work for any reason so as to maintain quota ratios between the rest of the pools. BALANCE This strategy monitors the amount of difficulty 1 shares solved for each pool and uses it to try to end up doing the same amount of work for all pools. QUOTAS The load-balance multipool strategy works off a quota based scheduler. The quotas handed out by default are equal, but the user is allowed to specify any arbitrary ratio of quotas. For example, if all the quota values add up to 100, each quota value will be a percentage, but if 2 pools are specified and pool0 is given a quota of 1 and pool1 is given a quota of 9, pool0 will get 10% of the work and pool1 will get 90%. Quotas can be changed on the fly by the API, and do not act retrospectively. Setting a quota to zero will effectively disable that pool unless all other pools are disabled or dead. In that scenario, load-balance falls back to regular failover priority-based strategy. While a pool is dead, it loses its quota and no attempt is made to catch up when it comes back to life. To specify quotas on the command line, pools should be specified with a semicolon separated --quota(or -U) entry instead of --url. Pools specified with url are given a nominal quota value of 1 and entries can be mixed. For example url poola porta -u usernamea -p passa --quota "2;poolb portb" -u usernameb -p passb Will give poola 1/3 of the work and poolb 2/3 of the work. Writing configuration files with quotas is likewise supported. To use the above quotas in a configuration file they would be specified thus "pools" [ { "url" "poola porta", "user" "usernamea", "pass" "passa" }, { "quota" "2;poolb portb", "user" "usernameb", "pass" "passb" } ] LOGGING cgminer will log to stderr if it detects stderr is being redirected to a file. To enable logging simply add 2 logfile.txt to your command line and logfile.txt will contain the logged output at the log level you specify (normal, verbose, debug etc.) In other words if you would normally use ./cgminer -o xxx -u yyy -p zzz if you use ./cgminer -o xxx -u yyy -p zzz 2 logfile.txt it will log to a file called logfile.txt and otherwise work the same. There is also the -m option on linux which will spawn a command of your choice and pipe the output directly to that command. The WorkTime details 'debug' option adds details on the end of each line displayed for Accepted or Rejected work done. An example would be -00000059.ed4834a3 M X D 1.0 G 17 02 38 0.405 C 1.855 (2.995) W 3.440 (0.000) S 0.461 R 17 02 47 The first 2 hex codes are the previous block hash, the rest are reported in seconds unless stated otherwise The previous hash is followed by the getwork mode used M X where X is one of P Pool, T Test Pool, L LP or B Benchmark, then D d.ddd is the difficulty required to get a share from the work, then G hh mm ss n.nnn, which is when the getwork or LP was sent to the pool and the n.nnn is how long it took to reply, followed by 'O' on it's own if it is an original getwork, or 'C n.nnn' if it was a clone with n.nnn stating how long after the work was recieved that it was cloned, (m.mmm) is how long from when the original work was received until work started, W n.nnn is how long the work took to process until it was ready to submit, (m.mmm) is how long from ready to submit to actually doing the submit, this is usually 0.000 unless there was a problem with submitting the work, S n.nnn is how long it took to submit the completed work and await the reply, R hh mm ss is the actual time the work submit reply was received If you start cgminer with the --sharelog option, you can get detailed information for each share found. The argument to the option may be "-" for standard output (not advisable with the ncurses UI), any valid positive number for that file descriptor, or a filename. To log share data to a file named "share.log", you can use either ./cgminer --sharelog 50 -o xxx -u yyy -p zzz 50 share.log ./cgminer --sharelog share.log -o xxx -u yyy -p zzz For every share found, data will be logged in a CSV (Comma Separated Value) format timestamp,disposition,target,pool,dev,thr,sharehash,sharedata For example (this is wrapped, but it's all on one line for real) 1335313090,reject, ffffffffffffffffffffffffffffffffffffffffffffffffffffffff00000000, http //localhost 8337,GPU0,0, 6f983c918f3299b58febf95ec4d0c7094ed634bc13754553ec34fc3800000000, 00000001a0980aff4ce4a96d53f4b89a2d5f0e765c978640fe24372a000001c5 000000004a4366808f81d44f26df3d69d7dc4b3473385930462d9ab707b50498 f681634a4f1f63d01a0cd43fb338000000000080000000000000000000000000 0000000000000000000000000000000000000000000000000000000080020000 RPC API For RPC API details see the API-README file FAQ Q Can I mine on servers from different networks (eg xxxcoin and bitcoin) at the same time? A No, cgminer keeps a database of the block it's working on to ensure it does not work on stale blocks, and having different blocks from two networks would make it invalidate the work from each other. Q Can I configure cgminer to mine with different login credentials or pools for each separate device? A No. Q Can I put multiple pools in the config file? A Yes, check the example.conf file. Alternatively, set up everything either on the command line or via the menu after startup and choose settings- write config file and the file will be loaded one each startup. Q The build fails with gcc is unable to build a binary. A Remove the "-march=native" component of your CFLAGS as your version of gcc does not support it. Q Can you implement feature X? A I can, but time is limited, and people who donate are more likely to get their feature requests implemented. Q Work keeps going to my backup pool even though my primary pool hasn't failed? A Cgminer checks for conditions where the primary pool is lagging and will pass some work to the backup servers under those conditions. The reason for doing this is to try its absolute best to keep the devices working on something useful and not risk idle periods. You can disable this behaviour with the option --failover-only. Q Is this a virus? A Cgminer is being packaged with other trojan scripts and some antivirus software is falsely accusing cgminer.exe as being the actual virus, rather than whatever it is being packaged with. If you installed cgminer yourself, then you do not have a virus on your computer. Complain to your antivirus software company. They seem to be flagging even source code now from cgminer as viruses, even though text source files can't do anything by themself. Q Can you modify the display to include more of one thing in the output and less of another, or can you change the quiet mode or can you add yet another output mode? A Everyone will always have their own view of what's important to monitor. The defaults are very sane and I have very little interest in changing this any further. Q What are the best parameters to pass for X pool/hardware/device. A Virtually always, the DEFAULT parameters give the best results. Most user defined settings lead to worse performance. Q What happened to CPU and GPU mining? A Their efficiency makes them irrelevant in the bitcoin mining world today and the author has no interest in supporting alternative coins that are better mined by these devices. Q GUI version? A No. The RPC interface makes it possible for someone else to write one though. Q I'm having an issue. What debugging information should I provide? A Start cgminer with your regular commands and add -D -T --verbose and provide the full startup output and a summary of your hardware and operating system. Q Why don't you provide win64 builds? A Win32 builds work everywhere and there is precisely zero advantage to a 64 bit build on windows. Q Is it faster to mine on windows or linux? A It makes no difference in terms of performance. It comes down to choice of operating system for their various features and your comfort level. However linux is the primary development platform and is virtually guaranteed to be more stable. Q My network gets slower and slower and then dies for a minute? A; Try the --net-delay option if you are on a getwork or GBT server. Q How do I tune for p2pool? A It is also recommended to use --failover-only since the work is effectively like a different block chain, and not enabling --no-submit-stale. If mining with a BFL (fpga) minirig, it is worth adding the --bfl-range option. Q I run PHP on windows to access the API with the example miner.php. Why does it fail when php is installed properly but I only get errors about Sockets not working in the logs? A http //us.php.net/manual/en/sockets.installation.php Q What is a PGA? A At the moment, cgminer supports 3 FPGAs BitForce, Icarus and ModMiner. They are Field-Programmable Gate Arrays that have been programmed to do Bitcoin mining. Since the acronym needs to be only 3 characters, the "Field-" part has been skipped. Q What is an ASIC? A They are Application Specify Integrated Circuit devices and provide the highest performance per unit power due to being dedicated to only one purpose. Q Can I mine scrypt with FPGAs or ASICs? A No. Q What is stratum and how do I use it? A Stratum is a protocol designed for pooled mining in such a way as to minimise the amount of network communications, yet scale to hardware of any speed. With versions of cgminer 2.8.0+, if a pool has stratum support, cgminer will automatically detect it and switch to the support as advertised if it can. If you input the stratum port directly into your configuration, or use the special prefix "stratum+tcp //" instead of "http //", cgminer will ONLY try to use stratum protocol mining. The advantages of stratum to the miner are no delays in getting more work for the miner, less rejects across block changes, and far less network communications for the same amount of mining hashrate. If you do NOT wish cgminer to automatically switch to stratum protocol even if it is detected, add the --fix-protocol option. Q Why don't the statistics add up Accepted, Rejected, Stale, Hardware Errors, Diff1 Work, etc. when mining greater than 1 difficulty shares? A As an example, if you look at 'Difficulty Accepted' in the RPC API, the number of difficulty shares accepted does not usually exactly equal the amount of work done to find them. If you are mining at 8 difficulty, then you would expect on average to find one 8 difficulty share, per 8 single difficulty shares found. However, the number is actually random and converges over time, it is an average, not an exact value, thus you may find more or less than the expected average. Q My keyboard input momentarily pauses or repeats keys every so often on windows while mining? A The USB implementation on windows can be very flaky on some hardware and every time cgminer looks for new hardware to hotplug it it can cause these sorts of problems. You can disable hotplug with hotplug 0 Q What should my Work Utility (WU) be? A Work utility is the product of hashrate * luck and only stabilises over a very long period of time. Assuming all your work is valid work, bitcoin mining should produce a work utility of approximately 1 per 71.6MH. This means at 5GH you should have a WU of 5000 / 71.6 or ~ 69. You cannot make your machine do "better WU" than this - it is luck related. However you can make it much worse if your machine produces a lot of hardware errors producing invalid work. This code is provided entirely free of charge by the programmer in his spare time so donations would be greatly appreciated. Please consider donating to the address below. Con Kolivas kernel@kolivas.org 15qSxP1SQcUX3o4nhkfdbgyoWEFMomJ4rZ