this line for any atome type need to change?

TABEAM.Pair.Ag  in csh file.

On Fri, Jan 13, 2017 at 9:09 PM, Hamid Mosaddeghi <h.mosaddeghi@gmail.com>
wrote:

> for two atoms alloy for example Ag and pb , this code work correct?
>
> i add data of Pb in end of Ag files. please see attach file.
>
> i get this error:
>
>  ./Make_Alloy_EAMS.csh 3
> cp: cannot stat `morse_mod.dat.1': No such file or directory
> cp: cannot stat `dens_mod.dat.1': No such file or directory
> cp: cannot stat `embed_mod.dat.1': No such file or directory
>
>
> thank you.
>
> On Fri, Jan 13, 2017 at 9:06 PM, Hamid Mosaddeghi <h.mosaddeghi@gmail.com>
> wrote:
>
>> hi
>>
>> On Thu, Jan 12, 2017 at 6:23 PM, Hamid Mosaddeghi <h.mosaddeghi@gmail.com
>> > wrote:
>>
>>> I found new ref that used your data. did you see it?
>>>
>>> PHYSICAL REVIEW B 69, 144113 ~2004!
>>>
>>> On Thu, Jan 12, 2017 at 4:00 PM, keeeto <notifications@github.com>
>>> wrote:
>>>
>>>> Why not build the TABEAM for Ni using the parameters from the Acta
>>>> Mater paper. You can then test the calculations.
>>>>
>>>> On 12 Jan 2017, at 11:59, hamidmosaddeghi <notifications@github.com
>>>> <mailto:notifications@github.com>> wrote:
>>>>
>>>> I want in first step prepare one file for Ni and I have same file for
>>>> NI
>>>> from https://sites.google.com/site/eampotentials/Ni#TOC-Other-formats
>>>>
>>>> and then compare output. what't your idea?
>>>>
>>>> On Thu, Jan 12, 2017 at 3:20 PM, keeeto <notifications@github.com<mail
>>>> to:notifications@github.com>> wrote:
>>>>
>>>> > Well,
>>>> >
>>>> > You must have data to fit it to. Either experiment or quantum
>>>> mechanics
>>>> > calculations. You can always try with the value from that paper and
>>>> see if
>>>> > it works.
>>>> >
>>>> >
>>>> > On 12 Jan 2017, at 11:47, hamidmosaddeghi <notifications@github.com
>>>> <mailto:notifications@github.com><
>>>> > mailto:notifications@github.com>> wrote:
>>>> >
>>>> > exactly I have some other molecules and ion, but I don't how set it.
>>>> >
>>>> > thank you so much for your attention.
>>>> >
>>>> > On Thu, Jan 12, 2017 at 3:14 PM, keeeto <notifications@github.com
>>>> <mailto:notifications@github.com><mailto:
>>>> > notifications@github.com<mailto:notifications@github.com>>> wrote:
>>>> >
>>>> > > For my system - which included other elements and potentials I had
>>>> a
>>>> > > strained interface. You must choose your potential carefully
>>>> depending
>>>> > on
>>>> > > the system that you are investigating.
>>>> > >
>>>> > > On 12 Jan 2017, at 11:41, hamidmosaddeghi <notifications@github.com
>>>> <mailto:notifications@github.com><
>>>> > mailto:notifications@github.com><
>>>> > > mailto:notifications@github.com>> wrote:
>>>> > >
>>>> > > what is your reason for change it? please explain for me.
>>>> > >
>>>> > > On Thu, Jan 12, 2017 at 3:04 PM, keeeto <notifications@github.com
>>>> <mailto:notifications@github.com><
>>>> > mailto:notifications@github.com><mailto:
>>>> > > notifications@github.com<mailto:notifications@github.com><mailto:
>>>> notifications@github.com>>> wrote:
>>>> > >
>>>> > > > These were values that I derived for my own system. I think that
>>>> you
>>>> > > > should use literature values if you are doing these elements.
>>>> > > >
>>>> > > > I think that DLPOLY is in eV - it should be in the user manual.
>>>> > > >
>>>> > > > Cheers
>>>> > > >
>>>> > > > Keith
>>>> > > >
>>>> > > > On 12 Jan 2017, at 11:28, hamidmosaddeghi <
>>>> notifications@github.com<mailto:notifications@github.com><
>>>> > mailto:notifications@github.com><
>>>> > > mailto:notifications@github.com><
>>>> > > > mailto:notifications@github.com>> wrote:
>>>> > > >
>>>> > > > that's great, but i see typo wrong according to literature in
>>>> some
>>>> > > > example,
>>>> > > >
>>>> > > > you set lambda for Ag and Pb 0.764955 but this value in
>>>> > > > literature 0.850703? why?
>>>> > > >
>>>> > > > unit for dl_poly field is ev?
>>>> > > >
>>>> > > > thank you so much for quick reply.
>>>> > > >
>>>> > > > On Thu, Jan 12, 2017 at 2:50 PM, keeeto <notifications@github.com
>>>> <mailto:notifications@github.com><
>>>> > mailto:notifications@github.com><
>>>> > > mailto:notifications@github.com><mailto:
>>>> > > > notifications@github.com<mailto:notifications@github.com><mailto:
>>>> notifications@github.com><mailto:
>>>> > notifications@github.com<mailto:notifications@github.com>>>> wrote:
>>>> > > >
>>>> > > > > Hi,
>>>> > > > >
>>>> > > > > lower_limit, upper_limit: For these parameters, usually the
>>>> defaults
>>>> > > > > provided in the files are sufficient. This could change if your
>>>> > > > potential
>>>> > > > > is particularly slowly decaying for some reason.
>>>> > > > > I would advise to use these numbers, but to run some small
>>>> tests
>>>> > > (single
>>>> > > > > point total energy) to check that the energy is not sensitive
>>>> to the
>>>> > > > chosen
>>>> > > > > cutoffs. Also, for the sake of convenience it is probably
>>>> easier to
>>>> > > set
>>>> > > > > upper and lower cutoffs to be the same for all ELEMENTS in your
>>>> > > > > calculation.
>>>> > > > >
>>>> > > > > Grid density should be good at the default. Again you can try
>>>> to
>>>> > test
>>>> > > > > convergence if you like, as above.
>>>> > > > >
>>>> > > > > Cheers
>>>> > > > >
>>>> > > > > Keith
>>>> > > > >
>>>> > > > > On 12 Jan 2017, at 11:10, hamidmosaddeghi <
>>>> notifications@github.com<mailto:notifications@github.com><
>>>> > mailto:notifications@github.com><
>>>> > > mailto:notifications@github.com><
>>>> > > > mailto:notifications@github.com><
>>>> > > > > mailto:notifications@github.com>> wrote:
>>>> > > > >
>>>> > > > > Hi
>>>> > > > >
>>>> > > > > thank you, i am so sorry, some parameters as:
>>>> > > > >
>>>> > > > > lower limit, upper limit and grid density for example for Fe
>>>> metal
>>>> > > > >
>>>> > > > > how set them?
>>>> > > > >
>>>> > > > > thanks
>>>> > > > >
>>>> > > > > On Thu, Jan 12, 2017 at 10:43 AM, keeeto <
>>>> notifications@github.com<mailto:notifications@github.com><
>>>> > mailto:notifications@github.com><
>>>> > > mailto:notifications@github.com><
>>>> > > > mailto:notifications@github.com><mailto:
>>>> > > > > notifications@github.com<mailto:notifications@github.com><ma
>>>> ilto:notifications@github.com><mailto:
>>>> > notifications@github.com<mailto:notifications@github.com>><mailto:
>>>> > > notifications@github.com<mailto:notifications@github.com><mailto:
>>>> notifications@github.com>>>> wrote:
>>>> > > > >
>>>> > > > > > Hello,
>>>> > > > > >
>>>> > > > > > Thanks for your interest in the code. The parameters can be
>>>> found
>>>> > in
>>>> > > > the
>>>> > > > > > Appendix of the paper.
>>>> > > > > >
>>>> > > > > > Best,
>>>> > > > > >
>>>> > > > > > Keith
>>>> > > > > >
>>>> > > > > > On 11 Jan 2017, at 22:05, hamidmosaddeghi <
>>>> > notifications@github.com<mailto:notifications@github.com><mailto:
>>>> notifications@github.com><
>>>> > > mailto:notifications@github.com><
>>>> > > > mailto:notifications@github.com><
>>>> > > > > mailto:notifications@github.com>>
>>>> > > > > > wrote:
>>>> > > > > >
>>>> > > > > > > Acta Mater. 49 (2001) 4005 - 4015
>>>> > > > > >
>>>> > > > > > —
>>>> > > > > > You are receiving this because you commented.
>>>> > > > > > Reply to this email directly, view it on GitHub
>>>> > > > > > <https://github.com/keeeto/DLPOLY_EAM/commit/
>>>> > > > > 5f63fdc4e557c5945cc6b765b34fbb55fc875ccd#commitcomment-20447717>,
>>>>
>>>> > > > > > or mute the thread
>>>> > > > > > <https://github.com/notifications/unsubscribe-auth/
>>>> > > > > AX1FjxSoKTSMeucVidWdct1tEolCXHvzks5rRdKjgaJpZM4LhIH->
>>>> > > > > > .
>>>> > > > > >
>>>> > > > >
>>>> > > > >
>>>> > > > >
>>>> > > > > --
>>>> > > > > *Best Regards*
>>>> > > > > *Hamid **Mosaddeghi*
>>>> > > > >
>>>> > > > > *PhD of Physical Chemistry
>>>> > > > > *
>>>> > > > > *Department of Chemistry*
>>>> > > > >
>>>> > > > > *Isfahan University of Technology, Iran*
>>>> > > > >
>>>> > > > > —
>>>> > > > > You are receiving this because you commented.
>>>> > > > > Reply to this email directly, view it on GitHub<
>>>> https://github.com/
>>>> > > > > keeeto/DLPOLY_EAM/commit/5f63fdc4e557c5945cc6b765b34fbb
>>>> > > > > 55fc875ccd#commitcomment-20450602>, or mute the thread<
>>>> > > > https://github.com/
>>>> > > > > notifications/unsubscribe-auth/ADhr5OHuLrwfTUElP9LBMjJx8LjpBJ
>>>> > > > > tXks5rRgpBgaJpZM4LhIH->.
>>>> > > > >
>>>> > > > > —
>>>> > > > > You are receiving this because you commented.
>>>> > > > > Reply to this email directly, view it on GitHub
>>>> > > > > <https://github.com/keeeto/DLPOLY_EAM/commit/
>>>> > > > 5f63fdc4e557c5945cc6b765b34fbb55fc875ccd#commitcomment-20450735>,
>>>>
>>>> > > > > or mute the thread
>>>> > > > > <https://github.com/notifications/unsubscribe-auth/AX1Fj8D25_
>>>> > > > ZxL5yaQ0weLwGcaGFjuwrAks5rRgyZgaJpZM4LhIH->
>>>> > > > > .
>>>> > > > >
>>>> > > >
>>>> > > >
>>>> > > >
>>>> > > > --
>>>> > > > *Best Regards*
>>>> > > > *Hamid **Mosaddeghi*
>>>> > > >
>>>> > > > *PhD of Physical Chemistry
>>>> > > > *
>>>> > > > *Department of Chemistry*
>>>> > > >
>>>> > > > *Isfahan University of Technology, Iran*
>>>> > > >
>>>> > > > —
>>>> > > > You are receiving this because you commented.
>>>> > > > Reply to this email directly, view it on GitHub<
>>>> https://github.com/
>>>> > > > keeeto/DLPOLY_EAM/commit/5f63fdc4e557c5945cc6b765b34fbb
>>>> > > > 55fc875ccd#commitcomment-20450797>, or mute the thread<
>>>> > > https://github.com/
>>>> > > > notifications/unsubscribe-auth/ADhr5FJ7WRG45sq6auXCOqRPIbT3cc
>>>> > > > 5Dks5rRg5AgaJpZM4LhIH->.
>>>> > > >
>>>> > > > —
>>>> > > > You are receiving this because you commented.
>>>> > > > Reply to this email directly, view it on GitHub
>>>> > > > <https://github.com/keeeto/DLPOLY_EAM/commit/
>>>> > > 5f63fdc4e557c5945cc6b765b34fbb55fc875ccd#commitcomment-20450871>,
>>>> > > > or mute the thread
>>>> > > > <https://github.com/notifications/unsubscribe-auth/
>>>> > > AX1FjwXllelbgszBRFyHqY8UYTLLgCqrks5rRg--gaJpZM4LhIH->
>>>> > > > .
>>>> > > >
>>>> > >
>>>> > >
>>>> > >
>>>> > > --
>>>> > > *Best Regards*
>>>> > > *Hamid **Mosaddeghi*
>>>> > >
>>>> > > *PhD of Physical Chemistry
>>>> > > *
>>>> > > *Department of Chemistry*
>>>> > >
>>>> > > *Isfahan University of Technology, Iran*
>>>> > >
>>>> > > —
>>>> > > You are receiving this because you commented.
>>>> > > Reply to this email directly, view it on GitHub<https://github.com/
>>>> > > keeeto/DLPOLY_EAM/commit/5f63fdc4e557c5945cc6b765b34fbb
>>>> > > 55fc875ccd#commitcomment-20450947>, or mute the thread<
>>>> > https://github.com/
>>>> > > notifications/unsubscribe-auth/ADhr5LMyVzf9mQXDBJKrpMD-
>>>> > > Jq8s7WkZks5rRhFVgaJpZM4LhIH->.
>>>> > >
>>>> > > —
>>>> > > You are receiving this because you commented.
>>>> > > Reply to this email directly, view it on GitHub
>>>> > > <https://github.com/keeeto/DLPOLY_EAM/commit/
>>>> > 5f63fdc4e557c5945cc6b765b34fbb55fc875ccd#commitcomment-20450987>,
>>>> > > or mute the thread
>>>> > > <https://github.com/notifications/unsubscribe-auth/AX1Fj_
>>>> > 6Av82Z1oPirCzjW6PT1dekJckHks5rRhIMgaJpZM4LhIH->
>>>> > > .
>>>> > >
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > *Best Regards*
>>>> > *Hamid **Mosaddeghi*
>>>> >
>>>> > *PhD of Physical Chemistry
>>>> > *
>>>> > *Department of Chemistry*
>>>> >
>>>> > *Isfahan University of Technology, Iran*
>>>> >
>>>> > —
>>>> > You are receiving this because you commented.
>>>> > Reply to this email directly, view it on GitHub<https://github.com/
>>>> > keeeto/DLPOLY_EAM/commit/5f63fdc4e557c5945cc6b765b34fbb
>>>> > 55fc875ccd#commitcomment-20451019>, or mute the thread<
>>>> https://github.com/
>>>> > notifications/unsubscribe-auth/ADhr5Hxn-RdNgWhQ_
>>>> > nt2f8sLMJRy9885ks5rRhK9gaJpZM4LhIH->.
>>>> >
>>>> > —
>>>> > You are receiving this because you commented.
>>>> > Reply to this email directly, view it on GitHub
>>>> > <https://github.com/keeeto/DLPOLY_EAM/commit/5f63fdc4e557c59
>>>> 45cc6b765b34fbb55fc875ccd#commitcomment-20451059>,
>>>> > or mute the thread
>>>> > <https://github.com/notifications/unsubscribe-auth/AX1Fj93a3
>>>> egkAhF90lcF0hIz_x74rYTxks5rRhNrgaJpZM4LhIH->
>>>> > .
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> *Best Regards*
>>>> *Hamid **Mosaddeghi*
>>>>
>>>> *PhD of Physical Chemistry
>>>> *
>>>> *Department of Chemistry*
>>>>
>>>> *Isfahan University of Technology, Iran*
>>>>
>>>> —
>>>> You are receiving this because you commented.
>>>> Reply to this email directly, view it on GitHub<https://github.com/keee
>>>> to/DLPOLY_EAM/commit/5f63fdc4e557c5945cc6b765b34fbb55fc875cc
>>>> d#commitcomment-20451160>, or mute the thread<https://github.com/noti
>>>> fications/unsubscribe-auth/ADhr5Ktd8bSwpfevtFeEsBiQc-Zlr9Pok
>>>> s5rRhWcgaJpZM4LhIH->.
>>>>
>>>> —
>>>> You are receiving this because you commented.
>>>> Reply to this email directly, view it on GitHub
>>>> <https://github.com/keeeto/DLPOLY_EAM/commit/5f63fdc4e557c5945cc6b765b34fbb55fc875ccd#commitcomment-20451451>,
>>>> or mute the thread
>>>> <https://github.com/notifications/unsubscribe-auth/AX1FjwXzDVdLHXUDKCmZ-FDWi5zUmHo8ks5rRhzkgaJpZM4LhIH->
>>>> .
>>>>
>>>
>>>
>>>
>>> --
>>> *Best Regards*
>>> *Hamid **Mosaddeghi*
>>>
>>> *PhD of Physical Chemistry
>>>                                  *
>>> *Department of Chemistry*
>>>
>>> *Isfahan University of Technology, Iran*
>>>
>>>
>>>
>>>
>>
>>
>> --
>> *Best Regards*
>> *Hamid **Mosaddeghi*
>>
>> *PhD of Physical Chemistry
>>                                  *
>> *Department of Chemistry*
>>
>> *Isfahan University of Technology, Iran*
>>
>>
>>
>>
>
>
> --
> *Best Regards*
> *Hamid **Mosaddeghi*
>
> *PhD of Physical Chemistry
>                                *
> *Department of Chemistry*
>
> *Isfahan University of Technology, Iran*
>
>
>
>

--
*Best Regards*
*Hamid **Mosaddeghi*

*PhD of Physical Chemistry
                               *
*Department of Chemistry*

*Isfahan University of Technology, Iran*


Its already taken care by `public Map<String,String> formData(String accessKey, String secretKey)` which is backward compatible.


More meh, make a setting for it in Galaxy


> If you built 4.3.0 months ago, you probably don't have this change yet.

Oh thanks! I'll rebuild then.


I've made the message even more generic in the code (because the LUKS PCR is being checked too) and added a sentence to the README about ensuring that the right SINIT blob has been used.


My friend hit this bug recently, I did not realize this is signal instead of broadcast, good catch!


@Klumbumbus but that is a general issue with multiple rings (and a half valid argument I suppose :-)).


Hi Jason,

If only it was that straight forward.  The change you suggest will result in all instructors being non-primary, which is not what I suspect you want.

We will need to decide what the default should be, i.e., 0 or 1, do an ordering by that column, and then a select top 1 or something like that to achieve the results you are looking for.

Regards,
Ken


todo: add in numpad 1,2,3 as well, as I think they are different?


First, build the binding, remeber where ```pymei``` was placed. Then, reference that location with ```pip install <path>``` or ```pip install -e <path>```.


Very nice :)


Hello,
Is it possible to build hexa frame? ( like "make px4-v2-hexa)


I think its there for some reason, for aot I think, but there seems to be duplication in polyfill creation I observed as well.

I am confused with my configuration where to to put polyfills entry which works for dev, prod and aot as well.


@robertodr


I prefer hyperzine over morphine, even though having a constant morphine drip is REALLY, REALLY good when you have a hardsuit/riot armor/anything heavy, it kind of makes it impossible to use charcoal without passing out. Plus the extra stun time hurts, gotta remember that.


@maxisam @asadsahi - I'm in the middle or refactoring the webpack configs to simplify this process and allow the additions of vendor libs / pollyfills / plugins without needing to modify the webpack configs directly.

Should have an initial pass in a PR this evening.


I lost 17 Wanderer-equipped Kestrels, on my best try. Ah well, it was worth it.


eggzactly


Create branch: Hello, my name is Janice. I am excited about learning to code. Coding is something that I have been interested in fora longtime; however, I found it intimidating to learn. Hopefully, FCC will be a step in accomplishing my goal.


And mention my goal


missed adding this commit yesterday


LGTM


I guess I'm saying +1 to this change or something, I don't know how this shit works.

Alternatively, it'd be hilarious if there were also a morphine virus, presumably requiring plasma, that works the same as current stims. Gobba go fast.


@d3viant0ne nice to hear that.


See file attached, a lot slower on this machine but still fast; I didn't
think it'd be that efficient. It's not actually zero, so maybe you could
still consider it a possible optimization.

Kind regards,

Kroc.

On 13/1/17 2:08 PM, Tanner wrote:
>
> Inside PhotoDemon's /Data/Debug/ folder, there's a file called
> "pdProfileLog_PhotoDemon_Startup.log". If you want to mail that to me
> (or just paste the file here), I can give you an answer specific to
> your PC!
>
> On my development PC, of the ~1.5 second startup time, parsing menu
> icons only takes ~65 ms. That number will go down as menu icons get
> removed and/or migrated to the new resource engine, but on this
> particular PC, any time savings won't really be noticeable. The
> numbers could be different on other PCs.
>
> Here's what my log looks like right now:
>
> ------------------------------------------------------------------------
>
> Mean time across ALL RECORDED SESSIONS, with events sorted from
> longest to shortest:
>
> |1) Initialize translation engine, 437 ± 80 ms 2) Display splash
> screen, 286 ± 28 ms 3) Window manager: load right toolbox, 258 ± 7 ms
> 4) Window manager: load left toolbox, 147 ± 8 ms 5) Initialize UI, 91
> ± 3 ms 6) Load all menu icons, 63 ± 2 ms 7) Window manager: load
> bottom toolbox, 41 ± 0 ms 8) Initialize theme engine, 41 ± 5 ms 9)
> Final interface sync, 36 ± 21 ms 10) Load plugins, 23 ± 3 ms 11)
> Initialize window manager, 18 ± 2 ms 12) Build font cache, 18 ± 1 ms
> 13) Initialize preferences engine, 18 ± 5 ms 14) Initialize
> pdClipboardMain, 16 ± 10 ms 15) Initialize tools, 14 ± 7 ms 16)
> Initialize viewport engine, 14 ± 0 ms 17) Load import and export
> libraries, 10 ± 1 ms 18) Prepare splash screen, 10 ± 1 ms 19) Prep
> developer menus, 9 ± 1 ms 20) Prep MRU menus, 8 ± 1 ms 21) Detect
> monitors, 3 ± 1 ms 22) Check Windows version, 1 ± 1 ms 23) Prep
> accelerators, 1 ± 1 ms 24) Initialize resource handler, 1 ± 1 ms 25)
> PhotoDemon Startup, 0 ± 0 ms 26) Initialize menu manager, 0 ± 0 ms 27)
> ClearType check, 0 ± 0 ms |
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/tannerhelland/PhotoDemon/commit/c0df94367be8fb7514f5e4beed044ba5db58d5c7#commitcomment-20467884>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAItOn_OolALJ2mUVyVEXrPm6C1zAl7kks5rR4VWgaJpZM4Lizjv>.
>

-- pdProfile report for "PhotoDemon Startup" --
(Report updated at 5:54:40 PM on 13-January-17)

Number of events tracked: 27
Total time taken (this session): 8.37 seconds
Program compiled: True

Timing for THIS SESSION, with events sorted from longest to shortest:

	1) Initialize translation engine, 3288 ms
	2) Final interface sync, 1671 ms
	3) Display splash screen, 769 ms
	4) Window manager: load right toolbox, 697 ms
	5) Window manager: load left toolbox, 444 ms
	6) Load plugins, 353 ms
	7) Initialize UI, 279 ms
	8) Load all menu icons, 195 ms
	9) Initialize theme engine, 182 ms
	10) Window manager: load bottom toolbox, 127 ms
	11) Initialize preferences engine, 86 ms
	12) Prep developer menus, 62 ms
	13) Build font cache, 53 ms
	14) Initialize window manager, 43 ms
	15) Initialize viewport engine, 43 ms
	16) Prep MRU menus, 30 ms
	17) Load import and export libraries, 13 ms
	18) Prepare splash screen, 10 ms
	19) Initialize pdClipboardMain, 9 ms
	20) Initialize tools, 7 ms
	21) Prep accelerators, 4 ms
	22) Check Windows version, 3 ms
	23) Initialize resource handler, 2 ms
	24) Detect monitors, 2 ms
	25) PhotoDemon Startup, 0 ms
	26) Initialize menu manager, 0 ms
	27) ClearType check, 0 ms

Mean time across ALL RECORDED SESSIONS, with events sorted from longest to shortest:

	1) Initialize translation engine, 2263 ± 886 ms
	2) Initialize window manager, 1591 ± 1904 ms
	3) Window manager: load right toolbox, 904 ± 318 ms
	4) Load plugins, 901 ± 729 ms
	5) Final interface sync, 850 ± 1162 ms
	6) Window manager: load left toolbox, 389 ± 46 ms
	7) Display splash screen, 232 ± 242 ms
	8) Initialize UI, 231 ± 137 ms
	9) Load all menu icons, 186 ± 13 ms
	10) Initialize theme engine, 101 ± 42 ms
	11) Window manager: load bottom toolbox, 71 ± 52 ms
	12) Initialize preferences engine, 48 ± 20 ms
	13) Build font cache, 38 ± 19 ms
	14) Initialize viewport engine, 37 ± 21 ms
	15) Prep developer menus, 35 ± 39 ms
	16) Prep MRU menus, 21 ± 13 ms
	17) Load import and export libraries, 17 ± 7 ms
	18) Initialize pdClipboardMain, 16 ± 4 ms
	19) Initialize tools, 15 ± 8 ms
	20) Detect monitors, 7 ± 5 ms
	21) Prepare splash screen, 6 ± 2 ms
	22) Prep accelerators, 4 ± 0 ms
	23) Check Windows version, 4 ± 2 ms
	24) Initialize resource handler, 3 ± 1 ms
	25) PhotoDemon Startup, 0 ± 0 ms
	26) Initialize menu manager, 0 ± 0 ms
	27) ClearType check, 0 ± 0 ms

Coefficient of variation across ALL RECORDED SESSIONS, with events sorted from highest to lowest magnitude:

	1) Initialize window manager, 2.9310
	2) Display splash screen, 2.5558
	3) Load plugins, 1.9819
	4) Detect monitors, 1.6906
	5) Initialize UI, 1.4543
	6) Initialize viewport engine, 1.3911
	7) Final interface sync, 1.3676
	8) Initialize tools, 1.3151
	9) Window manager: load bottom toolbox, 1.2648
	10) Build font cache, 1.2377
	11) Prep developer menus, 1.1273
	12) Check Windows version, 1.1100
	13) Prepare splash screen, 1.0706
	14) Initialize theme engine, 1.0173
	15) Initialize preferences engine, 0.9907
	16) Load import and export libraries, 0.9618
	17) Initialize translation engine, 0.9591
	18) Prep MRU menus, 0.6554
	19) Window manager: load right toolbox, 0.6091
	20) Initialize pdClipboardMain, 0.5639
	21) Initialize resource handler, 0.4714
	22) Window manager: load left toolbox, 0.2037
	23) Load all menu icons, 0.0724
	24) Prep accelerators, 0.0000
	25) PhotoDemon Startup, 0.0000
	26) Initialize menu manager, 0.0000
	27) ClearType check, 0.0000

-- End of timing report --


I actually had an idea for that though I'd use a snowflake chem instead because morphine has some real shit downsides.


I don't understand the question. What do you mean?
FF is returnig an XMLDocument object if 2xx has empty body and I'm trying to make it consistent across browsers.

What parsing error do you mean?


I would prefer this padded so that listing shows the PVs in a more natural order "oc get pv" returns:
pv001
pv002
..
and not
pv1
pv10
pv100


I was playing around with these changes and so far looks good to me.


I think the downsides are necessary to balance it out. Never get slowed down in exchange for confusing health and longer stuns. With the way the current stims virus works, you never get the drowsy effect anyway, so it'd be fine in my eyes. Not to mention the fact that, again, you could combine morphine and hyperzine viruses to go FASTEST.


Extract method of this loop:
```java
+    for(int ¢ = 0; ¢ < ll.size(); ++¢)
 +      if(iz.switchCase(ll.get(¢)) && wizard.same(c, ll.get(¢))) {
 +        ind = ¢;
 +        break;
 +      }


Does this role need to be cluster-admin?


@davad Thanks for pointing out this mistake!! I tested it and you are correct, I was able to copy/paste the timestamp and signature while being able to change the hostname and other parameters to connect to different hosts. With my latest changes, the hostname and port number are also hashed


I had the same idea on getting rid of the top-level scope of the client but arrived to the same conclusion. Never really came up with any other way of implementing that.


Does this role need to be privileged?


1-10 Vertically


I had pretty serious problems with random bouts of drowsiness, plus any purge chem completely fucked you over and not to mention the fact you essentially had less health. Sure a painkiller virus could use downsides but morphine was not the right solution.


Is this 20 minutes?


ok look good


Nice experiment and important result !

Would repeating this experiment at bullet make some sense ?
Say 40M games @9  + 0,1
and compare with 40M games @9 +0.1 against a "normal" master.
...
At first sight, in worst case,  if the lazy version is not playing well the ending,
the score will drop below 600 cp, and the deeper evaluations will be triggered again, probably securing the win anyway. But it is worth investigating this subject deeper.
...
Another experiment (against your special master) could be to stop using lazy if the current game start position is in the high ranges, say >400cp.
Yes, we loose the speed optimisation, but since game is already "won" anyway, we do not really need that optimisation, (It is more important  to make sure we win it, and why not, win it with style).
This could also alleviate some of the gray zone just before the 1500 boundary.


Yes, the reason is that hostdir volumes (which the job uses) are only allowed by default on the privileged SCC. The other issue is SELinux permissions by default don't allow the directory creation if not running the container as privileged. (Of course only when running on Fedora/RHEL/Centos)


test


Retry so that if first install did not finish, this time could continue. If you do that, the Job could just try to continue where it left off, and not from scratch, to minimize time.


It needs to be a role that allows creating PV's. We don't have a role by default that only allows that, so we can create one with just that one action or simply use cluster-admin. Because this SA is getting created in the default namespace, which by default only the cluster admin has access to, I didn't think this would be an issue.


[01:00:33 AM]  Loaded Build: v0.1-12-Jan-17
[01:01:18 AM]  Initializing AI...
[01:01:19 AM]  Changing objective to: Hero Management
[01:01:30 AM]  Scene: Lobby
[01:01:34 AM]  Scene: Heroes
[01:01:34 AM]  Start managing heroes
[01:01:35 AM]  Checking each position for level 30...
[01:01:37 AM]  ERROR: Object reference not set to an instance of an object.
[01:01:37 AM]  ERROR: System.NullReferenceException: Object reference not set to an instance of an object.
   at SevenKnightsAI.Classes.SevenKnightsCore.ExpectingScene(SceneType sceneType, Int32 retry, Int32 sleepInterval)
   at SevenKnightsAI.Classes.SevenKnightsCore.ManageHeroes()
   at SevenKnightsAI.Classes.SevenKnightsCore.MainLoop(Object sender, DoWorkEventArgs e)
[01:01:56 AM]  Scene: ...
[01:02:02 AM]  Scene: Heroes
[01:02:03 AM]  Checking each position for level 30...
[01:02:13 AM]  Initializing AI...
[01:02:14 AM]  Changing objective to: Adventure
[01:02:34 AM]  Scene: ...
[01:02:53 AM]  cannot find scene escape
[01:02:56 AM]  Scene: Heroes
[01:02:56 AM]  Changing objective to: Hero Management
[01:02:56 AM]  Start managing heroes
[01:02:57 AM]  Checking each position for level 30...
[01:02:59 AM]  ERROR: Object reference not set to an instance of an object.
[01:02:59 AM]  ERROR: System.NullReferenceException: Object reference not set to an instance of an object.
   at SevenKnightsAI.Classes.SevenKnightsCore.ExpectingScene(SceneType sceneType, Int32 retry, Int32 sleepInterval)
   at SevenKnightsAI.Classes.SevenKnightsCore.ManageHeroes()
   at SevenKnightsAI.Classes.SevenKnightsCore.MainLoop(Object sender, DoWorkEventArgs e)
[01:03:19 AM]  Scene: ...
[01:03:38 AM]  cannot find scene escape

![image](https://cloud.githubusercontent.com/assets/11155951/21940136/6f9be368-d9f5-11e6-9b78-eb08c02f6efb.png)


Why do you remove most frame build targets?


Why reset buttons selection?


Missing updates in the doc, but I guess that'll come later. What's the difference between volumes and pvs? This will make a lot of confusion.


Yes and now that you mention it... I may want to make it longer. On average, pv creation took about 10 minutes on my server.


Yup, will make the change


137438445_Issue5133 (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (2335 of 2392 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-97.62%25-yellow.png)


I would still not consider Recycle as the option until it's clear what would be the usage.


How do record these screencasts btw? Like this https://gist.github.com/dergachev/4627207?
Is there a way to increase the resolution of the recording?


Orem UT 40 Degrees


137438445_Issue5133 (Nigusse) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: OK (0 of 0 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png)


With this version, we run in the following error:

```
5870 [Thread-14-spout-executor[8 8]] INFO  com.digitalpebble.stormcrawler.elasticsearch.persistence.ElasticSearchSpout - Populating buffer with nextFetchDate <= 2017-01-13T18:51:10.710+0100
5929 [Thread-14-spout-executor[8 8]] ERROR org.apache.storm.util - Async loop died!
org.elasticsearch.action.search.SearchPhaseExecutionException: all shards failed
	at org.elasticsearch.action.search.AbstractSearchAsyncAction.onFirstPhaseResult(AbstractSearchAsyncAction.java:204) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.action.search.AbstractSearchAsyncAction$1.onFailure(AbstractSearchAsyncAction.java:139) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.action.ActionListenerResponseHandler.handleException(ActionListenerResponseHandler.java:51) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:984) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.transport.TransportService$DirectResponseChannel.processException(TransportService.java:1091) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.transport.TransportService$DirectResponseChannel.sendResponse(TransportService.java:1069) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.transport.TransportService$6.onFailure(TransportService.java:588) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.onFailure(ThreadContext.java:512) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:39) ~[elasticsearch-5.1.2.jar:5.1.2]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[?:1.8.0_60]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[?:1.8.0_60]
	at java.lang.Thread.run(Thread.java:745) [?:1.8.0_60]
Caused by: org.elasticsearch.transport.RemoteTransportException: [y643DXZ][127.0.0.1:9300][indices:data/read/search[phase/dfs]]
Caused by: org.elasticsearch.ElasticsearchParseException: failed to parse date field [Fri Jan 13 18:51:10 CET 2017] with format [dateOptionalTime]
	at org.elasticsearch.common.joda.DateMathParser.parseDateTime(DateMathParser.java:213) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.common.joda.DateMathParser.parse(DateMathParser.java:66) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.index.mapper.DateFieldMapper$DateFieldType.parseToMilliseconds(DateFieldMapper.java:297) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.index.mapper.DateFieldMapper$DateFieldType.isFieldWithinQuery(DateFieldMapper.java:337) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.index.query.RangeQueryBuilder.getRelation(RangeQueryBuilder.java:419) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.index.query.RangeQueryBuilder.doRewrite(RangeQueryBuilder.java:426) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.index.query.AbstractQueryBuilder.rewrite(AbstractQueryBuilder.java:264) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.search.builder.SearchSourceBuilder.rewrite(SearchSourceBuilder.java:885) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.search.internal.ShardSearchLocalRequest.rewrite(ShardSearchLocalRequest.java:206) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.search.internal.ShardSearchTransportRequest.rewrite(ShardSearchTransportRequest.java:162) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.search.SearchService.createSearchContext(SearchService.java:598) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.search.SearchService.createContext(SearchService.java:547) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.search.SearchService.createAndPutContext(SearchService.java:529) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.search.SearchService.executeDfsPhase(SearchService.java:233) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.action.search.SearchTransportService$5.messageReceived(SearchTransportService.java:291) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.action.search.SearchTransportService$5.messageReceived(SearchTransportService.java:288) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:69) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.transport.TransportService$6.doRun(TransportService.java:577) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:527) ~[elasticsearch-5.1.2.jar:5.1.2]
	at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-5.1.2.jar:5.1.2]
```

I found the following difference between elasticsearch 2.4.1 and 5.1.2 :

In 2.4.1. the object in the RangeQuery was treaten as ByteRef after transport.
However, in org.elasticsearch.index.mapper.DateFieldMapper.parseToMilliseconds the value was instanceof BytesRef and everything works :

```
public long parseToMilliseconds(Object value, boolean roundUp,
                @Nullable DateTimeZone zone, @Nullable DateMathParser forcedDateParser, QueryRewriteContext context) {
            DateMathParser dateParser = dateMathParser();
            if (forcedDateParser != null) {
                dateParser = forcedDateParser;
            }

            String strValue;
            if (value instanceof BytesRef) {
                strValue = ((BytesRef) value).utf8ToString();
            } else {
                strValue = value.toString();
            }
            return dateParser.parse(strValue, context::nowInMillis, roundUp, zone);
        }
```

In 5.1.2. the value here is instanceof Date, the ugly date.toString is used  and throws the error :(

As a workaround, I use the following in the ElasticSearchSpout:
```
        LOG.info("Populating buffer with nextFetchDate <= {}", lastDate);

        QueryBuilder rangeQueryBuilder = QueryBuilders.rangeQuery(
                "nextFetchDate").lte(String.format("%1$tY-%1$tm-%1$tdT%1$tH:%1$tM:%1$tS.%1$tL",lastDate));
```

and the crawler works fine.
I'm not sure if this error is related to Elasticsearch or if some settings are missing.


Ninio just a tip - make sure you are not committing private firebase info into the repo.  Looks very good man!


can be clarified whether you're going to place binaries directly here or you'll create `${go.toolsGopath}/{src,bin,pkg}` here.


git -C spinnaker checkout $GITHUB_REPOSITORY_BRANCH

but this has the side effect of switching branches on you.
This whole thing doesnt really make sense.
This script lives in the repository it is checking out, so you need it to check it out.
Furthermore, the build depends on lots of other repositories which you are not checking out, nor are you giving it the parameters it would require if it were to check them out.

I think you should assume that the repositories are already prepared as a precondition to this script and wire it into the jenkins task prior to wiring in the call to this script.


@WonderToys Are you referring to the Authorization key assignment in the send function? Please clarify


@jorgemoralespou I would think this is a reasonable default. The alternative, Retain would mean that pv's can never be reused and long after a project has been deleted, there's a lot of junk in your pv dirs. Especially for your use case, where you're going to have directories on the user's machines storing the pv's, this would seem like an unnecessary accumulation of stuff that will never get cleaned up. Like I said, if you want "pet" storage, then you're likely going to carefully consider where to put it and for now I would think manually creating the pv for it shouldn't be that bad.


show


Thank you @davidaurelio!!!


@guilhermeblanco this one will throw `Only variables should be passed by reference`, see PreUpdateEventArgs::__constructor


ruby-update (kbenne) - x86_64-MacOS-10.10-clang: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-NA-red.png)


Maybe endings are not big problems, but this new Stockfish will lose queen odds games against relatively weak players.


请问有原因为什么要用yarn替代npm吗？DOC上并没有说明，所以有点困惑。


will update


Probably the smallest commit I ever made. I have no idea why the diff's so big.


Hi


Biuro Podróży
0. Stwórz projekt – aplikacja konsolowa lub WPF (przemyśl wybór, bo zmiana
może być czasochłonna).
1. Stwórz abstrakcyjną klasę SrodekLokomocji.
a) dodaj w niej pola iloscMiejsc (int) oraz cenaBiletu(double) z mod. protected
b) dodaj konstruktor domyślny (pusty)
c) dodaj metodę wirtualną ObliczCene() typu void, bez parametru, która za pole
cenaBiletu podstawia wartość iloscMiejsc *3,
d) dodaj zwykłą metodę zwracającą cenę biletu.
2. Stwórz klasę Autobus dziedziczącą z klasy SrodekLokomocji. W klasie
potomnej wykonaj następujące czynności:
a) dodaj konstruktor parametryczny z parametrem typu int, parametr ma być
podstawiony w pole iloscMiejsc, w konstruktorze należy wywołać metodę
ObliczCene() – w wersji z klasy bazowej
b) przesłoń metodę ToString() tak, aby zwracała informacje o Autobusie np.
Autobus: ilość miejsc: 24, cena biletu: 72.
3. Stwórz klasę Samolot dziedziczącą z klasy SrodekLokomocji. W klasie Samolot
wykonaj następujące czynności:
a) dodaj prywatne pole odleglosc typu int,
b) przesłoń metodę ObliczCene() następująco: jeśli odleglosc jest większa niż
200 za cenę biletu należy podstawić wartość odleglosc * 2,56; w przeciwnym
wypadku należy za cenę biletu podstawić wartość 24.
c) dodaj konstruktor parametryczny z dwoma parametrami (oba typu int),
parametry należy podstawić odpowiednio do pól iloscMiejsc i odleglosc, w
konstruktorze należy również wywołać metodę ObliczCene() – w wersji
przesłoniętej
d) przesłoń metodę ToString() tak, aby zwracała informacje o samolocie:
Samolot: ilość miejsc: 50, odległość: 200, cena biletu: 24.
4. Stwórz dwa interfejsy:
a) IZarzadzaj – w nim dodaj deklarację następujących metod (wszystkie typu
void):
DodajAutobus(int iloscMiejsc)
DodajSamolot(int iloscMiejsc, int odleglosc)
UsunOstatni()
Wyczysc()
b) IData – w nim deklarację metod:
UstawDate(DateTime data) – typ zwracany void
SprawdzDate() – typ zwracany bool
5. Stwórz klasę Podroz. W tej klasie wykonaj następujące czynności:
a) dodaj prywatne pole dataPodrozy typu DateTime
b) dodaj prywatne pole planPodrozy typu List<SrodekLokomocji> (lista
przechowująca środki lokomocji), zadbaj o inicjację pola
c) dodaj prywatne pole koszt typu double i nadaj mu wartość początkową 200
(dwieście)
d) dodaj implementację metod z interfejsów z punktu 5 i podepnij oba
interfejsy do klasy Podroz, zasady implementacji:
- DodajAutobus – dodaje obiekt typu Autobus do listy planPodrozy, dodatkowo
powiększa koszt o cenę biletu
- DodajSamolot – dodaje obiekt typu Pociag do listy planPodrozy, dodatkowo
powiększa koszt o cenę biletu
- UsunOstatni – usuwa ostatni element na liście planPodrozy
- Wyczysc – usuwa wszystkie elementy ze liście planPodrozy
- UstawDate – ustawia pobrany parametr jako pole dataPodrozy
- SprawdzDate – zwraca true kiedy wartość pola dataPodrozy jest większa niż
aktualna data pobrana z systemu (można wykorzystać normalny porządek < w
klasie DateTime); w przeciwnym wypadku zwraca false
e) przesłoń metodę ToString() tak, aby zwracała w kolejnych wierszach
informacje o elementach na liście planPodrozy
6. Stwórz aplikację WPF lub konsolową do testowania powyższych metod.
Logika aplikacji:
- należy wykorzystać metody i klasy stworzone w punktach 1-5
- dodawanie do planu podroży Autobusu i Samolotu musi być
swobodne/elastyczne tzn. można dodać same autobusy, same samoloty lub na
przemian w dowolnej kolejności
- przed dodaniem na listę (planPodrozy) należy upewnić się, że parametry
liczbowe są liczbami dodatnimi wskazanego typu
- przy ustawieniu daty podróży należy użytkownikowi przekazać informację na
temat wpisywanego formatu daty (np. dd.mm.yyyy lub yyyy/mm/dd, itp.) i
aplikacja ma obsłużyć możliwe wyjątki przy zmianie typu string na DateTime
- opcjonalnie użytkownik może wpisać sam dzień (i wtedy domyślnie za czas
podstawi się północ) lub użytkownik może podać i datę i godzinę podróży
- sprawdzenie daty podroży ma wyświetlić komunikat np. MessageBoxa lub info
na konsoli
Punktacja
Polecenia 1-4 po 1 pkt każde.
Polecenie 5 – 2pkt
Polecenie 6
+1 pkt za poprawne działanie kontrolek (tylko dla WPF)
+1 pkt za poprawny algorytm aplikacji przechodzenia po menu (tylko konsola)
+ 1 punkt za obsługę możliwych wyjątków przy konwersji typów i usuwaniu z
pustej listy
+ 2 za logikę aplikacji

Przykładowy screeny wpf
Przykładowy screen konsola:

Diagramy UML


I never got randomly drowsy with stims, and I understand your point, but I still think it's fine. As always, there's a tradeoff, move around at hypersonic speeds when combining both, but one stun and you're out.


+	A cloud service for CRM (YMENS)


Heh... I used it...


With this commit the hunter's traps can not be seen at close range and that is not correct. If the hunter uses traps and his enemy is around 10 yards or less, the enemy can see the trap.


I was about to warn you about it ! Thank you very much for doing this quick fix !


LGTM


More full description


Actually:
```crystal
{% if flag?(:x86_64) || flag?(:aarch64) %}
```

Maybe we shoud introduce new flags, like `abi64` and `abi32`? I mean, there are other 64bits archs (e.g. S/390, MIPS, RISC V, PowerPC, SPARC).


Thank you for the report. A mistake. Pushed as v1.4.3.


Yikes, that 8-second startup time is brutal.  Thank you for sending this over -- it's very helpful to see what times are like on an older PC.

I've got some additional ideas for improving the worst offenders, and will try to get those implemented ASAP.


Oy vey...


137438445_Issue5133 (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-UnitTestsCoverage-Debug: OK (1208 of 1208 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.png) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-36.28%25-green.png)


Changes:

setting your waifu or pokemon will now let the battle system use that character as default for defending and attacking.


Pedido


Ok, cool.  I'll get rid of it. I'll make sure there is a nice way to add custom events like this for custom server implementations.


Well, "oc cluster" is not for long lived clusters, as @bparees says, why so many volumes? I would think that 10 minutes is a lot of overhead.


@jrieken thanks for the review, sir!


Hum, for the story, I better understand why some game developer said that the only sane language is asm.

Here the generated code for `TEX0.TBP0 >> 5` (I suspect a strange optimization bug on GCC but still).
```
    38e0:	movzx  eax,BYTE PTR [ebx+0x1]
    38e4:	movzx  edx,BYTE PTR [ebx]
   ...
   ...
    38ed:	and    eax,0x3f
    38f0:	shl    eax,0x8
    38f3:	or     eax,edx
    38f5:	sar    eax,0x5
```


@bjreath Thanks for letting us know! We've just released 0.8.3 of the celluloid dependency that reverts all the breaking changes! Sorry for the inconvenience. Stay tuned for a new version of the ruby-client.


I think you can directly use `HttpUrl.parse` for this and check for `null`. No reason to waste an allocation of `Request`


huahua


re: Python feedback
Hi Ivan
cc: @aramnath @reshama @julialintern @vinoad @gfsoileau

Good job in completing the Python sections! 👍 . And great job with the markdown!
I noticed you haven't finished the pre-work. Pls feel free to seek the help of one of the TAs for help with this if you feel you need it, that is what we are here for! We will also send out a solutions set soon.
I've provided a little extra background for questions in Python 1:
Q1. Dictionaries have keys and values. Each of the keys within a dictionary must be unique. If you make an assignment using an existing key as the index, the old value associated with that key is overwritten by the new value. Since tuples are immutable, they will work as keys in dictionaries.
Q2. Sets are implemented using hash functions, which grants them constant lookup time O(1).
Whereas in lists, you have to iterate through the whole list using the indices, and that is linear time operation O(N).
If you are not familiar with the big O notation, it's a great subject to review, and here is a nice cheatsheet:
http://bigocheatsheet.com/
Best,
Gina


This fixes a bug that was introduced by Kevin in the following commits:
b9f5e00886600b18441188e320e775284fae039d
eb307e53256b12bde24a74aa5121aee278c32ee3


The following doc(s) have been deployed to the [commandsas](https://commandsas-static-docs.pantheonsite.io/docs) Multidev environment:
- [.gitignore](https://github.com/pantheon-systems/documentation/commit/941c04a4cad7b2d0887410b65eea0a390ec099c9/.gitignore)
- [source/docs/assets/terminus/commands.json](https://github.com/pantheon-systems/documentation/commit/941c04a4cad7b2d0887410b65eea0a390ec099c9/source/docs/assets/terminus/commands.json)


where i don't region being fetch from the region cache in `formData()`


This change is wrong. FireFox will crash having const in for (in) loop


re: Python feedback
Hi Pallavi
cc: @aramnath @reshama @julialintern @vinoad @gfsoileau

Good job in completing the Python sections! :thumbsup: Your code was clean and succinct. And great job with the markdown!

I've provided a little extra background for questions in Python 1:

Q1. Dictionaries have keys and values. Each of the keys within a dictionary must be unique. If you make an assignment using an existing key as the index, the old value associated with that key is overwritten by the new value. Since tuples are immutable, they will work as keys in dictionaries.

Q2. Sets are implemented using hash functions, which grants them constant lookup time O(1). Whereas in lists, you have to iterate through the whole list using the indices, and that is linear time operation O(N).
If you are not familiar with the big O notation, it's a great subject to review, and here is a nice cheatsheet:
http://bigocheatsheet.com/

We will be sending out solution sets to the pre-work questions soon.

Best,
Gina


This is all happening in the background after you started your cluster. So not necessarily adding to the startup time.


Баг, не полностью удаляется KeyValue.
Последний ключ не удаляет = утечка памяти в последнем DataPack.


nice


My tessdata is stored at /usr/share/tessdata which is where the package manager on my OpenSUSE system (zypper) installs them.

In this case, will a correct value of TESSDATA_PREFIX be /user/share or /user/share/tessdata?


Regressions noted:
taito_l.cpp - kurikint and clones
Required memory bank ':bank7' not found

taito_l.cpp - raimais and clones
Required memory bank ':bank6' not found


Eit algo esta mal


gj


Thanks. I'll be aware for next time ... hopefully.


re: Python feedback
Hi Josephine
cc: @aramnath @reshama @julialintern @vinoad @gfsoileau

Good job in completing the Python sections! :thumbsup: Your code was clean and succinct. And great job with the markdown!

I've provided a little extra background for questions in Python 1:

Q2. Sets are implemented using hash functions, which grants them constant lookup time O(1). Whereas in lists, you have to iterate through the whole list using the indices, and that is linear time operation O(N).
If you are not familiar with the big O notation, it's a great subject to review, and here is a nice cheatsheet:
http://bigocheatsheet.com/

We will be sending out solution sets to the pre-work questions soon.

Best,
Gina


commit merge 13/01/2017 19:52


Hey Sangwan70,
What do you see when you execute these 2 commands in the terminal?
`echo $JAVA_HOME `
and
`java -version'


Funny, just submitted something similar.


It causes #18824
All Bosses without entry in linked_respawn, can respawn now.


@bvierra @aditya2272sharma - There was some confusion this week. We have resolved the issue. Update published a short time ago: https://docs.microsoft.com/en-us/intune/get-started/what-to-know-before-you-start-microsoft-intune

For the commit with this update, see https://github.com/Microsoft/IntuneDocs/pull/299/commits/e2810513646828cc5da734f3af9cc8d81e0c03fc.


Isn't it a duplicate of http://tests.stockfishchess.org/tests/view/58791dfd0ebc5915193f755d ?


@gh2k Update published a short time ago: https://docs.microsoft.com/en-us/intune/get-started/what-to-know-before-you-start-microsoft-intune

For the commit with this update, see https://github.com/Microsoft/IntuneDocs/pull/299/commits/e2810513646828cc5da734f3af9cc8d81e0c03fc.


137438445_Issue5133 (Nigusse) - i386-Windows-7-VisualStudio-14: OK (2301 of 2358 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-97.58%25-yellow.png)


re: Python feedback
Hi Lisa
cc: @aramnath @reshama @julialintern @vinoad @gfsoileau

Good job in completing the Python sections! :thumbsup: Your code was clean and succinct. And great job with the markdown!

I've provided a little extra background for questions in Python 1:

Q1. Dictionaries have keys and values. Each of the keys within a dictionary must be unique. If you make an assignment using an existing key as the index, the old value associated with that key is overwritten by the new value. Since tuples are immutable, they will work as keys in dictionaries.

Q2. Sets are implemented using hash functions, which grants them constant lookup time O(1).
Whereas in lists, you have to iterate through the whole list using the indices, and that is linear time operation O(N).
If you are not familiar with the big O notation, it's a great subject to review, and here is a nice cheatsheet:
http://bigocheatsheet.com/

We will be sending out solution sets to the pre-work questions soon.

Best,
Gina

I've provided a little extra background for questions in Python 1:


Just noticed the test by Rocky did'nt have the time to look into it. Benches are different, so I assume not.


Almost. In my version I include the PassedFile, in his version, he doesn't.


Nice catch :)


Why are you still coding? We will only be evaluating your code committed up to 10:00 am


Ah ok, well let us what happens, hope that at least one passes...


I have this fixed in my work. No need for this - sorry.


What is this?


Consistent space and enter keystrokes between buttons and anchor buttons (#459)

Preview: docs
Coverage: core | datetime


OK good, just making sure.


Well, the more we put into the lazy eval, the better isn't it ? PassedFile is not a big difference anyway.


Should we try them sequentially ?


As you'd expect, the LFS-free client downloads only the pointer file. There are no errors, but I could see that as a risk if someone was:

- Using the CLI only (most desktop clients come with LFS support).
- Unfamiliar with Git LFS, and edited—for whatever reason—the pointer file.

I can point that out. The test repo is [here](https://github.com/Schoonology/git-lfs-test), and I have a local revision of its README that includes how the testing was carried out. I want to link back to the blog, so I'll wait to push the README until I know where to link.


¿Qué cosa?


Fails with A* due to memory usage, completes with BFS, but with memory usage at about 99% and just about to fail (on a windows machine with 16GB).

States explored in BFS: 6,042,250
Running Time: ~38 minutes

A* fails presumably because as mentioned in prior commit, it doesn't prune states effectively for this problem, and it has the additional overhead of keeping track of costs for each state as well as pointers to parent states (which is like the explored set in BFS, but adding another set with duplicates of every state to track costs).


What, you don't like them?


I meant that the first condition is not necessary.
tl;dr: unless you wanna support IE5.5* you just have to remove `xhr.status === 204 && `.

\* replace `nodeName` by `tagName`


Yes, it makes sense to first test Rockys, just changed the prio to -1. In principle, the more you put in lazy the better, but it could be that you increase lazy variance to much and you should readjust the threshold.


Try to maintain the original authorship in the commit and the commit message. You may add something like "Upstream commit <shortened-hash>", or some longer remarks if the backport required massaging of the code. Also maintain the signed-off, just add yours to the list.

Is this based on a single upstream commit? If not, please unfold again.


This is a test, what does this do ?


load to desktop


That's quite a bump in wait time...were you actually seeing boot times that were longer than 30 seconds? @mod mentioned that he saw mid-20's (via https://github.com/elasticdog/packer-arch/pull/56), but I wouldn't want to add a ton of extra time.

_@elasticdog wishes there were a cleaner way instead of just blindly sleeping_ ☹


бажано таки побачити реалізацію на php, замість опису


Ok, then I'll do away with the `$GITHUB_REPOSITORY_BRANCH` logic in this script and comment that `spinnaker/` should exist and be on the branch you want to run.


best commit message ever


import pandas as pd
import numpy as np
import matplotlib.pyplot as plt
import string
dates=pd.date_range('20170101',periods=30)
df =pd.DataFrame(np.random.randn(30,6),index=dates,columns=list("ABCDEF"))


das jar befindet sich in https://repo.metasfresh.com - danke an [metas-ts](https://forum.metasfresh.org/t/einbinden-eines-jars-das-in-keinem-maven-archive-existiert/117/7)


This is change causes an assert failure:
```
$r3-core --do "a"
src/core/c-error.c:198: Trapped_Helper_Halted: Assertion `SER_LEN(GC_Manuals) >= s->manuals_len' failed.
```

I think it's because when it [pushes](https://github.com/metaeducation/ren-c/blob/f745cf9e667e2239f0e24f831b4ed8205e6627e9/src/os/host-main.c#L927) the state, `startup` was a manual series, and `state.manuals_len == SER_LEN(GC_Manuals)` (= 6 to be exact) and when it errors out in [Apply_Only_Throws](https://github.com/metaeducation/ren-c/blob/f745cf9e667e2239f0e24f831b4ed8205e6627e9/src/os/host-main.c#L952), GC_Manuals was cut off by one, and thus `SER_LEN(GC_Manuals) >= s->manuals_len` failed.


Put this back. This command isnt restricted to jenkins.
I use it all the time manually. I dont want to have to add lots of environment variables just to run this.
In my earlier suggestion I meant to conditionally define it, using the above if it wasnt already supplied.


ok, I think I get it. 4h left to midnight, I should find a minute to get back to it :)


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 30](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1444&buildTypeId=XbimEssentials_XbimEssentials) is now running


Great, thanks a lot for doing this! I was about to look into this as well.

We have linux repo internally which has all those patches applied to branch that is based on the upstream yocto tree we pull via meta-intel. You patch(es) should make it into that repo as well, will send you the details.


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 30](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1444&buildTypeId=XbimEssentials_XbimEssentials) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:45


I believe this move breaks links on the Projects page.


Who the heck is this??!?!? Anon?!??!


I dont think this is restricted to 1404. If so, it isnt this script that is defining (or enforcing) the policy.


@k-ljung you may check the latest develop version now for converting the MusicXML tempo to `<scoreDef>`. @craigsapp This is where the Humdrum importer puts it, so maybe you want to use that, too.


Typo ? "it will stop" or "it will be stopped"


I was seeing it come up around the mid 20 second mark, but it might have been related to host-system resources.
I added a few extra so that, no matter what, it would be sure that the machine was up before beginning to type the rest of the boot commands.


Partly takes care of issue #5


Interestingly, this change means that `4.23` is now rendered "4.2300000000000004263", while it was previous rendered as "4.23". This is relevant for two PHPC tests where we print a float through libbson's JSON formatter.


@Martoon-00 we must exit on such cases, not only print error!


That was ported from [this](https://github.com/sochix/TLSharp/blob/86d373db266ce72275a536d5b2a007a5390f7100/TLSharp.Core/Auth/Step3_CompleteDHExchange.cs#L39). I guess it's part of the authentification process. But you sir found out that this "unused" variable was removed. Thank you!! Let's try how it works with it.


положение вещей на момент пятницы 13.01.17

![screen shot 2017-01-13 at 22 18 04-fullpage](https://cloud.githubusercontent.com/assets/3063817/21942485/66482414-d9de-11e6-9a4e-d8326c7f5627.png)


@nelsonic surely this is a breaking change and is not backward compatible. We have gone from:
`module.exports = sendEmail () {...}`
to
`module.exports.email = sendEmail () {...}`

So anyone who has installed sendemail as suggested with `npm install sendemail --save` (e.g. we have it in our package.json as `sendemail: ^2.5.0`) will suddenly have the error `TypeError: email is not a function`


@nfeske, @chelmuth: please add to staging


Hello @superyarik, I can confirm that this change is currently in the `next` branch.

We recently changed our release policy (see the [relevant chapter](https://github.com/BobKnothe/autoNumeric/tree/next#how-to-push) in the readme).

It's now normal that there is no `dist` folder in `next` since it's the dev branch and we do not want to put generated files in the git repository (which would make merging a pain).

The idea is that if somebody want to use the *unstable* dev branch `next`, then they should be able to [generate](https://github.com/BobKnothe/autoNumeric/tree/next#make-your-changes) the `dist` files themselves, while other users wanting to use the stable `master` branch will be able to use the `dist` files directly since we'll force-add those only on each official release, making them available for direct download of via a CDN.

Does that answer your question?


Yes. A typo! Please use it will be stopped


Ok I see, so are you gonna change it?

Btw. If that's not a problem, could you explain to me how do we get number `3` in the example?
https://github.com/Reactive-Extensions/RxJS/blob/master/doc/api/core/operators/debounce.md#example
There's no 500ms timespan after `1` (at 600ms). It's really confusing.


![](https://github.trello.services/images/mini-trello-icon.png) [Validar PDB conforme conteúdo](https://trello.com/c/RtUbnsdN/9-validar-pdb-conforme-conteudo)


But it's adding to the time you need the cluster up to succeed provisioning
and it's adding to the real provisioning time, as the job will not succeed
until all PVs are provisioned, which should be the configuration.


@NSkelsey: missing file.

going to add a file just with the removed content.


Haha it won me "best commits" @ hackathon XD


Yes code might not use the variable but it reads data and cursor moves further and next read will be from new position. Code formatter removed this line because `hashsum` hasn't been used anywhere and thought this line is useless, it might have removed some other lines, I suggest reviewing this commit for more issues like this.


137438445_Issue5133 (Nigusse) - x86_64-Linux-Ubuntu-14.04-gcc-4.8-IntegrationCoverage-Debug: OK (1784 of 1784 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-100.0%25-green.png) ![Coverage Badge](http://img.shields.io/badge/coverage%20status-71.17%25-green.png)


@sambernard shouldn't we leverage aliases though?


The following doc(s) have been deployed to the [commandsas](https://commandsas-static-docs.pantheonsite.io/docs) Multidev environment:
- [.gitignore](https://github.com/pantheon-systems/documentation/commit/941c04a4cad7b2d0887410b65eea0a390ec099c9/.gitignore)
- [source/docs/assets/terminus/commands.json](https://github.com/pantheon-systems/documentation/commit/941c04a4cad7b2d0887410b65eea0a390ec099c9/source/docs/assets/terminus/commands.json)
- [composer.json](https://github.com/pantheon-systems/documentation/commit/cd8fcfb07ff74d86372a16261f3eb833a1acf6ec/composer.json)
- [composer.lock](https://github.com/pantheon-systems/documentation/commit/cd8fcfb07ff74d86372a16261f3eb833a1acf6ec/composer.lock)
- [source/_partials/navbar.html](https://github.com/pantheon-systems/documentation/commit/cd8fcfb07ff74d86372a16261f3eb833a1acf6ec/source/_partials/navbar.html)


llvm35 and llvm36 were removed, but not added to homebrew/core. Was this intended? I would like llvm35 and llvm36 to stay available, if possible; I use them in my automatic test build matrix, to test regressions between compiler versions.


137438445_Issue5133 (Nigusse) - x86_64-Linux-Ubuntu-14.04-custom_check: OK (0 of 0 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-passing-green.png)


# comment


@Younes-L thanks. Fixed on https://github.com/TilesLocalization/resources/commit/1dd735230cc32cb041c3418ef9718b36a6776cd5


:heart: :heart:


Yessss it is solved!!!! Thank you a lot @k1-hedayati!!


aha hier dus ;)


There is no extra stun time with morphine FYI


Nervermind anymore, @k1-hedayati spotted it.


Debian isn't an architecture, it's an operating system...


You're welcome :)


The following doc(s) have been deployed to the [commandsas](https://commandsas-static-docs.pantheonsite.io/docs) Multidev environment:
- [composer.json](https://github.com/pantheon-systems/documentation/commit/cd8fcfb07ff74d86372a16261f3eb833a1acf6ec/composer.json)
- [composer.lock](https://github.com/pantheon-systems/documentation/commit/cd8fcfb07ff74d86372a16261f3eb833a1acf6ec/composer.lock)
- [source/_partials/navbar.html](https://github.com/pantheon-systems/documentation/commit/cd8fcfb07ff74d86372a16261f3eb833a1acf6ec/source/_partials/navbar.html)


I updated it to be more "realistic" in visualization for yee.


8-char tabs please


Did this help the touch work better?


travis ci verbose error (intended behavior)

```
Running the tests in ‘tests/demo_iris.R’ failed.
Last 13 lines of output:
  +                            cnfnd=glm(family='gaussian',
  +                                             y~mat_trt+Sepal.Width+ I(Petal.Width/sd(Petal.Width))+letters1,
  +                                             data=dat_input[,c("y","mat_trt","Sepal.Width","Petal.Width","letters1")]))
  +                      )

  Since 'X' was supplied, we will focus on : Sepal.Width Petal.Width letters1
  Error in assert_names_match(cnfnd = cnfnd, Y = Y, D = D, X = X) :
    Some of your specified pre-treatment variable names in argument X are not found in the terms of your specified 'cnfnd' argument. They are: Petal.Width

```


new to programing


Thanks!


The following doc(s) have been deployed to the [commandsas](https://commandsas-static-docs.pantheonsite.io/docs) Multidev environment:
- [.gitignore](https://github.com/pantheon-systems/documentation/commit/941c04a4cad7b2d0887410b65eea0a390ec099c9/.gitignore)
- [source/docs/assets/terminus/commands.json](https://github.com/pantheon-systems/documentation/commit/941c04a4cad7b2d0887410b65eea0a390ec099c9/source/docs/assets/terminus/commands.json)
- [composer.json](https://github.com/pantheon-systems/documentation/commit/cd8fcfb07ff74d86372a16261f3eb833a1acf6ec/composer.json)
- [composer.lock](https://github.com/pantheon-systems/documentation/commit/cd8fcfb07ff74d86372a16261f3eb833a1acf6ec/composer.lock)
- [source/_partials/navbar.html](https://github.com/pantheon-systems/documentation/commit/cd8fcfb07ff74d86372a16261f3eb833a1acf6ec/source/_partials/navbar.html)
- [scripts/deploy-live.sh](https://github.com/pantheon-systems/documentation/commit/ef2e828aef583813c6f2d5fd648a74eab6510852/scripts/deploy-live.sh)
- [scripts/deploy-multidev.sh](https://github.com/pantheon-systems/documentation/commit/ef2e828aef583813c6f2d5fd648a74eab6510852/scripts/deploy-multidev.sh)


This thing definitely fixed the issue we were experiencing with our own `ParameterResolverFactory` implementations~


The website still shows Katana at WL 3? Didn't these get merged? Need to sync @brianfeister ?
http://www.openlegendrpg.com/core-rules/04-wealth-equipment#weapons-implements


Wrote up an issue (#59) in case anyone else has the same problem.


This line should be the line that was in the org.kuali class:
pcardDocument.getDocumentHeader().setDocumentDescription("Auto Approved On " + dateTimeService.toDateTimeString(currentDate) + ".");


We just had a user drop into channel thinking that because the contact information was at the end of the document, it applied to module authoring and review in general.

While I'm all in favour of people finding the channel if they have toolchain problems, having somebody turn up wanting an "is this module I'm working on useful" for a set of grammar utilities (which ... looked useful to me, maybe, but I'm hardly the right person to have an opinion there) seemed suboptimal.

So it's likely worth rephrasing or moving this somehow.


Many of these imports are not used. Use CTRL + Shift + O to "organize" the imports (remove all imports that are unused, plus sort them.)


Time to use `traceM` in `WorkMode`.


shouldn't you be able to use composition here?

```
let start = startAndExposedMessageSink >> ignore
```

or am I wrong?


@cybermerlin  I just tested this out and the problem still remains when I **click** on a column header to sort by column.


@Albinoman887 No, it's to stop CTS and SafetyNet being flagged as modified.


import this module to your project


This constructor does not appear to be needed. The transactionEntries are populated in the org.kuali class.


This constant is never used. Please remove it.


Unnecessary comment.


I think we should revert this commit. We definitely shouldn't register these environments, since it doesn't make sense to evaluate on the one-life version of the environments -- it's just something you do in training. People have traditionally added the EpisodicLifeWrapper in their own code after applying the monitor, but before training.


Unnecessary comment. Please remove it.


This field is unnecessary. Please remove it.


There's an additional check lower down. Some themes may not use bootstrap but will use font-awesome.
Have you found any issues with this change so far?


Getter for an unnecessary field. Please remove it.


please take a look here: https://github.com/astro/rust-lpc43xx


Setter for an unnecessary field. Please remove it.


***this commit also includes the testing of displaySchedule***


need to change the license type


Is this needed?


Unused constant. Please remove it.


Hello, bon j'ai une merde l'ampoule du neutre est commandée par la masse je peux donc pas avoir de signal en +5V. Comment je peux faire niveau code?
Thx


Useful hint (related to bug #67).


## First screen

![screen shot 2017-01-13 at 20 53 07](https://cloud.githubusercontent.com/assets/2672413/21943617/4f300af0-d9d2-11e6-9696-9352b2de958e.jpg)

## Adding bot screen
![screen shot 2017-01-13 at 20 52 40](https://cloud.githubusercontent.com/assets/2672413/21943605/403abdce-d9d2-11e6-878b-6e0b86e812cd.jpg)


I am getting an Miwok has stopped error
here is my java code
`package com.example.android.miwok;

import android.content.Intent;
import android.os.Bundle;
import android.support.v7.app.AppCompatActivity;
import android.view.View;

public class MainActivity extends AppCompatActivity {

    @Override
    protected void onCreate(Bundle savedInstanceState) {
        super.onCreate(savedInstanceState);
        // Set the content of the activity to use the activity_main.xml layout file
        setContentView(R.layout.activity_main);
    }

    public void openNumbersList(View view) {
               Intent i = new Intent(this, NumbersActivity.class);
                startActivity(i);
            }
}'

what is wrong with it


This entire class appears to be unused. Please remove it.


Updated by clang format.


I tried to repro this yesterday but didn't see this issue. What are the errors you're getting? (e.g. is it the same script / sourceURL that's being loaded too many times?)


Now that it is 2017, will the 2016 version be stable?


The changes to this class appear to be unnecessary. Please remove it.


아니오


Since non-zero current sum is legit for patch clamp injected current, I suggest to only warn once, instead of for each time step, unless verbose=True


Use Eclipse's Code Formatter (CTRL + Shift + F) to format the file and remove unnecessary trailing space and blank lines.


I'm still thinking your implementation should match the Dragula API...  i.e. (clone, original, type).

In your code, when user destruct the args, they get "item", which means the original element, and the itemVM it means either 'copy' or 'mirror'..., confusing...

but it's your project, you can do whatever you want...


Werner, what else besides code formatting did you change?
I mean this no looks 1:1 the same like my original proposal https://github.com/struberg/javaConfig/blob/master/api/src/main/java/io/microprofile/config/spi/ConfigSource.java
Even the wording of the JavaDoc got copied over 1:1.
I fail to see where the degree of inventive ingenuity is which justifies authorship.

To be blunt: changing just line breaks to different positions doesn't justify to add @author.

Beside from that it is a good style to use a single line per sentence. This is a recommendation from Asciidoc but also makes perfect sense for JavaDoc.
I recommend to revert this commit.


It was loading Main.js multiple times (more than 2x). Not sure why it was happening.

Let me try to reproduce it again.


what is this shit


Test Comment


I think so too. I was confused by changing of display state. But it looks good to revert it.
With this commit, when is_display_on() is true then changed to false there will be no choice.


aaaa


Ok. That's good.


setting the piece null doesn't instantiate it. I'll make this part clearer in next commit


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 27](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1441&buildTypeId=XbimEssentials_XbimEssentials) is now running


I've just updated HTML_Class. Followed to your corrections, check it when
you'll be free.
https://github.com/errorrmaxim/Boost_camp/blob/master/HTML_Class/main.cpp

2017-01-12 13:52 GMT+02:00 Dmitriy <notifications@github.com>:

> The rest is fine! Good job!
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/errorrmaxim/Boost_camp/commit/9267dd376ca69a5de2d6b5833ead977deda489da#commitcomment-20451092>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AQVSIZp2yoPRTMXU2am-_cjZaVwYaV_9ks5rRhQLgaJpZM4Lhqcx>
> .
>


ruby-update (kbenne) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.61: Build Failed

![Build Badge](http://img.shields.io/badge/build%20status-failing-red.png)


I had to test that it worked on circle. :)


> 75行cout输出语句的缩进不对吧，难道不应该跟原75行缩进一样吗？

:sweat_smile:  的确不太对, 我直接在网页上编辑的, 没注意...


TeamCity Xbim :: Xbim Essentials :: XbimEssentials [Build 27](http://xbimbuilds.cloudapp.net/viewLog.html?buildId=1441&buildTypeId=XbimEssentials_XbimEssentials) outcome was **FAILURE**
Summary: Exit code 1 (new) Build time: 00:01:39


The ids really should be only internal and never printed.


> I tried for a feasible solution as follows by using ordinary iterators instead of reverse iterators. Please check.

:+1:  NP.


I think this can be made simpler using http://book.pythontips.com/en/latest/ternary_operators.html.  Avoid reassigning any variables (utc_series_values and mask, in this example).


![](https://github.trello.services/images/mini-trello-icon.png) [Toolbar in Company Home and other activities](https://trello.com/c/cUEFLitx/27-toolbar-in-company-home-and-other-activities)


Oh? That's bad. What do they look like in other terminals?


first commit


Re 1. Done (see most recent commit)
Re 2. Done (see most recent commit)
Re 3. We could, but I'm not sure if there is a 'simple' way of doing this, do you have something in mind.
Re 4. Only if we know of other instances of courts using this specific format ("month - month year").  If not, I suppose we could and it would only be used here.  It would need a super specific name like estimate_date_from_hyphenated_month_range


من قہۗائد مہۗلوگ الفہۗسہۗيے بہۗوگ


Fixed, thanks!


@takashiki 这里是不是没有引号？
`text: data.s_url`


mb, ah i see


卧槽居然有人……只是不想轻易让别人直接盗走啦


start coding


wait so when you set p = null it just doesn't instantiate even when you like declare it as a Piece?


I guess a simple way of doing it, in more lines of code than I would like, would be to use a hardcoded list of month names.  I dont think there is a way to find the month between to months with dateutil.  Also, we'd have a headache if they decided to start using ranges of more than 3 months.  In my opinion, an estimates date is an estimated date, and if its within a few months or a few weeks doesn't make much of a difference.  But, you know better than I what users need.


In PowerShell:
`r n b q k b n r
p p p p p p p p
â?    â?    â?    â?
  â?    â?    â?    â?
â?    â?    â?    â?
  â?    â?    â?    â?
P P P P P P P P
R N B Q K B N R`


Ah, I see.  Sorry to see it irritates you so much!  I blame https://github.com/editorconfig/editorconfig/issues/179.

Sent from my Windows 10 phone

From: Martin Thomson<mailto:notifications@github.com>
Sent: Thursday, January 12, 2017 6:05 PM
To: quicwg/base-drafts<mailto:base-drafts@noreply.github.com>
Cc: Mike Bishop<mailto:Michael.Bishop@microsoft.com>; Comment<mailto:comment@noreply.github.com>
Subject: Re: [quicwg/base-drafts] This trailing whitespace has to end (3096ae6)

I had to test that it worked on circle. :)

-
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<https://github.com/quicwg/base-drafts/commit/3096ae64e07ed8622b7d704c43c889c2b999c629#commitcomment-20461874>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AEE2hbqVHqAbYCAonVJnQ_7u23Kbqzq4ks5rRtvMgaJpZM4LiaOL>.


I wonder how many of these should be in the main Drasil database, instead of being specific to SSP?


Consider using indexers:

```csharp
_.test["Value 1 listed in #value_list"] = () =>
{
    _.url(testpage);
    _.startEq("", "");
}
```


It's only because editors that don't have this problem actually trim on save and introduce bunches of unrelated changes, like the ones below.


I will try to get out of the habit of doing it. It helps my learning but i realize it's hard to see on gitHub. sorry!


The best practices recommended in this chapter was extremely helpful. In the past, I have always struggled, especially with code version retention and documentation. I look forward to trying out the best practices to improve my coding habits.


Would you be interested in raising a PR with your changes? Seems like I probably should have made React a peer dependency to begin with!


Good catch, thanks.  Added 6b7019a287c23b2930b2d7067f0671037a0104f4


손승빈 thstmdqls@naver.com


*Day 4


Isn't it "blueMSX" ? See: http://www.bluemsx.com/

And you can find it all over the source code too...


- (void)viewDidLoad {
    [super viewDidLoad];
    // Do any additional setup after loading the view, typically from a nib.
    [self accessToServerForGetGetLogin];
}

#pragma mark -- 网络请求
-(void)accessToServerForGetGetLogin
{

    NSString *requestName = GetLoginKey;
    NSString *url = @"http://apis.haoservice.com/lifeservice/cook/query?";

    NSMutableDictionary *postInfo = [NSMutableDictionary dictionary];

    postInfo[@"menu"] = @"土豆";
    postInfo[@"pn"] = @1;
    postInfo[@"rn"] = @"10";
    postInfo[@"key"] = @"2ba215a3f83b4b898d0f6fdca4e16c7c";
    [NetWorkRequest netWorkRequestByPostMode:url parameters:postInfo requestName:requestName delegate:self];

}

-(void)netWorkRequestSuccess:(id)data userInfo:(NSDictionary *)userInfo parameters:(NSDictionary *)getparameters
{
    //服务器连接成功
    NSString *requestUsername = [userInfo objectForKey:@"username"];

    if ([requestUsername isEqualToString:GetLoginKey]) {

        NSDictionary *dicR = (NSDictionary *)data;
        NSLog(@"%@",dicR);

    }

}
-(void)netWorkRequestFailed:(NSError*)error userInfo:(NSDictionary *)userInfo parameters:(NSDictionary *)getparameters
{
    //服务器连接失败请重试
    NSLog(@"%@",error);
}


@a-frobot docs-v0.4.0


TeamCity ReOpenLDAP :: devel [Build 339](https://binbug.bigbrother-matrix.ru/teamcity/viewLog.html?buildId=3188&buildTypeId=ReOpenLDAP_Devel&guest=1) is now running


Result:
![about2](https://cloud.githubusercontent.com/assets/3359132/21916435/dd0d1a80-d940-11e6-82f6-632d6c9c9bf0.png)


quedaria entonces asi:

Product.findById(req.params.productId, function(error,product){


I got no beef wid dis.


segun la estructura que hay en la documentacion:

Model.findById(obj._id, function (err, doc){
  // doc is a Document
});


You could also use ``combinators.smart`` for this, your first ``cleave>array [ ] all?`` could be ``1&&`` and your ``cleave>array [ ] any?`` could be ``1||``... has the advantages of not creating intermediate array and early exiting either when encountering a ``f`` value, or when encountering a true value.


This addresses issue #17.


fixed! thanks for the heads up. (i'll update the git when i iron some other things out.)


Thank you very much!


When do you think this will be on CRAN? As it stands, the package can't be installed on RHEL 6.x because of the older libxml2.
Thanks!


We call it FAST: https://wiki.libretro.com/index.php?title=Beetle/Mednafen_PCE_FAST


@thom8 You should commit the `composer.lock` file as it records what package versions are installed by `composer install`.


And upstream call it pce_fast heh: http://mednafen.fobby.net/documentation/pce_fast.html


Restoring old README


@thom8
Here's a great explanation of why you should commit `composer.lock`:

- https://getcomposer.org/doc/01-basic-usage.md#composer-lock-the-lock-file


#include<iostream>
#include<opencv2\opencv.hpp>
#include"moving_objs_detect.hpp"
#include"HoughTransform.cpp"
#include"FitLine.cpp"
#include"denseSift.hpp"
#include"sparse_coding.hpp"
#include<vector>

using namespace std;
using namespace cv;

Mat SiftCalculate(Mat &img)
{
	CDenseSIFT m_denseSIFT; //sift特征提取类的对象
	m_denseSIFT.init(); //计算sift特征之前必须先初始化一次

	Mat new_size_img;
	Mat siftArr;
	resize(img, new_size_img, Size(64, 64), 0, 0, CV_INTER_LINEAR);
	m_denseSIFT.CalculateSiftDescriptor(new_size_img, siftArr);
	return siftArr;
}

int main()
{
	VideoCapture capture("2.mp4");
	MovingObjsDetector moving_objs_detector; //运动目标检测类的对象

	CSparseCoding m_sparseCoding; //稀疏编码类的对象

	while (1)
	{
		Mat frame;
		capture >> frame;
		if (frame.empty())
		{	break;	}

		Mat half_frame;
		resize(frame, half_frame, Size(frame.cols / 2, frame.rows / 2));

		//运动目标(车辆)检测
		vector<Rect> moving_objs_poses;
		moving_objs_detector.detect(half_frame, moving_objs_poses);
		for (auto &pos : moving_objs_poses)
		{
			//原图中标注出运动目标位置
			rectangle(half_frame, pos, Scalar(0, 255, 255), 1);

			//计算运动目标的sift特征
			Mat siftArr = SiftCalculate(half_frame(pos));
			imshow("siftArr", siftArr);

		}
		imshow("运动目标检测", half_frame);

		waitKey(30);
	}

	waitKey();
	return 0;

	////////////////////////////////////////////////////////////////////////////////////
	////////////////////////////车道线检测+拟合+运动目标检测////////////////////////////
	//VideoCapture capture("1.avi");
	//MovingObjsDetector moving_objs_detector;

	//while (1)
	//{
	//	Mat frame;
	//	capture >> frame;
	//	if (frame.empty())
	//	{	break;	}

	//	Mat half_frame;
	//	resize(frame, half_frame, cv::Size(frame.cols / 2, frame.rows / 2));

	//	//车道线检测+拟合
	//	vector<Vec4i> houghlines;
	//	houghlines = HoughTransform(half_frame); //霍夫变换找直线
	//	for (size_t i = 0; i < houghlines.size(); i++)
	//	{
	//		Vec4i l = houghlines[i];
	//		Point start_Point(l[0], l[1]);
	//		Point end_Point(l[2], l[3]);
	//		//参数：Mat(image),Point1, Point2,Thickness,lineType
	//		line(half_frame, start_Point, end_Point, Scalar(0, 255, 0), 2, CV_AA);
	//
	//		/*
	//		//存放霍夫变换所求得的线段的点集
	//		vector<Point> points;
	//		points.push_back(Point(l[0], l[1]));
	//		points.push_back(Point(l[2], l[3]));
	//
	//		//直线拟合
	//		Vec4f fitlines = LaneFit(points);

	//		Point start_Point1(fitlines[2] - 150 * fitlines[0], fitlines[3] - 150 * fitlines[1]);
	//		Point end_Point1(fitlines[2], fitlines[3]);
	//		line(half_frame, start_Point1, end_Point1, Scalar(0, 0, 255), 2, CV_AA);
	//		*/
	//	}

	//	/*
	//	//运动目标(车辆)检测
	//	vector<Rect> moving_objs_poses;
	//	moving_objs_detector.detect(half_frame, moving_objs_poses);
	//	for (auto &pos : moving_objs_poses)
	//	{
	//		//参数：Mat(image),Rect(rectangle),Scalar(color),Thickness
	//		rectangle(half_frame, pos, Scalar(0, 255, 255), 1);
	//	}
	//	*/
	//	imshow("车道线检测+拟合+运动目标检测", half_frame);
	//	waitKey(30);
	//}
	//////////////////////////////////////////结束////////////////////////////////////////
	//waitKey();
	//return 0;
}


FuelCell (brianlball) - x86_64-MacOS-10.10-clang: OK (2335 of 2511 tests passed, 0 test warnings)

![Build Badge](http://img.shields.io/badge/build%20status-warnings-yellow.png) ![Test Badge](http://img.shields.io/badge/tests%20passed-92.99%25-yellow.png)


这里有计算sift特征地程序，能够计算出每个运动目标的sift特征；
但是稀疏编码部分还不行！


Should be `$this->repository->count()` or `$this->repository->getModel()->count()`


Seriously, the api key? 😞


sir/mam how to play this game? what i need to


This needs to be `.get()` or it won't raise. And it's returning a QuerySet.


> By wrapping the if/else in an if (on line 114), doesn't that mean that neither the success nor the failure message will be printed if the verbose arg is not passed?

Yes, because failure will print lots of other error messages anyway, so it will be obvious.

> And, isn't the request from Ben that this be enabled by default, because it is to benefit newbies who aren't familiar with UNIX?

Right, that why I mentioned adding `--quite`, I just wanted to see if the command parsing thing is working then clean things up.


//这是HoughTransform.cpp，即直线（车道线）检测程序
#include<iostream>
#include<opencv2\opencv.hpp>
#include<opencv2\imgproc\imgproc.hpp>

using namespace std;
using namespace cv;

static void image_process(Mat &fgimg)
{
	medianBlur(fgimg, fgimg, 5);
	dilate(fgimg, fgimg, Mat());
	erode(fgimg, fgimg, Mat());
}

//霍夫变换直线检测
//Vec4i:即int,4(有4个int类型的元素，即直线的两个端点的4个坐标值)
inline vector<Vec4i> HoughTransform(Mat Img)
{
	Mat grayImage;
	if (Img.channels() == 3)
	{
		cvtColor(Img, grayImage, CV_BGR2GRAY);
	}
	else
	{
		Img.copyTo(grayImage);
	}

	Mat binaryImage;
	threshold(grayImage, binaryImage, 195, 255, THRESH_BINARY_INV);

	Mat cannyImage;
	Canny(binaryImage, cannyImage, 200, 250);

	//lines容器：存放输出的直线向量，每条线用4个元素表示，即直线的两个端点的4个坐标值
	vector<Vec4i> lines;
	HoughLinesP(cannyImage, lines, 1, CV_PI / 180, 35, 20, 10);

	return lines;
}


添加会员


書き換えたコードをpushしました。
よろしくお願いします。


//这是denseSift.hpp，即用于计算车辆的sift特征的程序
/**
* @brieft extract the dense sift descriptor
*/
#include <opencv2/opencv.hpp>

class CDenseSIFT
	{
	public:
		CDenseSIFT() {}

		~CDenseSIFT() {}

		// 计算sift特征前，必须调用一次init
		void init();

		/**
		** output: siftArr
		** 行数为图片中采样点数量：81，列数为sift的维数：128
		*/
		void CalculateSiftDescriptor(cv::Mat& img, cv::Mat& siftArr);
	protected:
		void sp_find_sift_grid(cv::Mat& img, cv::Mat& siftArr);//?

		void sp_normalize_sift(cv::Mat& siftArr, double threshold = 1.0);//归一化
	private:
		cv::Mat m_weights;
		cv::Mat m_G_X, m_G_Y;
	};

static int g_maxImSize = 300;
// dense sample pixel position
static const int g_gridSpacing = 6;
static const int g_patchSize = 16;
// image filter kernel
static const double g_sigma = 0.8;

// sift descriptor extract
static const int g_num_angles = 8;
static const double g_angles[8] = { 0., 0.7854, 1.5708, 2.3562, 3.1416, 3.9270, 4.7124, 5.4978 };
static const int g_num_bins = 4;
static const int g_num_samples = g_num_bins * g_num_bins;
static const int g_alpha = 9;

static void gen_dgauss(double sigma, cv::Mat& GX, cv::Mat& GY)
{
	int f_wid = 4 * cvCeil(sigma) + 1;// cvCeil 返回不小于参数的最小整数值
	cv::Mat kernel_separate = cv::getGaussianKernel(f_wid, sigma, CV_64F);
	cv::Mat kernel = kernel_separate * kernel_separate.t();
	GX.create(kernel.size(), kernel.type());
	GY.create(kernel.size(), kernel.type());// 核矩阵是[5,5]
	//cout << kernel.size() << endl;
	for (int r = 0; r < kernel.rows; ++r)
	{  // 构建核矩阵，GX,GY
		for (int c = 0; c < kernel.cols; ++c)
		{
			if (c == 0)// 对列处理
			{
				GX.at<double>(r, c) = kernel.at<double>(r, c + 1) - kernel.at<double>(r, c);
			}
			else if (c == kernel.cols - 1)
			{
				GX.at<double>(r, c) = kernel.at<double>(r, c) - kernel.at<double>(r, c - 1);
			}
			else
			{
				GX.at<double>(r, c) = (kernel.at<double>(r, c + 1) -
					kernel.at<double>(r, c - 1)) / 2;
			}

			if (r == 0)// 对行处理
			{
				GY.at<double>(r, c) = kernel.at<double>(r + 1, c) - kernel.at<double>(r, c);
			}
			else if (r == kernel.rows - 1)
			{
				GY.at<double>(r, c) = kernel.at<double>(r, c) - kernel.at<double>(r - 1, c);
			}
			else
			{
				GY.at<double>(r, c) = (kernel.at<double>(r + 1, c) -
					kernel.at<double>(r - 1, c)) / 2;
			}
		}
	}
	GX = GX * 2 / cv::sum(cv::abs(GX))[0];// X方向上的高斯核
	GY = GY * 2 / cv::sum(cv::abs(GY))[0];// Y方向上的高斯核
}

// 每次计算的weights值都相同，此处在初始化时直接计算出weights
// 使用 [0, 1, ... , 15] 的相对像素坐标计算weights
void initWeightMatrix(cv::Mat& weights)
{
	weights.create(16, 256, CV_64F);
	cv::Mat weights_x(16, 256, CV_64F);
	cv::Mat weights_y(16, 256, CV_64F);

	double sample_x_t[16] = { 1.5, 1.5, 1.5, 1.5,
		5.5, 5.5, 5.5, 5.5,
		9.5, 9.5, 9.5, 9.5,
		13.5, 13.5, 13.5, 13.5 };
	double sample_y_t[16] = { 1.5, 5.5, 9.5, 13.5,
		1.5, 5.5, 9.5, 13.5,
		1.5, 5.5, 9.5, 13.5,
		1.5, 5.5, 9.5, 13.5 };

	double* pweight_x = (double*)weights_x.data;
	double* pweight_y = (double*)weights_y.data;
	for (int i = 0; i < 16; ++i) {
		for (int j = 0; j < 16; ++j) {
			for (int k = 0; k < 16; ++k) {
				double tmp = std::abs(j * 1.f - sample_x_t[i]) / 4;
				tmp = 1 - tmp;
				*pweight_x++ = tmp > 0 ? tmp : 0;
				tmp = std::abs(k * 1.f - sample_y_t[i]) / 4;
				tmp = 1 - tmp;
				*pweight_y++ = tmp > 0 ? tmp : 0;
			}
		}
	}
	weights = weights_x.mul(weights_y);
	//cout << weights.rows <<" "<< weights.cols << endl << endl;
}

static enum ConvolutionType
{
	/* Return the full convolution, including border */
	CONVOLUTION_FULL,
	/* Return only the part that corresponds to the original image */
	CONVOLUTION_SAME,
	/* Return only the submatrix containing elements that were not influenced by the border */
	CONVOLUTION_VALID
};
static void filter2(cv::Mat& src, cv::Mat& dst, cv::Mat& kernel, int type)
{
	cv::Mat source = src;
	//if (CONVOLUTION_FULL == type) {
	//	source = cv::Mat();
	//	const int additionalRows = kernel.rows - 1, additionalCols = kernel.cols - 1;
	//	cv::copyMakeBorder(src, source, (additionalRows + 1) / 2, additionalRows / 2,
	//		(additionalCols + 1) / 2, additionalCols / 2, cv::BORDER_CONSTANT, cv::Scalar(0));
	//}

	cv::Point anchor(kernel.cols - kernel.cols / 2 - 1, kernel.rows - kernel.rows / 2 - 1);
	int borderMode = cv::BORDER_CONSTANT;
	cv::filter2D(source, dst, CV_64F, kernel, anchor, 0, borderMode);

	//if (CONVOLUTION_VALID == type) {
	//	dst = dst.colRange((kernel.cols - 1) / 2, dst.cols - kernel.cols / 2)
	//		.rowRange((kernel.rows - 1) / 2, dst.rows - kernel.rows / 2);
	//}
}

static void magnitude(const cv::Mat& I_X, const cv::Mat& I_Y, cv::Mat& I_mag)
{
	CV_Assert(I_X.type() == CV_64F && I_X.type() == I_Y.type());

	I_mag = I_X.mul(I_X) + I_Y.mul(I_Y);
	int s = I_mag.rows * I_mag.cols;
	double* p = (double*)I_mag.data;
	for (int i = 0; i < s; ++i) {
		*p = cv::sqrt(*p);
		p++;
	}
}

static void orientation(const cv::Mat& I_X, const cv::Mat& I_Y, cv::Mat& I_theta)
{
	CV_Assert(I_X.type() == CV_64F && I_X.type() == I_Y.type());

	I_theta.create(I_X.size(), I_X.type());
	const double* pdx = (double*)I_X.data;
	const double* pdy = (double*)I_Y.data;
	double* ptheta = (double*)I_theta.data;
	for (int i = 0, s = I_X.rows * I_X.cols; i < s; ++i) {
		*ptheta++ = atan2(*pdy++, *pdx++);
	}
}

static void weightOrientation(const cv::Mat& I_theta, const cv::Mat& I_mag, cv::Mat& I_orientation)
{
	CV_Assert(I_theta.size() == I_mag.size());
	CV_Assert(I_theta.type() == CV_64F && I_theta.type() == I_mag.type());
	I_orientation.create(I_theta.size(), CV_64FC(g_num_angles));

	const double* ptheta = (double*)I_theta.data;
	const double* pmag = (double*)I_mag.data;
	double* phist = (double*)I_orientation.data;
	for (int i = 0, s = I_theta.cols * I_theta.rows; i < s; ++i) {
		for (int j = 0; j < g_num_angles; ++j) {
			double tmp = std::pow((std::cos(*ptheta - g_angles[j])), g_alpha);
			if (tmp < 0) tmp = 0;
			*phist++ = tmp * (*pmag);
		}
		ptheta++; pmag++;
	}
}

static void siftForSinglePoint(const cv::Mat& weights, const std::vector<cv::Mat>& I_orientations,
	const cv::Point& point, cv::Mat& descriptor)
{
	CV_Assert(weights.size() == cv::Size(256, 16));
	CV_Assert(descriptor.cols == 128);

	cv::Rect rect(point.x, point.y, 16, 16);
	cv::Mat descriptor_tmp(g_num_angles, g_num_samples, CV_64F);
	double* pdescriptor_tmp = (double*)descriptor_tmp.data;
	for (int i = 0; i < g_num_angles; ++i) {
		cv::Mat hist = I_orientations[i](rect).t();
		for (int r = 0; r < weights.rows; ++r) {
			double sum = 0;
			const double* phist = (double*)hist.data;
			const double* pweights = weights.ptr<double>(r);
			for (int c = 0; c < weights.cols; ++c) {
				sum += (*pweights++) * (*phist++);
			}
			*pdescriptor_tmp++ = sum;
		}
	}
	descriptor_tmp = descriptor_tmp.t();
	memcpy(descriptor.data, descriptor_tmp.data, descriptor_tmp.step * descriptor_tmp.rows);
}

/*************************** help function end *********************************/

void CDenseSIFT::init()
{
	initWeightMatrix(m_weights);
	gen_dgauss(g_sigma, m_G_X, m_G_Y);
	//cout << m_G_X << endl<< endl;
	//cout << m_G_Y << endl;
}

void CDenseSIFT::sp_find_sift_grid(cv::Mat& img, cv::Mat& siftArr)
{
	cv::Mat I;
	if (img.channels() == 3) {
		cv::cvtColor(img, I, CV_BGR2GRAY);
	}
	else {
		img.copyTo(I);
	}
	I.convertTo(I, CV_64F, 1.0 / 255);

	// opencv resize 函数不能取得与 matlab imresize 相同的结果
	// matlab imresize函数默认添加了 antialiasing 处理
	// 此处当图片尺寸但与 g_maxImSize(300）时，不处理此张图片
	/*
	if (std::max(I.rows, I.cols) > g_maxImSize) {
	double scale = g_maxImSize * 1.0 / std::max(I.rows, I.cols);
	cv::resize(I, I, cv::Size(0, 0), scale, scale, cv::INTER_CUBIC);
	}
	*/
	if (std::max(I.rows, I.cols) > g_maxImSize) return;

	cv::Mat I_X, I_Y;
	filter2(I, I_X, m_G_X, CONVOLUTION_SAME);
	filter2(I, I_Y, m_G_Y, CONVOLUTION_SAME);

	cv::Mat I_mag, I_theta;
	magnitude(I_X, I_Y, I_mag);
	orientation(I_X, I_Y, I_theta);

	cv::Mat I_orientation;
	weightOrientation(I_theta, I_mag, I_orientation);
	std::vector<cv::Mat> I_orientations;
	cv::split(I_orientation, I_orientations);

	int remX = (I.cols - g_patchSize) % g_gridSpacing;
	int offsetX = cvFloor(remX * 1.0 / 2) + 1;
	int remY = (I.rows - g_patchSize) % g_gridSpacing;
	int offsetY = cvFloor(remY * 1.0 / 2) + 1;
	int num_patches = ((I.cols - g_patchSize + 1 - offsetX) / g_gridSpacing + 1) *
		((I.rows - g_patchSize + 1 - offsetY) / g_gridSpacing + 1);
	siftArr.create(num_patches, g_num_angles * g_num_samples, CV_64F);
	num_patches = 0;
	for (int x = offsetX - 1; x <= I.cols - g_patchSize; x += g_gridSpacing) {
		for (int y = offsetY - 1; y <= I.rows - g_patchSize; y += g_gridSpacing) {
			cv::Point point(x, y);
			siftForSinglePoint(m_weights, I_orientations, point, siftArr.row(num_patches++));
		}
	}
}

void CDenseSIFT::sp_normalize_sift(cv::Mat& siftArr, double threshold)
{
	for (int r = 0; r < siftArr.rows; ++r) {
		cv::Mat row = siftArr.row(r);
		double mag = std::sqrt(cv::sum(row.mul(row))[0]);
		double* pdata = (double*)row.data;
		if (mag >= threshold) {
			for (int c = 0; c < row.cols; ++c) {
				pdata[c] /= mag;
				if (pdata[c] > 0.2) pdata[c] = 0.2;
			}
			double s = std::sqrt(cv::sum(row.mul(row))[0]);
			for (int c = 0; c < row.cols; ++c) pdata[c] /= s;
		}
		else {
			for (int c = 0; c < row.cols; ++c) {
				pdata[c] /= threshold;
				if (pdata[c] > 0.2) pdata[c] = 0.2;
			}
		}
	}
}

void CDenseSIFT::CalculateSiftDescriptor(cv::Mat& img, cv::Mat& siftArr)
{
	sp_find_sift_grid(img, siftArr);
	sp_normalize_sift(siftArr);
}


那就去掉`to reduce app bundle size`


//这是moving_objs_detect.hpp，即用于检测运动目标（车辆）的程序
#include<iostream>
#include <opencv2/opencv.hpp>
#include<vector>

using namespace std;
using namespace cv;

class MovingObjsDetector
{
public:
	MovingObjsDetector();

	~MovingObjsDetector();

	void detect(Mat &img, vector<Rect> &moving_objs_poses);

private:
	BackgroundSubtractorMOG2 fgSubtractor;

	Mat foregroundimg;
};

static void foreground_image_process(Mat &fgimg)
{
	medianBlur(fgimg, fgimg, 5);
	dilate(fgimg, fgimg, Mat());
	erode(fgimg, fgimg, Mat());
}

//Parameters:vector<vector<Point>>(contours),vector<Rect>(pos),Mat(image)
static void getObjsPos(vector<vector<Point>> &contours, vector<Rect> &objsPos, const Mat &img)
{
	objsPos.resize(0); //调用vecter成员函数resize并初始化
	for (auto &c : contours) //遍历图像
	{
		//minAreaRect:对于给定的点集返回一个轮廓的外接矩形，返回的是一个RotatedRect（旋转矩形）的类，类中包含了外接矩形的中心center、大小size以及角度angle
		//Parameters:InputArray(points)
		RotatedRect rorect = minAreaRect(c);
		float w = min(rorect.size.width, rorect.size.height);
		float h = max(rorect.size.width, rorect.size.height);
		if (h < 25.f) continue; //去除过小的矩形

		//计算点集的最外面（up-right）矩形边界
		//Parameters:InputArray(points)
		Rect rect = boundingRect(c);
		if (rect.y < img.rows / 5 || (rect.y + rect.height / 2) * 10 > img.rows * 9) continue;

		//获取图像的ROI，因为是引用，所以对ROI操作，就是对img中的rect操作了
		Mat &roi = img(rect);
		if (countNonZero(roi) * 8 < rect.area()) continue; //countNonZero:计算ROI的非零像素点数，若ROI太小，则放弃该rect，即去除过小的矩形

		objsPos.push_back(rect); //将每一个符合条件的矩形存到objsPos容器中
	}
}

MovingObjsDetector::MovingObjsDetector()
{}

MovingObjsDetector::~MovingObjsDetector()
{}

//Parameters:Mat(image), vector<Rect>(pos)
void MovingObjsDetector::detect(Mat &img, vector<Rect> &moving_objs_pos)
{
	static Mat gray_img; //静态变量
	if (img.channels() == 3) cvtColor(img, gray_img, CV_BGR2GRAY);
	else img.copyTo(gray_img);

	//高斯前景提取
	fgSubtractor(gray_img, foregroundimg);
	//imshow("高斯混合模型提取的前景", foregroundimg);

	//对前景进行形态学滤波
	foreground_image_process(foregroundimg);

	//将获得的前景赋给临时矩阵变量:contour_temp
	Mat contour_temp;
	foregroundimg.copyTo(contour_temp);
	//imshow("对前景进行形态学处理后的轮廓", contour_temp);

	//对前景二值图像提取轮廓，并且返回提取轮廓的数目
	vector<vector<Point>> contours; //定义轮廓容器，存放的是每一个轮廓的点集
	//Parameters:Mat(image),vector<vector<Point>>(contours),mode(提取模式:CV_RETR_EXTERNAL为只提取最外层的轮廓),method(逼近方法:CV_CHAIN_APPROX_NONE为将所有点由链码形式翻译为点序列形式)
	findContours(contour_temp, contours, CV_RETR_EXTERNAL, CV_CHAIN_APPROX_NONE);

	//获取（更新）运动目标位置
	getObjsPos(contours, moving_objs_pos, foregroundimg);
}