@hellais @origliante: ok with this sigle integrated webworker i managed to solve all our issues.

just as excercise i did also: https://gist.github.com/evilaliv3/060b2cc8a075f4704e32
this is smaller, works with the original openpjp.js without the patchs by @hellais but is too hackish :)
anyway also using this small one we would require the streaming functionality to be integrated in openpgp.js.

@tanx: have mercy on us! :)


(Scott Daniel) Here is an == None that got missed


(Scott Daniel) Here is a !=None that got missed


(Scott Daniel) Here are some !=None s that got missed


(Scott Daniel) Here is a != None that got missed


(Scott Daniel) Just curious:

There are several points in the code where you use the bit-wise & rather than the 'and' operator for boolean tests (also the bitwise | instead of 'or').  Is there a reason for this?  Either way works.  I was just wondering if there was a reason to use one rather than the other.


(Lynne Jones) I think there was not a good reason, and probably just forgot which one I should be using. I'll look through the code and see if I can find those places and make them self-consistent.


(Lynne Jones) Found a bunch of == and != None's that were missed, and fixed those. Also replaced & with and and | with or when comparing booleans.
Also, found that unit tests for sed and applyIGM weren't being run by scons, so added the necessary 'unittest.main()' to those unit tests, so they will run.


(Bryce Kalmbach) Feature/SIM-164 fit for magnorm in selectstarsed
* Created calcMagNorm routine. Need to create tests and add appropriate calls within select*SED routines.
* Created calcMagNorm test in testReadGalfast.py
* Added magNorm functionality in selectGalaxySED matching routines.
* Finished adding in magNorm calculation in selectStarSED. Added initBand option in calcMagNorm.


(Scott Daniel) how can this be less than zero?  You called np.abs()


develop (lefticus) - Win64-Windows-8.1-VisualStudio-14: OK (346 of 346 tests passed)

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


(Bryce Kalmbach) No, I'm finding the argument with the greatest absolute difference and then calling the actual value.


Continuation of https://github.com/markets/dotfiles/commit/06e76854e2041b3f91ee690359f7560b4df8b3eb. Use `~/.secrets` to hook Git credentials (interactive first time).


(Scott Daniel) rather than instantiating the selectGalaxySED class, could you just make calcMagNorm part of some other utility class from which selectStarSED and selectGalaxySED both inherit?


(Scott Daniel) This looks good.

I think as a next step we should write an alternate version of calcMagNorm that finds the magnorm by analytically minimizing the error function

E = \sum_i ((Norm * unnormed_flux_i - object_flux_i)/flux_error_i)^2

We can then compare the two methods and see which gives the better fits.


(Scott Daniel) ah.  right.  got it


(Scott Daniel) Feature/CATSIM-111
brings sims_photUtils into line with the feature/CATSIM-111 branch in sims_catalogs_generation

* calculatePhotometricUncertainty in Photometry.py now uses ObservationMetaData's stored value of m5
* initialize m5 in the observationMetaData in testPhotometry.py


(Scott Daniel) Bugfix/CATSIM-103 update obsMetaData
see description in identically named pull request in sims_catalogs_generation

change Variability.py to reflect new observation meta data formalism


(Simon Krughoff) Sorry it does have bandpass.


(Scott Daniel) Bugfix/SIM-1088 calcm5 bug when multiplying throughputs
Numpy range creation using the stepsize/2.0 for the last step (to make the array to end reliably at the max value specified).
Also, propagated wavelength range of bandpass into the flat sed used for calculating m5, so that the above wouldn't be an issue (if happened unexpectedly .. or if bandpass was covering non-standard range).


Were we using some other URIs other than `file://`?


(Bryce Kalmbach) Bugfix/SIM-1018 readgalfast example notebook throws
* Made copy of SED object in calcBasicColors to avoid overlap error.
* fixed problem: matchErrors was not using the same value for the minimum of distanceArray if there was a nan. Also added matchErrors to example notebook.
* Added copying of SED in calcBasicColors.
* Added copy option to calcBasicColors. Made it necessary in matchToObserved, but optional argument in matchToRestFrame. Adjusted example and added test.


(Scott Daniel) This shouldn't be necessary.  loadTotalBandpassesFromFiles calls setupPhiArray_dict()


(Scott Daniel) The environment variable SDSS_THROUGHPUTS has been removed.  You have to use

os.path.join(eups.productDir('throughtputs'),'sdss')


(Scott Daniel) You should also get rid of os.getenv in readGalfastExample.

Once you take care of that, this is ready to merge.  Michael wants to move this repo over to GitHub on Monday, so if you can handle merging this by the end of this week, that would be ideal.  Thanks.


(Scott Daniel) Feature/CATSIM-102 create ebv utils that can be accessed
This should achieve the "input an RA, Dec; get out EBV" functionality that Alex Kim wanted.  There is a related pull request on sims_coordUtils which I will also send you

* separated EBVmixin into a base class that can be accessed from anywhere and a mixin that just contains the getters; also, redesigned inputs of calculateEBV so that the user can specify their own dust maps if they want
* can now specify either glon,glat or ra,dec in calculateEBV
* added unit test just to make sure that calculateEbv runs
* calcualteEbv throws exception if you improperly specify coordinates


Line 2119 change ...apply the <from> styles... to ...apply the <form> styles...


(Lynne Jones) So wait - is it still a mixin or is it a regular class now? Or is that just a distinction in how it's used? (sorry, I'm not entirely clear on the details of mixins).


(Lynne Jones) Oh, I think we're supposed to use 'is None' and 'is not None' rather than "== None" and '!= None'.


(Lynne Jones) Okay, so here's the mixin part .. and a 'normal' (non catalogs) user would use the EBVbase above? Maybe a little additional documentation along those lines would be helpful.


(Lynne Jones) Some comments below which could be fruitfully addressed, but in general looks good!


(Scott Daniel) That is correct.  I will make it more clear.  Thanks.


(Bryce Kalmbach) Feature/CATSIM-193 write galaxy sed matching code
I made the changes that Scott proposed in the previous pull request. I also removed all calls throughout the readGalfast/ folder to photUtils.py and replaced them with Photometry.py routines. Finally, I've added examples for readGalfast in the sims_photUtils/examples folder and this part is tied to issue CATSIM-194.

* Rewrote Observed routine to have similar form to rest frame but it's still too slow.
* Sped up observed routine and added way to correct for extinction from milky way.
* Finished writing unit tests and separated out Spectrum class into file rgUtils.py
* Added line for Scons about LSST_THROUGHPUTS
* Trying to make buildbot happy, second attempt.
* Removed all calls to photUtils. Removed Spectra class in favor of just using SED. Started on some documentation.
* Changed matchToObserved structure to sort catalog by redshifts and only keep set of colors at the redshift it's currently matching.
* Changed to accept bandpass objects in selectGalaxySED.py. Also changed way to get throughput directory in testReadGalfast.py
* Amended __init__.py to account for changes
* Finished adding examples for readGalfast files. Added subset option to readGalfast.py in order to exploit ability to use same thing in selectStarSED.py. Made minor changes to selectGalaxySED.py output.


(Bryce Kalmbach) I also made some small additions to the "Catalog Simulations - code overview" confluence page for the documentation aspect of this. If you have any comments on that let me know as well.


Ok, I have merged into 4.x.x too :-)   There's a bunch of changes since 4.x.x, in 'remove-activation-conv-fc', but that branch is also kind of broken.  Probably best to develop on 4.x.x, and I can handle merging those changes into remove-activation-conv-fc.


(Scott Daniel) shouldn't this be subset = multSubset?


(Scott Daniel) shouldn't this be subset = wdSubset


(Scott Daniel) will eups.productDir('sims_sed_library') work in place of os.environ['SIMS_SED_LIBRARY_DIR']?


(Scott Daniel) This probably isn't really a performance hit, but would it seems easier to have

fileNameAsList = fileName.split('.')

and then reference the elements of fileNameAsList rather than repeatedly splitting fileName


(Scott Daniel) I am confused.  When you assemble modelColors, you first set it up as a list of lists where the inner list is a list of colors.  When you call np.transpose(modelColors) you get a numpy array in which every row is a color and every column is an object.

When you assemble matchColors, you first set it up as a lit of lists where the inner list is a list of objects.  Calling np.transpose(matchColors) should give you a numpy array in which every row is an object and every column is a color.

Is that what you want, or am I misunderstanding something?


(Bryce Kalmbach) Yes, because when I match (in lines 131-138 below), I take one of the objects I want to match to at a time (one row of matchColors) and then take each color for this object and subtract it from the value for all SED models for that particular color (one row of modelColors) and then square all of these differences and save that as distance array. Then I do it for the remaining colors and add them in to get the total difference between the object's colors and the colors of all the models and use this to find the best match.


If you have time, @LunkRat, you might check this for functionality. I wrote it up pretty fast.


If you delete the quotes, spaces won't stay and when creating the text everything will be united.


(Scott Daniel) ah.  Yes.  I see.  Sorry.


(Scott Daniel) The name of the parameter should be extCoeffs.

Also: include a note here that they default to SDSS [u,g,r,i,z] values.


(Scott Daniel) Since you have defaults set for extCoeffs, maybe we should have bandpassList default to None and have code in the method that, if bandpassList is None, will automatically load the SDSS filters from our throughputs directory.


(Scott Daniel) you refer to filterList.  I think you mean bandpassList.


:cake: I was just thinking about this last night since I was toying with Rust again.


(Scott Daniel) Can this be done with eups.productDir('sdss_throughputs')?

or os.path.join(eups.productDir('throughputs'),'sdss')

?


(Scott Daniel) check that these are still necessary (i.e. if you are able to use eups.productDir in the code that does the SED matching)


(Scott Daniel) eups.productDir ?


(Scott Daniel) again: make sure these are still necessary


(Scott Daniel) The iPython notebooks look great.  The one catch is, iPython automatically saves as you go (and output is considered part of the notebook), which means that anyone running off of a cloned repository who runs the iPython notebooks will end up making changes to the code whether or not that is what they mean to do.  Rather than force our users to be careful about not committing changes they don't mean to, I suggest that you run the iPython notebooks and then save, commit, and push them in their "just-run" state.  That way, users can't change the code unless that is what they intend to do.


(Bryce Kalmbach) Yes. Thanks.


(Bryce Kalmbach) Yes again.


(Bryce Kalmbach) Yes, just made sure it did. I will change it here and in the test.


 - __style__: [src/chaiscript_stdlib.cpp:18](../blob/86ec14c2c82145e95366b9bbd80dd9855840dedc/src/chaiscript_stdlib.cpp#L18) The function 'create_chaiscript_module_chaiscript_stdlib' is never used. (unusedFunction)
 - __style__: [src/main.cpp:169](../blob/86ec14c2c82145e95366b9bbd80dd9855840dedc/src/main.cpp#L169) The function 'get_eval_error' is never used. (unusedFunction)
 - __style__: [src/main.cpp:140](../blob/86ec14c2c82145e95366b9bbd80dd9855840dedc/src/main.cpp#L140) The function 'help' is never used. (unusedFunction)
 - __style__: [src/main.cpp:216](../blob/86ec14c2c82145e95366b9bbd80dd9855840dedc/src/main.cpp#L216) The function 'myexit' is never used. (unusedFunction)
 - __style__: [src/main.cpp:158](../blob/86ec14c2c82145e95366b9bbd80dd9855840dedc/src/main.cpp#L158) The function 'throws_exception' is never used. (unusedFunction)


(Bryce Kalmbach) Good idea. I'll add that in.


(Scott Daniel) Bugfix/CATSIM-129 cull the m flares
This is just two small changes concurrent with the culling of the mflare light curve files.  Mostly I want to make sure that there wasn't a good reason were were only using the mflare light curves that end in _1.dat

* removed code in Variability.py that meant only mflare light curve
files ending in _1.dat were ever used
(not sure why that was there in the first place)

* turned on caching in applyVariability()


(Simon Krughoff) I think this was probably left over from when we only had the _1 versions.  Good catch and thanks for fixing it.


(Simon Krughoff) good to go.


(Scott Daniel) Feature/CATSIM-130 update bounds API
See sims_catalogs_generation for description of this pull request

(note: I also cleaned up an ambiguityin Variability.py; there were two redundant microlensing routines; I fixed it so that the one just calls the other)

* fixed unittest to comport with new circ_bounds/box_bounds API
* move applyMicrolensing to be near applyMicrolens in
Variability.py
* Removed incorrect microlensing method.  Made it call the correct
method (just in case the database relies on both methods
still existing)


(Yusra AlSayyad) OK.  See the general comments in sims_catalogs_generation/pull-requests/13/


(Scott Daniel) Feature/CATSIM-151 split astrometry and photometry
This pull request is the first in a series that will alter the general philosophy behind the Photometry and Astrometry mixins.  When they were written, the mixins were designed to operate solely within the context of an InstanceCatalog.  Every method that did anything interesting was a getter for a database column.  We are now moving to a model where there are, whenever possible, two methods: one method that does the work, but which can be called from outside an InstanceCatalog if so desired, and a getter method that calls the first method.

This pull request touches
sims_catalogs_measures
sims_catUtils
sims_coordUtils
sims_photUtils

* added unit test for stand-alone calculate_magnitudes
* updated docstring on loadBandPassesFromFiles
* loadBandPassesFromFiles now calls setupPhiArray_dict automatically
* changed PhotometryGalaxies.calculate_magnitudes API to function outside of
an InstanceCatalog
* test exceptions in PhotometryGalaxies.calculate_magnitudes()
* test more exceptions
* change default magNorm in calculate_component_magnitudes
* test for more problematic uses
* test the output of PhotometryGalaxies.calculate_magnitudes() when it is
called correctly
* test that magnitudes are correctly added


Did you mean the following?
Line 2119: ...apply the **from** styles...
or did you mean to type
...apply the **form** styles...


(Lynne Jones) Would it make sense to make this be a kwarg?


(Lynne Jones) If the purpose of this refactor was to make it so that these methods could be called from outside instance catalogs, it's not really obvious to me how this would work. Is the idea that you'd still have some at least of these values, so that you were essentially calling this method to calculate galaxy magnitudes from data created by a database query? I guess I understand that.
Could this method be called calculate_galaxy_magnitudes or something more specific? (presumably you might also want a calculate_stellar_magnitudes at some point too).


(Lynne Jones) Should these (magNorm and sedNames) be args instead of kwargs, if they're required?


(Scott Daniel) I wanted to re-design this method so that you could call it "by hand," passing in all of the data (i.e. SED names, magNorms, and Av for each relevant component).

I was inspired by our hack day back in November during which Rahul and I were trying to access some of the Photometry methods in the context of MAF code.  It wasn't very easy, because most of the code was written assuming it would only be called from an InstanceCatalog (i.e. there were a bunch of self.column_by_name() calls lying around where they did not have to be).

I'm not 100% sure what the use cases will be.  I just figured this would give people options.


(Lynne Jones) Sorry - I release that this is in a photometry mixin where the root of the class includes "Galaxies", so I take back the 'calculate_galaxy_magnitudes' naming suggestion.


hpwh_residential (nmerket) - x86_64-MacOS-10.9-clang: Tests Failed

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


(Lynne Jones) Got it.


(Scott Daniel) not of get_all_mags().  get_all_mags() is a getter that is meant to be called by an InstanceCatalog.  It can only take self as an argument.

If someone were to do this outside of an InstanceCatalog, they would need to call loadBandPassesFromFiles() passing in bandPassNames, bandPassRoot, and bandPassDir by hand (those last two being optional).


(Lynne Jones) Ah, right, it's a getter. Um, but does that mean bandpassNames should be a self argument, set/saved in loadBandpasssesFromFiles?


(Scott Daniel) I personally like kwargs because it relieves the user of having to remember whether sedNames comes before magNorm or vice-versa.

It's possible this is laziness on my part.  Are args more computationally efficient than kwargs?


(Scott Daniel) ultimately it is, but doing it this way makes it easy(er) for users to write their own getters for non-LSST bandpasses.

see exampleSDSScatalog.py in sims_catUtils/examples/


(Lynne Jones) Ah, never mind. I see .. if someone has done this by hand, they'll never use that info but would instead have self.BandpassList set. I guess, for readability, you could swap the bandpassNames as a default kwarg for loadBandpassesFromFiles, instead of making it an argument there? I think that's what most people would do anyway.


(Scott Daniel) sure.  Makes sense.


(Lynne Jones) That I don't know, and I see your point about remembering which comes first. I think as a user though if you specify 'magNorm=X' and 'sedNames=Y', then it doesn't matter which way around you do things (!what! I was surprised this worked).
>>> def testargs(a, b, c):
...     print "a=", a
...     print "b=", b
...     print "c=", c
...
>>> testargs(1, 2, 3)
a= 1
b= 2
c= 3
>>> testargs(a=1, c=3, b=2)
a= 1
b= 2
c= 3


(Scott Daniel) Python never ceases to baffle/amaze me.  Cool.  I can make everything an arg that is required.


(Lynne Jones) One of the unit tests (testPhotometry) fails on lsstsw build. I think it's a case-sensitive filename issue.
/lsst/home/lsstsw/stack/Linux64/sims_sed_library/2014.10.06/galaxySED/Const.80E07.02z.spec.gz should have a capital Z before .spec.gz.


(Lynne Jones) Here's the problem with the unit test, I believe.


(Scott Daniel) Yeah.  That is the bug.  I'll fix it.  Thanks for running the lsstsw build (it's a little alarming that OSX lets that pass, but oh well)


(Lynne Jones) I was just trying to be lazy and avoid checking it out on my own system :)


(Scott Daniel) I believe I have addressed everything we discussed as of 5:30pm Tuesday.

I left the arguments to PhotometryGalaxies.calculate_magnitudes() as kwargs because everything is optional (i.e. it is legal to have galaxies with a bulge but not disk or vice-versa)


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.357](http://teamcity.monogame.net/viewLog.html?buildId=6406&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 484, ignored: 6 Build time: 00:14:39


(Bryce Kalmbach) Feature/SIM-1038 adjust selectstarsed.py selectgalaxysed.py
Made catRA, catDEC optional. Added ability to accept objects with missing data in some passbands. Added matchError output (Mean Squared Error on SED match).
Adjusted to take in incomplete data (nan). After discussion returned dereddening default to True.
Created counter in selectStarSED for object without enough information to match.
Did same in selectGalaxySED.py
Added Error Output for matching
Added unit tests for error counting. This found a major bug in selectGalaxySED.py in matchToO...


(Scott Daniel) I'm not sure what "Be aware, this starts at 0, but is initialized to 1..." means.  The default value for initBand is 0 in the constructor.

On a related note: you should add something here indicating that, if filtRange is not None, initband gets replaced with filtRange[0]


(Scott Daniel) specify that filtRange is a list of indices denoting the filters to be used (as opposed to, for example, a list like ['lsst_u', 'lsst_r', 'lsst_i'])


(Scott Daniel) I assume this line is for debugging purposes?  You should remove it now that everything passes.


(Scott Daniel) Should it throw an exception if reddening is set to True but catRA and catDec are still None?


(Scott Daniel) Again: should there be an exception of reddening is True but catRA and catDec are None?


86019526_IgNullChoice (evanweaver) - x86_64-MacOS-10.9-clang: Build Failed

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


(Scott Daniel) If you do, add a unit test to verify that an exception does get thrown when it should.


(Scott Daniel) Feature/CATSIM-152 unify photutils.py and photometry.py
removed photUtils.py; it was redundant with Photometry.py


(Lynne Jones) Totally agree.


(Simon Krughoff) Feature/CATSIM-33 database unit tests
* changed example_faststars.py so that it reflect directory structure where star SEDs are stored
* changed example_faststars.py so that it inherits from the photutils package
* prep for tagging
* Repo with only the SED examples
* Moved SED examples from measures
* updated test to not use UW server.  Modified variability to get bandpass name form ObservationMetaData object.
* removed reference to catUtils
* updated photometry test to fail if no data are returned


(Scott Daniel) When I run testPhotometry.py, the output testGalaxiesOutput.txt outputs a single galaxy with nan's and None's for all of the calculated magnitudes (uRecalc, uRecalc_var, uBulge, etc.).  Is this expected?


(Scott Daniel) ah.  I see.  The testGalaxies data base does not contain SED filenames.  So, yes, this is what should happen


(Simon Krughoff) Actually, I am trying to use a flat sed.  I know the redshift is too large for the flat SED sometimes, but it should produce some reasonable magnitudes.


(Simon Krughoff) Turns out that this is a change that Lynne made recently.  We'll have to extend the flat spectrum to get mags out.  I'll file an issue.  I will also increase the number of objects in the test database so that there are more objects in the test output.


(Peter Yoachim) Where's sims_sed_library hiding?


(Simon Krughoff) It's here: https://dev.lsstcorp.org/cgit/LSST/sims/sims_sed_library.git/

We haven't moved it over to stash yet because it is too big.


(Lynne Jones) Can you move the runBandpass*py things out of python/lsst/sims/photUtils/ and into examples? (they won't work there, but I can fix the import statements so they will). They aren't classes that need to be in the base set of classes, but they are things that we need to have somewhere in git (doing useful things for science evaluation) and in the examples directory seems as good as any.


(Lynne Jones) Palpy is imported into python/lsst/sims/photUtils/photUtils.py but is not actually used, and is not one of the required packages in the table file. Suggest removing the import palpy statement from python/lsst/sims/photUtils/photUtils.py.


lol


(Simon Krughoff) Done.


(Bryce Kalmbach) Feature/CATSIM-121 add alex abate s igm code into
* Added Lookup Table. Separate files for Mean and Variance.
* Converted Lookup Tables to Nanometers
* Fixed Mean Lookup Tables to include mean and not variance. Also add first draft of applyIGM class.
* Added unittests and took out extra print commands from apply IGM
* Removed Lookup Tables from this folder to be stored in sims_sed_library. Redefined applyIGM so that it can accept other lookup tables that user may want as long as it follows the same naming convention. Modified test to test new loadTables method.
* "Removed Lookup Tables from repo."
* Made changes according to Scott's review


(Bryce Kalmbach) I'm pretty sure this is what you recommended in your review of the previous pull request. If it's not let me know and if you're in tomorrow we can talk about it.


(Scott Daniel) Very close.  The initializeIGM method is good.  However, we need for there to not be an __init__() method in this class.  The reason for this is as follows.  If this becomes a proper mixin, we will use it like this:

class myCatalogClass(InstanceCatalog, PhotometryGalaxies, AstrometryGalaxies, ApplyIGM)

Because of python's method resolution order, if this happens, then, when we instantiate myCatalogClass, python will call the __init__() in ApplyIGM, but no the __init__() in InstanceCatalog.  There is a way around this using the python built-in method super().  However, we don't want to have to make every new class we write call super().  Fortunately, we can set the variables IGMisInitialized and tablesPresent outside of any method, i.e.

class Apply IGM
    IGMisInitialized = False
    tablesPreset = False

    def initializeIGM()....

This will achieve the same end as the __init__() method you wrote without running afoul of python's method resolution order.

I made the change already and pushed it onto this branch (I hope you don't mind).  Pull down my changes and see what I did.

I also renamed the class to ApplyIGM (apparently there is a convention in which we want class names to start with capital letters; I only just learned this myself).

This is ready to merge.  You should run a build bot test, though, just to make sure we haven't broken anything.  I will forward you an email expalining how to do that.

Feel free to stop by if you want to talk about any of this.


(Bryce Kalmbach) Hi Scott,

I ran the bot test and it failed because testPhotometry.py is failing. We didn't touch that, so I'm guessing that this is a problem that came from another source?


(Scott Daniel) I think the problem is that some unrelated code was changed between the time that you made this branch and now.

Do a

git rebase master

that should bring your branch in sync with all unrelated master changes (it will ask you to resolve an conflicts, but there shouldn't be any).  After that is done, push your branch and try running buildbot again.


(Scott Daniel) Feature/SIM-136 photometric uncertainties
In this branch, I implement a more accurate method to calculate magnitude uncertainties in photometric catalogs.

In addition to adding code to the photometry mixins, this involved re-factoring some of the code in Sed.py and Bandpass.py so that it could be called in different contexts to calculate photometric uncertainty.

The basic design is that we read in m5 from ObservationMetaData, use that to calculate the gamma parameter from equation (5) of arXive:0805.2366, and then use that gamma parameter to calculate the uncertainty in magnitude.

* wrote calculatePhotometricUncertaintyFromColumnNames
stars and galaxies use that method now
* variability getters now use the new formalism
* deleted old photometric uncertainty routines
* made extra parameter dependencies in calcGamma more explicit from
Photometry mixins
* removed unneeded variable
* renamed loadTotalBandPassesFromFiles to
loadTotalBandpassesFromFiles
* changed all instances of bandPass to bandpass
* documented changes associated with this branch
* more documentation
* documented new unit tests


(Lynne Jones) Bleeeh, I don't like this whole method, I'm sorry.
It's not the right way to determine the sky background and it will (or should) go away once Peter's sky brightness code is around. I worry that by putting this here we will discourage adoption of the proper sky brightness code. And it doesn't fit with Bandpass, either.
Can this code not be turned into a utility or method somewhere else where the scaled sky sed is being used?


(Lynne Jones) Plus, shouldn't it actually return skysed, if you want the user to have the scaled version? Without returning it, you're relying on python to pass the Sed object by reference, right? Is that the 'right' thing to do?


(Lynne Jones) Not quite done going through this yet (ak, sorry!) but so far so good except for 'setM5' method, which I would really like to go elsewhere.


(Scott Daniel) Do we know what the timeframe of Peter's sky brightness code is?  Andy has wanted to have something resembling realistic photometric errors in CatSim for a while.  Absent Peter's code (and given that CatSim and OpSim don't define m5 the same way), I think something like this is the best workaround.  I'm perfectly fine deleting this method once Peter's code comes on-line.  I think that Andy is eager to simulate realistic images (with realistic noise) in GalSim.


(Lynne Jones) I don't know exactly, but I guess if Andy needs something right away, creating this method is probably best for now.
Reflecting on this further though, I think what might be useful is to add some explanatory documentation about the relationship between setM5 and calcM5 (in the docstring for each method. Something along the lines of
(for setM5)
"The 5-sigma limiting magnitude (m5) for an observation is determined by a combination of the telescope and camera parameters (such as diameter of the mirrors and the readnoise) together with the sky background. This method (setM5) scales a provided sky background Sed so that an observation would have a target m5 value, for the provided hardware parameters. Using the resulting Sed in the 'calcM5' method will return this target value for m5."
(for calcM5)
"The 5-sigma limiting magnitude (m5) for an observation is determined by a combination of the telescope and camera parameters (such as diameter of the mirrors and the readnoise) together with the sky background. This method (calcM5) calculates the expected m5 value for an observation given a sky background Sed and hardware parameters."

I know what you have is essentially similar to this, but it's not as straightforward and I think (particularly for the engineering teams) the name "setM5" could be confusing, as it was to me. Somehow 'setM5' seems to suggest that the bandpass itself is altered somehow, but it's not (and indeed, since nothing is returned, it may not entirely obvious what has been changed). I hope being more explicit in the docstrings will help.


(Lynne Jones) Is there an advantage to making these parameters above be class variables rather than instance variables? (for my own edification)


(Lynne Jones) I mean, if you wanted to calculate SDSS magnitudes and LSST magnitudes at the same time using Photometry.py, you couldn't, could you?


(Scott Daniel) Yes, you could (and there is an example script for calculating SDSS magnitudes in sims_catUtils).  Basically, these are class variables because, since this is a mixin class, we don't want to have to call `__init__()` (more specifically: we want to call `InstanceCatalog.__init__()` and we don't want to have to use `Super` in this class).

I have attached a test script that (in my mind) proves that we don't have to worry about different instances stepping on one another when setting these variables
[testClassVar.py](https://stash.lsstcorp.org/projects/SIM/repos/sims_photutils/attachments/b7c57bd96d/testClassVar.py)


(Scott Daniel) Agreed.  I will change it as we discussed.


(Scott Daniel) Feature/CATSIM-30 profile the photometry generation
* tried to speed up loadSeds(); for some reason, I am changing the output
* some sloppy hacks that have restored the code to its old state
* I had been mishandling the names of Sed files; that is fixed; we now have a factor of 3 speed up when run on catalogs of stars; however, the code does not run on galaxies for some reason; I will investigate that
* ah... I was trying to normalize Sed's that had been set to None; fixed that
* removed needless diagnostic code
* can save around 10 seconds out of 40 total when doing galaxies by only calling setupCCMab once for each unique wavelen array
* added comment
* refactored calculatePhotometricUncertainty and calculatePhotometricUncertaintyFromColumn to avoid confusing dict and list interfaces
* a bunch of blank lines... sorry
* added some clarifying comments


(Simon Krughoff) What do we do if the cached SEDs are larger than the memory of the machine?  We have been caching SEDs in an ad hoc way when we write a script, but I wonder if we need a better way if the mechanism is hidden.


(Simon Krughoff) @danielsf and I talked about this yesterday and decided that it's not the mixins job to manage memory.  It should be taken care of by the chunking mechanism.  We just need to make sure the caches are cleared after each chunk.


Can we remove the $ export mesos_master a few lines above?


(Simon Krughoff) You could do the above outside the loop and not check if sedName == "None" every time.  This would get rid of the else and simplify things in this loop slightly at the expense of always having and empty sed even if there is no "None" sedName.


(Simon Krughoff) I wonder if resample_same should default to True since.  It is obviously more overhead, but not doing it can lead to hard to track down bugs.  The reliance of the photometry code on side effects like this is one thing I'd like to think about in the redesign.


(Simon Krughoff) Is it possible to write a minimal how to reproduce and file an issue on this?


(Scott Daniel) I'm writing this down so it exists somewhere in the system.  I looked more closely at Lynne's documentation for the Sed class.  Any time you do anything to flambda, fnu gets set to None.  This is to prevent the two getting out of synch (flambda getting renormalized without fnu, etc.).


(Scott Daniel) Again, just replying for the sake of the record: At least in this context, the Sed's all end up getting resampled onto the wavelength grid of the bandpasses, so the initial resample will just get overwritten, unless we are clever enough to already know the wavelength grid of the bandpasses when we call loadSeds().  Are there specific bugs you are thinking of?


(Simon Krughoff) I wish I could remember exactly, but it's something like this.  The agn is on a different grid than the bulge and disk and if you add them all up to get a composite magnitude without explicitly resampling the agn to the bulge grid you get the wrong answer...  It's something like that, but now that I think about it, this doesn't help that anyway.  False it is!


(Scott Daniel) Feature/CATSIM-78 accept sdss filters in photutils
Hi Simon,

This isn't anything that was formally talked about in JIRA. It came out of Andy's attempt to simulate HST photometry for Julianne. I think I have made the Photometry.py API cleaner. At the very least, it is easier to write customized getters that accept different bandpasses (you can see this in get_all_mags and get_magnitudes in Photometry.py; also in cartoonPhotometryStars and cartoonPhotometryGalaxies in testPhotometry.py)

I wrote a unit test to verify that the getters look where they are told for alternate bandpass files. Note that this has slowed down testPhotometry.py. It takes about three minutes to run, now.

If you have time, I thought this might be worth merging into master. Or I can just keep what I did and we can make it part of the larger re-factor when we get around to that

-- Scott

* test of alternate bandpasses succeeds
* renamed unittest of alternate bandpasses to be a little more descriptive
* something is wrong; the test should be failing
* need to write the catalogs to have python call the getters
* simplified alternateBandpass unit tests
* added comments to the alternate bandpass tests in testPhotometry.py
* added comments to other parts of the testPhotometry.py
* cleaned up Photometry.py
* added comment to generate_photometry_test_data.cpp
* reorganized Photometry.py so that galaxy photometry getters are at the end of PhotometryGalaxies mixin


(Simon Krughoff) Sorry to take so long getting to this.  I'm going hold of on this for a bit longer since it seems like it will be a tricky merge and the other code improvements seem more important in the short term.  Is that o.k?


(Scott Daniel) yeah.  We shouldn't try to merge this until after the re-organization has been merged


(Scott Daniel) I have reconciled this code with the catSim reorganization and moved the SDSS getters into catUtils (you should have received a separate pull request for that branch).  This pull request is ready to be reconsidered.


(Scott Daniel) Hi Simon.  Do you think you will get to this review in the next few days?  The changes made here will influence how I write the documentation for the photometry examples in CATSIM-104


(Simon Krughoff) Is this some sort of bad value you expect to get?  Maybe it's hardcoded in the databases.  If possible, I'd much prefer making this setable (but maybe default it to something like -999).


(Simon Krughoff) I'm not sure how much we should bake in that the band passes we deal with are in files.  I can imaging creating band pass objects from simple models and it would be a pain to be required to write them down on disk before I can use them.

I like the loadBandPasses convenience function.  Can we call that outside the methods that do the magnitude calculation and pass bandpass objects rather than passing paths to bandpasses and loading inside this method?


(Simon Krughoff) I'd like the failure value to be setable.  It would also be nice if it were non-numeric since it's easy to confuse numeric bad values with good values.  Is that an issue?


(Simon Krughoff) Why can't you do:
for bandPass in bandPassList
?

It's a little cleaner and easier to read.


(Simon Krughoff) I'm a little confused about why there is mention of specific band passes in these classes.  Would it make sense to move LSST specific photometry routines into catUtils, or do they need to be here for some reason?


thanks @erickrdch ! i'll test out 1.2 later -- don't anticipate any other issues. :+1:


(Simon Krughoff) Again here.  I think you can do:
for bandPass in bandPassList:


(Simon Krughoff) In general this all looks fine.  I'm not going to approve it right at the moment because I would like to get a sense for how hard it would be to allow the magnitude getters to take bandpass objects rather than constructing them internally.


all tests pass:
success: http://buildbot.bos1/builders/test-riak_kv/builds/2008


Odd, thanks for fixing that!


develop (lefticus) - x86_64-Linux-Ubuntu-14.04-clang-3.5-AddressSanitizer: OK (346 of 346 tests passed)

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


@jahirfiquitiva oh okay, you can put   where you want spaces to stay.


I'll do it actually


Hello


develop (lefticus) - i386-Windows-8.1-VisualStudio-12: OK (345 of 346 tests passed)

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


aha looks like someone kind submitted a PR so I accepted it ;)


(Scott Daniel) I changed the API here so that magDict is now a dict of lists, so I do not thing for bandPass in bandPassList will work.  I did, however, replace this while loop with a more straightforward for loop


(Scott Daniel) The reason to have these in photUtils (I suspect) is so that users who want to calculate LSST magnitudes can just include the relevant mixin and be done with it.  Alternatively, we could create LSSTPhotometry mixins in sims_catUtils that inherit from these mixins and include the getters.  That might be best done as a separate JIRA issue.


However, you should not have strings that get combined. You should have string arguments, since different languages order sentences differently, especially for right to left languages. The way you set it up is not good practice for Android dev.


(Scott Daniel) see above (I replaced it with a for loop)


(Scott Daniel) I set failure = None.  Do you still want it to be user-setable?


(Scott Daniel) see overview comment


(Scott Daniel) I re-worked the API.  The Photometry mixins have global variables self.bandPassList (which is a list of bandPass object); self.phiArray (which is an array of response curves for the bandPasses in self.bandPassList); self.waveLenStep (which controls the grid in self.phiArray).  Each getter must now, somehow, set self.bandPassList and then call self.setupPhiArray_dict().  The rest of the infrastructure reads in the bandPasses from self.bandPassList.  This way, we can load bandPasses however we want.  The method self.loadBandPassesFromFiles allows the user to load them from files saved to disk.

(This means I had to rework the examples in the sims_catUtils branch, so you should look at that, too)


Pull request accepted!

We would like all our documentation to be helpful!  If you have any suggestions or comments about what was missing or confusing that you would of found helpful we'd really appreciate them!  If you scroll to the bottom of the left hand pane at http://docs.aws.amazon.com/mobile/sdkforandroid/developerguide/kinesis.html  There is a Feedback button  you can use to help us improve the Kinesis guide for yourself and others!

Thanks,
Weston


Ok, I see. May be thinking in something else later. Thanks for everything you're working on.


Can probably eliminate this by constructing it in nextChunk(), I believe that's the only place it's used


(Scott Daniel) removed the mm>-990.0 value; it now just looks for None (since failure=None above)


(Simon Krughoff) Why not make this the default instead of interpreting None?


You're welcome, I'm working on importing Moonshine's wallpaper viewer too


(Simon Krughoff) O.K. can you file an issue for this.


(Simon Krughoff) I'm sorry, I don't think I was clear in my earlier comment.  I was suggesting sending a list of Bandpass objects instead of a list of bandpass names.  Does that make sense?


(Simon Krughoff) I'm confused here.  Isn't it setupPhiArray's job to set this?  Am I missing something about how phiArray is supposed to work?


(Simon Krughoff) Sorry to take so long.  I've made some comments.  The thing is whether the magnitude calculation takes the bandpass objects (I'm not sure that makes sense but is what I originally suggested) or whether the photometry object contains the bandpass objects in a member variable.


(Scott Daniel) The way the new API works, self.bandPassList needs to be set directly by the getter.  This can be done in several ways.  One of them is to call loadBandPassesFromFiles, but it is also possible that the user will want to write a getter that generates the bandPasses in situ (or loads them from somewhere outside of the LSST framework).  In that case, the getter will also need to call setupPhiArray_dict() to make sure that self.phiArray and self.waveLenStep are synced with the new bandPass.  loadBandPassesFromFiles sets self.phiArray and self.waveLenStep to None so that the user is forced to re-sync self.phiArray and self.waveLenStep every time self.bandPassList changes (this guards against calculating photometry using one set of bandpasses when you think you are using another set of bandpasses).


(Scott Daniel) The way Sed is written, the method to calculate many magnitudes at once accepts an array of phi values rather than a list of bandPasses.  I figured it would make things more streamlined if we stored the phiArray (and bandPassList) as a member variable, so we would just calculate it once, when we loaded the bandPasses, rather than having to re-calculate it (or check whether or not it needs to be recalculated) every time we call calculate_magnitudes.


(Scott Daniel) I mentioned this below: but the trick is that the Sed method to caclulate many magnitudes at once accepts an array of phi values rather than a list of bandPasses.  The member variables in Photometry.py are there so that the code just calculates phi once for all and then proceeds with the magnitude calculations (until the bandPassList changes)


(Scott Daniel) Bugfix/SIM-969 fix magnorm precision
Hi Bryce,

Russell observed an intermittent unit test failure in the new magNorm fitting code.  Simon and I think that it is due to floating point precision rounding errors.  This ought to fix it.

* made sure that numpy.sum works on floats in rgUtils.py
* cleaned up whitespace


(Rahul Biswas) Feature/SIM-923 add manyfluxcalc method to sims photutils.sed.sed
* Sed.py: Added method manyFluxCalc to calculate fluxes
* Fixed bug in getSED_fnu()
* Sed.py: Rewrote manyMagCalc method to use the fluxes calculated from
manyFluxCalc. This means that tests for manyMagCalc now apply to
manyFluxCalc too.


(Scott Daniel) can you copy these warnings from manyMagCalc

Use setupPhiArray first, and note that Sed.manyMagCalc *assumes*
phiArray has the same wavelength grid as the Sed, and that fnu has already been calculated for Sed.
These assumptions are to avoid error checking within this function (for speed), but could lead
to errors if method is used incorrectly.

and put them here?


(Scott Daniel) put a blank line between the new function definition and the end of the previous function


(Scott Daniel) remove this comment.  I don't know why it was in the original code.  That is not what is happening here (phi is assumed to already be calculated and sampled on the correct wavelength grid)


(Rahul Biswas) True, Done


Also, this really needs a longer comment to explain
- why the expiry is started on the first ping
- why sync.Once is used


(Rahul Biswas) In fact, I think we are probably supposed to put two between the end of a function and the next.


(Bryce Kalmbach) Feature/SIM-967 rework selectstarsed and readgalfast
* Started rearranging unit tests.
* Finished unit tests.
* Fixed Documentation, but noticed readGalfast is slow. Need to fix that.
* Started rewriting readGalfast to take batches.
* readGalfast now reads in batches to take advantage of list capability of selectStarSED
* Added gzip output capability.
* Adjusted for cases when chunkSize is 1.
* Removed whitespace.
* Corrected Documentation.
* Fixed readGalfast unit tests to work if there are 0 of either H or HE white dwarfs in test folders.


develop (lefticus) - x86_64-Linux-Ubuntu-14.04-clang-3.5-ThreadSanitizer: OK (346 of 346 tests passed)

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


(Bryce Kalmbach) @danielsf
I had a couple of goals here:
1) Move all loaders to rgUtils.py and move them into specific classes for stars and galaxies. I followed the format I observed in Photometry.py.
2) Redesign selectStarSED so that it was more like selectGalaxySED and could take user input as Bandpasses, this necessitated some change to readGalfast.py
3) Since redesigning selectStarSED would create the ability to load in arrays of magnitudes rather than one at a time, I decided to include changes in readGalfast.py that would take chunks of the input files instead of constant i/o in order to hopefully speed things up.

Things to look ahead still:
I need to speed up calcMagNorm. Investigating the alternate method of calculating it you suggested might help.


(Scott Daniel) for simplicity, can you do this as

for kNum, kuruczSED in enumerate(kuruczList):


(Scott Daniel) again: use enumerate (unless there is a specific reason you didn't)


This seems to be an unused import?


Travis should complain that you didn't document this new item. Usually we put new args last in the list, but this one is so far deep in the list I think it's okay in this instance.


(Scott Daniel) enumerate


(Scott Daniel) add a comment indicating where these numbers came from (i.e. a journal reference), so that future developers are not confused when they see this


(Scott Daniel) clear out the white space in these two blank lines


Todavía se me fueron algunas líneas >80, perdón. No estoy segura todavía porque pasa eso:
36
-espacio-
37

Gracias por el feedback!


(Scott Daniel) Can you include a comment explaining where the specific values governing these population cuts come from?


@mark-friedman Also, I was wondering if you could help me out some, I'm having just as much trouble with making the generic event block working as I did with the multi-generic block (and I don't have much more time. I'm working on App Inventor through Open Academy / an academic class, and my term is ending at the end of the week. Regardless of that, I do want to finish this feature).

Basically, what it seems to me is that top level blocks handled using define-syntax blocks (such as define-event). However, it seems that non top level blocks are handled with normal define functions (get-property, set-and-coerce-property!, etc). For this reason, I decided to create this function that should basically call the define-event-helper and register the event. I think this all I will need to do (besides unregister the old event). However, as in the past, I really can't figure out syntax to make this work. Could you take a look a this?


(Scott Daniel) This is my own preference, but could you include the journal name, volume, page number, and year so that its easy to find it again if we need to?


(Scott Daniel) Why can't you feed specObj directly into PhotometryBase?


blerg!


(Scott Daniel) again, include journal title, volume number, and page number for completeness


(Scott Daniel) space between param and [out]


(Scott Daniel) Are you sure this works?  My impression of how an outer product works is that the outer product of an an n-vector with an m-vector gives an n-by-m matrix.  Just multiplying two numpy vectors should give you what you want, i.e.

x * y = numpy.array([x0*y0, x1*y1, x2*y2,...])


(Scott Daniel) can you use eups.productDir('sims_sed_library')?


(Scott Daniel) Need to include a docstring for the class


:hankey:


(Scott Daniel) "can be loaded if a list of filenames of only seds wanted in the folder is provided" is a little awkward.  Try re-wording it.


(Scott Daniel) again: re-word


The indentation of this comment is inconsistent; probably best not to add this line at all?


(Scott Daniel) class needs docstring


(Scott Daniel) same awkward wording


develop (lefticus) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (346 of 346 tests passed)

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


Add option  sms plizzzzzzz


(Scott Daniel) class needs a docstring


:cake:


(Scott Daniel) I think 'galaxy catalog' means a catalog of galaxies.  Should this stay 'catalog of stars'?


(Scott Daniel) This SED gives testMags = [0, 0, 0, 0, 0, 0]
maybe choose an actual SED from sims_sed_library just in case something is wrong in calcBasicColors


(Scott Daniel) make sure every individual unit test has a docstring that explains what it is testing


(Scott Daniel) You are passing in the same bandpasses that the code itself loads a defaults, true?  Can you test on something different (i.e. the LSST bandpasses) to make sure that the default gets overridden correctly?

Can you do the same in testMatchToObserved (I know that code is not a part of this pull request, but I just thought of it)?


(Scott Daniel) What is your timeframe for merging this?  I ask because I am close to merging a branch that is going to make a bunch of small, annoying changes (for example, I finally learned how to spell and replaced all of the instances of bandPass with bandpass, etc.)

I'm willing to do the work of fixing up the readGalfast code to reflect that, but that's going to necessitate you merging in the next few days.  Sorry for the inconvenience.


@jakemmarsh I've been out of the loop for a bit, and am doing some catching-up. Is there a reason why you reverted this, and moved away from partialify? I browsed through the issues, but didn't see anything to explain.


I'm awesome at vim. :D.


Thanks for the PR. `windows.h` is a quite a mess, but I don't think that C++ Format should unconditionally define global macros that can affect it. The reason is that such macros can break other library's or user code when `windows.h` is included elsewhere. I think it should be up to the user to decide whether these macros are defined or not and they can be defined before including `format.h` or on a project level.


develop (lefticus) - x86_64-Linux-Ubuntu-14.04-gcc-4.6: OK (346 of 346 tests passed)

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


develop (lefticus) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.67: OK (0 of 0 tests passed)

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


By the way, do we need to call loadLastIndex() in ApplySnapshot()? I think we should refactor what's done in NewRange() and ApplySnapshot() so there's shared code. I've already noticed two instances where the right thing is done at startup but not when the snapshot is applied.


Pass


There is something wrong.


Vete a la verga we D:


smaller_make_shared (lefticus) - x86_64-Linux-Ubuntu-14.04-clang-3.5: OK (346 of 346 tests passed)

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


Ah-ha, the extra logic of ByteArrayWritableChannel is that it has a fixed-size maximum, which is what is complicating this code (also I think it breaks this part).

Perhaps we could just sub in a `ByteBuf outputBuffer` which we `buf.readBytes(outputBuffer)` and `Channels.newChannel(new ByteBufOutputStream(outputBuffer))`? The main goal here is simplicity and reducing number of necessary abstractions. If it is not that simple, we can just keep your original solution of `ByteArrayWritableChannel`, but documentation should be added about its semantics of fixed-size buffering.


PacMan prep project for intro to JS/HTML/CSS


Thanks for bringing this up.

I had aimed to make as simple of an interface as is possible. For example, when calling Go's SSH functions, you can also provide stdin, as well as pipes for input and output, but I didn't add these to our utility function.

However, I see that I made it too simple. Separating the error code from an SSH error is useful to have.

I implemented this via another returned value, `code`, and added tests. Let me know whether this looks OK. (not yet pushed)


I've updated the tests to check bout stdout and stderr. (not yet pushed)


Wikipedia has a good list of interesting "programming" "languages":
http://en.wikipedia.org/wiki/Esoteric_programming_language

On Mon, Apr 27, 2015 at 9:14 AM, Jamie Smith <notifications@github.com>
wrote:

> Actually there is:
> http://search.cpan.org/~mob/Acme-AsciiArtinator-0.04/lib/Acme/AsciiArtinator.pm
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/Team3128/frc-java-3128/commit/c0a9c6d7bf861f1c1e91a5dabb8d49a729c611d5#commitcomment-10919564>
> .
>


smaller_make_shared (lefticus) - x86_64-Linux-Ubuntu-14.04-clang-3.5-LibC++: OK (345 of 346 tests passed)

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


Forgot to note that some of the more random looking adjustments were simply cleaning up formatting.


Sounds like a great decision, IMO.  I'm only vaguely familiar with Forth, but there's enough documentation and reference implementations to hopefully make it a much easier task to tackle.

Though IMO, a general-purpose project like that seems like the kind of thing where outside contributors could actually be helpful instead of just a burden.  Might be worth trolling vbForums to see if any old VB6 guys could pitch in...?


hahaha no le edite!


rax retry tests


Tenemos que ser profesionales we jaja


yeaah that's true !!


Hahaha yeaaaa :D


it doesn't??????


This is an update and fix to most of the bugs reported in #5420.


Merge branch 'master' of https://github.com/tucker777/QSTK


I think you are expecting the pascal-like return statement:

    removeAt: func(index: SSizeT) -> T{
        result = data[index] // result variable declared by compiler
        memmove(...
    }

As a 6-years-pascal-user, I like it. However, it needs some changes to FunctionDecl and Return.

The only reason preventing me from allocating on stack is that it breaks class members.
It is a big source of bugs. I don't have enough confident in remembering to add ``__heap__``
before all the generics. `gc_free` makes me less worry, even though it is a performance-killer.

Frankly speaking, instead of modifying the current generic system, I think we need to change to
the popular template system. The popular template system is fast, easy-to-understand and less buggy.
Upstream shows no interest in template class, but I think it is really needed.


Yup. This will be 2.0.


yay


I haven't done the exercise but this doesn't "look good". Maybe a recursive or functional-style algorithm would be better?


Thanks a loot. Totally forgot this.


Thanks @beeman by credits in WebSockets pull


I'm not a huge fan of `loop` but also not against it. But perhaps there is a better way of doing this - maybe at least pulling out the complicated expressions to keep the `loop` form clean and simple?


I have reverted the changes until I find a better fix for this.


I'm of the leaning that it's better to have something that works just enough before soliciting feedback; you want a solid design before you worry about painting the bike shed. Since a VB6 Forth won't be knocking on the hardware, we can forgo rather a lot of typical Forth oddities (stemming from its 1970s heritage) and make certain tasks much higher level -- for example fetching the image data from a BMP/JPG/PNG, something I would not want to write in Forth!


changed branch name from '4.x.x-snapshot' to '4.x.x' to reduce possible confusion, reduce possibility that 4.x.x looks like a tag, instead of a development branch, which is what it is in fact, a development branch.


test it with:
http://localhost:8080/los/lecture
for all objects,
and:
http://localhost:8080/los/lecture/{id}
for single objects


("_TXINPUT_") (02) (InputValue


Any chance we could not abbreviate this - `BeginScopeImplementation` \ `BeginLoggerScope`  etc?


This does not work for me. Do you have a working example?


@mikeferguson FYI this is on our test repo. Once testing for #3 is complete I'll deploy it to the live farm if you can test it that would be great. Thanks


int64 nAmount = AmountFromValue


smaller_make_shared (lefticus) - x86_64-Linux-Ubuntu-14.04-clang-3.5-AddressSanitizer: OK (346 of 346 tests passed)

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


`s/name hard/name would be hard/`


更新ありがとうございます！

一点だけ; 下の「コルーチン」の部分と同じく、この部分も

```
フリーかつオープンソース（MITライセンス）
```

と、括弧を付けたほうが良いかと思います。


TeamCity Architecture Team :: Java Platform :: otj-logging :: build-config [Build 15](http://teamcity.otenv.com/viewLog.html?buildId=1277499&buildTypeId=ArchitectureTeam_JavaPlatform_OtjLogging_BuildConfig) is now running


TeamCity Architecture Team :: Java Platform :: otj-logging :: build-config [Build 16](http://teamcity.otenv.com/viewLog.html?buildId=1277500&buildTypeId=ArchitectureTeam_JavaPlatform_OtjLogging_BuildConfig) is now running


Sorry for taking so long to reply, i just now realized this was here.
So use elseif instead of else if, no problem, any advantage or disadvantage either way?


TeamCity Architecture Team :: Java Platform :: otj-logging :: build-config [Build 16](http://teamcity.otenv.com/viewLog.html?buildId=1277500&buildTypeId=ArchitectureTeam_JavaPlatform_OtjLogging_BuildConfig) outcome was **FAILURE**
Summary: Exit code 1; exit code 2 Build time: 0:0:0


TeamCity Architecture Team :: Java Platform :: otj-logging :: build-config [Build 15](http://teamcity.otenv.com/viewLog.html?buildId=1277499&buildTypeId=ArchitectureTeam_JavaPlatform_OtjLogging_BuildConfig) outcome was **FAILURE**
Summary: Exit code 1; exit code 2 Build time: 0:0:0


I just slapped this together. Probably should be Ivan instead. :)


ეს image არ გიდევს პროექტში და src-ც სკმაოდ უცნაურად წერია.


Good catch about chunking being broken now. I should add a test for that. :-/ Let me take a look at this and get back to you.


`s/and import and/and import any/`


`s/seperate/separate/`


例は意味のある例を考えましょう。デザインパターンの勉強では「そのパターンが最も効果を発揮する場面を考える」のが有効なので。
今回の例えばロガーを`Singleton`にしてログ出力回数を数えるとか。


There is a `+` that was added as part of this key


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.360](http://teamcity.monogame.net/viewLog.html?buildId=6409&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


@tfoote is there any concern with the naming of the debian? Currently for trusty we have version "2.2.0.33-2~trusty2", this appears to import "libopenni2-0_2.2.0.33+dfsg-1~ubuntu14.04.1_amd64.deb" -- is that going to cause builds against the new library but users with installed versions don't get an upgrade?


smaller_make_shared (lefticus) - x86_64-Linux-Ubuntu-14.04-clang-3.5-ThreadSanitizer: OK (346 of 346 tests passed)

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


Note: I replaced the four-space indentation with tab indentation


:shipit:


This is also imported 3 lines below.


Those are not the 3D elements, but the tetrahedral_4_P elements, with 4 scalar fields.


smaller_make_shared (lefticus) - x86_64-Linux-Ubuntu-14.04-gcc-4.8: OK (346 of 346 tests passed)

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


I did read about this, just replace settimer( with maketimer( ? No other changes needed to use maketimer?
I can't even check the wiki right now!


Apart from the typo, I did mean to actually comment these lines (after discovering that we need to create a valid "consistent snapshots" repository before we can fully test `self.repository_updater.consistent_snapshot = True`.   That is, the updater expects to find `<hash>.filename` files when it requests targets and `root.json` enables consistent snapshots on [this](https://github.com/theupdateframework/tuf/blob/develop/examples/repository/metadata/root.json#L11) line.


I think so- how do you mean? I'll be committing all of my school stuff
there.

Also- ran my first user test on my flowchart idea on Saturday. It was
fucking awesome.

On Mon, Apr 27, 2015 at 2:04 PM, Mike Sinkula <notifications@github.com>
wrote:

> Is this going to be your main?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/klavin/scc/commit/ce1356e26e707b07af926249645900c7a0f6852f#commitcomment-10926445>
> .
>


Can we please replace `db_query` by `db_select` and add a custom tag, as I did on 5c5d37? This way we can alter the query as needed.


That does look like a lower number series from the current trusty packages. I think this change is fine but in the future it might be an issue. @jspricke do you have a thought?


In fact:
- created 3.x.x from master
- merged 4.x.x onto master


+weather_effects_loop();
no newline, is this an issue? Is there suppose to be a newline at the end of every file?


smaller_make_shared (lefticus) - x86_64-Linux-Ubuntu-14.04-gcc-4.6: OK (346 of 346 tests passed)

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


Looks good


@psoloway apt shouldn't have brackets around it.


Defaults to file should have single quotes, not backticks


the default should have single quotes around it to match the valid options


smaller_make_shared (lefticus) - x86_64-Linux-Ubuntu-14.04-cppcheck-1.67: OK (0 of 0 tests passed)

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


Create a Repository
A repository is the basic unit of GitHub, most commonly a single project. Repositories can contain folders and files, including images – anything your project needs. Because we recommend including a README, or a file describing the project, in every repository, GitHub makes it easy to add one at the same time you create your new repository. It also offers other common options such as a license file, but we can skip that for now.


(and removed 4.x.x branch too)


@psoloway Sorry, few more catches here. Pretty minor, in all, though the brackets around apt in the ToC are unattractive. Shouldn't take long to make the fixes and do a new PR for them.


LGTM. Thanks Nopphon!


@jakebolewski Wouldn't it make sense to have a default version that uses `Float64` or should we require the user to specify that for the verbose version where procs and block layout is specified?


Hi Jacky,

Please have a look at the sample_network_preserving_topology function at
https://github.com/emreg00/guild/blob/master/src/create_random_networks_for_netzcore.py

It is used for generating the random networks for NetZcore, see
https://github.com/emreg00/guild/blob/master/doc/guild.pdf for more info.

Let me know if you have more doubts on this.

Emre

On Sun, Apr 26, 2015 at 2:06 AM, jackyuanjie1990 <notifications@github.com>
wrote:

> the guild is excellent, but i have confusion,could u tell me how to call
> graph_utilities.randomize_graph function and can u give me an
> example,thanks.
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/emreg00/guild/commit/5f49e9c99c63350fa81e0fc4d4999702756e3495#commitcomment-10904234>
> .
>


鄙视 update.

@zhengjinghua


Amazing!


(Bryce Kalmbach) Just to talk through my reasoning to make sure it makes sense, yes, this is what I want. I would like to apply the proper extinction to each object's magnitude in each filter so catMags is an n-by-m matrix where n = # of objects and m = # of filters. ebvVals is an array of length # of objects (1 ebvValue for each object based upon its position) and therefore, n. extCoeffs is an array holding the values scaling ebv to extinction in each filter and thus is of the same length as the number of filters and therefore of length = m. So using outer on these two arrays gives me and an n-by-m matrix where n, m are equal to the values of the size of catMags and each object's magnitude in each filter gets changed by the appropriate amount.


(Scott Daniel) Okay.  Right.  I forgot that catMags contained magnitudes for multiple objects (I thought it was a numpy array of magnitudes for just one object).


(Lynne Jones) Bugfix/CATSIM-87 if the sed does not cover the full
* Changed exception to warning in resampleSed (and did some minor improvements/updates to documentation in both Bandpass and Sed). Also added self.bandpassname and self.sedname so that error messages can refer to which file was causing the problem (request from AndyC).
* Fixed problem that Scott pointed out and changed error handling to what AndyC actually wanted (bad value returned for magnitude, plus warning message).
* Updated Photometry and photUtils for changes in Sed (and to also do error handling appropriately in manyMag calculation).


(Scott Daniel) Shouldn't we replace the call to self.calcMag in line 799 (where we calculate dmag) with the value of curmag.  That way we don't call self.calcMag twice to calculate the same thing.


(Lynne Jones) You're right! Thanks for catching that.


(Scott Daniel) Feature/CATSIM-99 refactor DBObject
refactoring DBObject so that arbitrary SQL queries are possible.  The bulk of the description of this pull request will be in sims_catalogs_generation


(Lynne Jones) Bugfix/CATSIM-88 improve error message handling
Changed 'Exception' from resampleSED to 'warning', and changed interpolation values outside desired wavelength range to Nan. Checked that this Nan propagates to magnitudes and adu calculations.


(Andrew Connolly) Feature/SIM-1015 remove addigmattenuation from sed.py
removed addIGMattenuation as that is superceeded by applyIGM and was incorrect implementation(according to comments in code)


(Lynne Jones) Fabulous, been wanting to do this for a while.
While you're messing around with dust, do you want to update the documentation for the CCM dust methods?


Thanks man...


@Mystist 我删除都被你发现了……-_-!


@robertmesserle this code looks correct. The ngAnmate spec tests look the same (https://github.com/angular/angular.js/blob/master/test/ngAnimate/animateSpec.js#L1163).

Could you send me more info on slack as to what is failing with it? Where is the animation code that calls animations on `elements.$.ul`?


plese can you send me(bolterican@naver.com) scheme layout or upload it at the github..
I will make electric longboard with arduion..

thanks you for your code..

Very nice code~


Thanks,  @wintre.


I am sorry but my last commit did not work.


My personal pref is tabs everywhere, except for Python. Reason given by @mikedep333 above.

Mixing tabs with spaces should be considered as an error. I am aware of the whitespace badnesses in NX code and also in X.Org code, but we should not touch that for now, as it will kill patching across our different branches.


Is it possible to grab the 'moreID's' branch separate from the remainder of the project?

If so, how can I install it?


I fixed it here: 62990e3


test


Are you sure this is a fix?


This flip seems to be unnecessary. Just define the function flipped.


这个会导致手机端的首页头像被压缩。不好看。


rax retry tests


Hey @bnolan I'm brodavi@gmail.com  :)


Summary.summary is confusing. I suggest Summary.text.


Closes Issue #3


Please note:
This shouldn't change ANYTHING for your distro, except that it becomes 3 MB smaller if samba is preinstalled.


@chrissprague why do you need to add the directories at all?


um


Once you start breaking long lines and want the content to match, you will end up mixing both tabs and spaces, as in:

```C
<-tab-->foo("bla",
<-tab-->    "bar");
```

Replacing that with a tab will make it always look off, especially because the tab width can be anything from 1 space to any number spaces.

```C
<-tab-->foo("bla",
<-tab--><-tab-->"bar");
```


但是在实际的ipad上运行的时候有重影！


done


Bro...


Tabs aren't worth the trouble in my opinion and actually *hinder* collaboration by being non-deterministic and non-reliable (because at some point you have to use spaces anyway, c.f. the example above)


@khipkin because @ https://github.com/rit-csc/csc_exam_reviews/commit/60b8fc15e0e648bbd34647fb388810cfd614dccc#diff-b1d2ddab8f955f27a77a522e2f9a0eeaR29


get them up!


The builds have been deleted as well.
Screen shots of testing.
![screen shot 2015-04-26 at 8 13 53 pm](https://cloud.githubusercontent.com/assets/5906041/7341208/3b75706e-ec52-11e4-8c8e-47c94ae8adee.png)
![screen shot 2015-04-26 at 8 14 18 pm](https://cloud.githubusercontent.com/assets/5906041/7341209/4a3755b8-ec52-11e4-85ad-a18c06f0d064.png)


Please note:
No functional changes.

Just very sophisticated tools moved from package samba to samba-advanced, reducing package samba by 3 MB.

Upgrading samba from 3.0.37-r15 to 3.0.37-r16 on root.
Removing obsolete file /usr/bin/profiles.
Removing obsolete file /usr/bin/net.
Removing obsolete file /usr/lib/vfs/expand_msdfs.so.
Removing obsolete file /usr/bin/smbget.
Removing obsolete file /usr/lib/vfs/shadow_copy.so.
Removing obsolete file /usr/bin/smbcacls.
Removing obsolete file /usr/bin/smbcquotas.
Removing obsolete file /usr/lib/vfs/recycle.so.
Removing obsolete file /usr/lib/vfs/readonly.so.
Removing obsolete file /usr/lib/vfs/fake_perms.so.
Removing obsolete file /usr/lib/vfs/readahead.so.
Removing obsolete file /usr/bin/ntlm_auth.
Removing obsolete file /usr/bin/rpcclient.
Removing obsolete file /usr/lib/vfs/extd_audit.so.
Removing obsolete file /usr/lib/vfs/audit.so.
Removing obsolete file /usr/bin/smbtar.
Removing obsolete file /usr/lib/vfs/full_audit.so.
Removing obsolete file /usr/lib/vfs/cap.so.
Removing obsolete file /usr/lib/vfs/netatalk.so.
Removing obsolete file /usr/lib/vfs/default_quota.so.


corrected Quint css file


@astorije `chai-as-promised 5` requires `chai > 3`.
```
npm ERR! peerinvalid The package chai does not satisfy its siblings' peerDependencies requirements!
npm ERR! peerinvalid Peer chai-as-promised@5.0.0 wants chai@>= 2.1.2 < 3
```

Unfortunately, npm only has `chai 2.x.x` for now. Is the upgrade necessary? If not, I suggest to revert to `4.x.x`.


BuildXInputLib removed from X11.tmpl...


una vez que veas lo borro...pero como elimino el branch? xD


![screenshot 1](https://cloud.githubusercontent.com/assets/10776330/7341240/3607df12-ec6c-11e4-9801-e9c95aed47bd.png)


Thanks for contributing! However, it looks like there is already supposed to be code to handle the case of limitedDiscreteValues == null and use the whole domain, which is a much faster way to implement unrestricted BP. This default value of null should have avoided your problem to begin with -- can we figure out why this was getting set in the first place to a non-null value?


OK, it looks like Factor2 checks for limiteddiscretevalues == null, but Factor3 doesnt


Friend, Gawain Lynch'm new to the world of bolt, and Symfony2, but here I am trying to install bootstrap-carousel and do not work for me as expected, you will have a product sample to observe its operation, to check if like me the place as in steps
`` `
+ Myslider:
+ Content: carousel / 1
+ `` `
+ The `content: use the parameter` `{%%}` setContent style of record definition
+ And lookup. In the above example it will return the Record with contenttype
+ `Slider` and the record ID of 1.
+4. template file
+ In the location you want to display the slider in your template, add:

really do not know.
in advance thank you very much for the answer you can give me.


## This is a markdown file


Thanks for the heads up @Radizzt


Removed all references to BuildXkbcomp, as we do not ship the code and do not use it at build time.


@jkr, @mpickering, what do you think?

+++ nkalvi [Apr 24 15 19:16 ]:
>@jgm @jkr @mpickering
>
>`collapseFilePath` which uses `joinPath` formats the path according to the OS. This why the test failed.
>
>*in pandoc/src/Text/Pandoc/Readers/EPUB.hs*
>```
>-- Remove relative paths
>renameImages :: FilePath -> Inline -> Inline
>renameImages root (Image a (url, b)) = Image a (collapseFilePath (root </> url), b)
>```
>
>---
>An easy fix seems to be using the `joinPath` and `pathSeparator` from `System.FilePath.Posix`, since all file related operations should convert the path before the operation (look like they do). Also, this won't require changes to anything else (pardon me if I'm wrong, as my familiarity with Pandoc/Haskell is minimal).
>
>All the current tests pass with the following changes:
>
>**Shared.hs**
>```
>import qualified System.FilePath.Posix as Posix (joinPath, pathSeparator)
>
>collapseFilePath :: FilePath -> FilePath
>collapseFilePath = Posix.joinPath . reverse . foldl go [] . splitDirectories
>  where
>    go rs "." = rs
>    go r@(p:rs) ".." = case p of
>                            ".." -> ("..":r)
>                            (checkPathSeperator -> Just True) -> ("..":r)
>                            _ -> rs
>    go _ (checkPathSeperator -> Just True) = [[Posix.pathSeparator]]
>    go rs x = x:rs
>    isSingleton [] = Nothing
>    isSingleton [x] = Just x
>    isSingleton _ = Nothing
>    checkPathSeperator = fmap isPathSeparator . isSingleton
>```
>
>**Tests/Shared.hs**
>```
>import System.FilePath.Posix (joinPath)
>```
>
>
>
>---
>Reply to this email directly or view it on GitHub:
>https://github.com/jgm/pandoc/commit/56e4ecab20613d86a6660547ed87e7ff4b80d632#commitcomment-10899420


This doesn't seem legit...


使用MockMvc做单元测试时，进入controller后，为啥@Valid注解不起作用


YaY. Moogle porter, finally ^.^


@brson The release date is still requires update.


Did a lot of work with the first two pages.
MainWindow.xaml
- The Login button now properly has an animation
- The Exit button has an animation
- Edited styles of the login page to look more modern
- Rename restaurant to BURGERTOPIA!

LoginWindow.xaml
- reskinned to match background
- style overhaul
- Added animations for login buttons
- Added animations to cancel buttons


dddd


OK!


I forked your repo to commit the fix but you already have it. Add the battery bar back to the navigation_bar.XML in res/layout only not the one in sw whatever and only add it once, not twice like before and it should work for you. It wasn't enough to create a pull request once I forked but if you have issues let me know


can you return false here? findbugs reported a new issue 'NULL Pointer Dereference'


use attribute obsolete and disallow  compilation for project that using this :)


GOOD! I meet the same problem. ths


慢工出細活！那就慢慢來吧。


sorry we did this at the same time, will fix up now


A few points:
* The FAQ is not the standard. In reality, there are several contradictions between the FAQ and the standard. This is known at the editorial committee, and we're trying to catch up, but ambiguities and contradictions remain. In short, the FAQ is the for the consumption of people new to Unicode. The actual standard(s) should be consulted instead if you know your way around them. (I just sent a comment to the consortium asking for the FAQ to be fixed.)

* The official *normative* definition of White_Space is given in [UAX 44](http://unicode.org/reports/tr44/#White_Space). It has no relation to display:

> White_Space: [...] Spaces, separator characters and other control characters which should be treated by programming languages as "white space" for the purpose of parsing elements."

* I support @khaledhosny's position. If you want to show things like Medium Mathematical Space when the font doesn't support them, you need to adjust the width.

* The actual amount of space for some of these depends on the language. Thin space is apparently interesting. According to [Microsoft's font recommendations](https://www.microsoft.com/typography/developers/fdsspec/spaces.aspx):

> Thin space U+2009 - Standard setting is 1/5 of the em space. [...] The standard language dependent setting for French is 1/8 of the em space. [...]


Dont worry, I'll fix


I'm hot for this.


Thanks for cleaning this up - I did a more shoddy job than expected.


xcsoft님 이렇게 하시면 !UseQ 일때 막타를 아예 안치게 됩니다.
Q 안쓰게 해놨는데 Q가 레디가 아닐때 평타를 치게 해놔서 수동으로 Q 쓸때까지 절대 막타를 안치게 되는걸요.
한편 UseQ일때도 문제가 발생하는데 Q를 이미 사용하여 Q를 사용할수 없게 된 상태에서 평타로 막타 가능할때도 평타를 안치게 됩니다.

해결하시려면 &&을 ||로 바꿔서 or로 처리하는게 바람직하다고 봅니다만.


@GingerBear what is technique zoon? :eyes:


Andres planas


i deleted spaces between appearing in class/value (ggg = "hhhh") as best practice is to  have no spaces bbb="cccc"


stray `puts`


To how sammich had it that is


nice !!!
if not SSH, how are you doing this …
pushing via HTTPS ???
============
> On Apr 26, 2015, at 6:55 PM, mi3kie <notifications@github.com> wrote:
>
> a busload of lawyers!
>
> —
> Reply to this email directly or view it on GitHub.
>


Let's get this done before the PR is merged.


I made a change to my result in second commit because in my first result I did not run the command to add 'Edina' for employees who do not have city value. so that is why in first one when I count employees living in Edina I got (2) instead of 3.


s/alraedy/already


var uvOptions = {};
(function() {
  var uv = document.createElement('script'); uv.type = 'text/javascript'; uv.async = true;
  uv.src = ('https:' == document.location.protocol ? 'https://' : 'http://') + 'widget.uservoice.com/YOURSPECIALKEY.js';
  var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(uv, s);
})();


good! 다른이들에게는 비밀.


Fixes `C:\\` vs. `C:\`


On  Mo 27 Apr 2015 05:22:12 CEST, Mihai Moldovan wrote:

> Once you start breaking long lines and want the content to match,
> you will end up mixing both tabs and spaces, as in:
>
> ```C
> <-tab-->foo("bla",
> <-tab-->    "bar");
> ```

Indeed. This I normally do.

> Replacing that with a tab will make it always look off, especially
> because the tab width can be anything from 1 space to any number
> spaces.
>
> ```C
> <-tab-->foo("bla",
> <-tab--><-tab-->"bar");
> ```

This I never do (but I have seen others doing it...)
--

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb


optimize function is_binary case


引数が多いね
引数は3つぐらいに抑えたいところだね
抑えるためには構造体を使おう！


Why did you change the logic here?


Grischa,

Remember to be careful when using response.json() without a try/except block.

The original code was designed to catch the case where the username entered into MyData's settings dialog didn't exist in MyTardis, in which case, the MyTardis API would return 401 (unauthorized), which was handled by the "if status_code < 200 or status_code >= 300" code below.  By using "response.json()" instead, you don't catch the 401 exception, and instead raise a JSONDecodeError which wasn't handled anywhere.  I've commited a workaround here: https://github.com/monash-merc/mydata/commit/b0d34f0fb9212526a6b1c51079774db248564574


Hey @JayWood.. Thanks for your pull code, but the README.md created by `grunt` tasks. I need to change this from there. :)


Got things working in a new pull request (PR #282). I get significantly different values for the 2nd set of marginals than you do, though. How did you get the numbers listed in this test?

Thanks again for pointing out this bug and locating the error! I also found another bug when fixing this.


画像がない部分（名前のみ）については、リンクも名前のみでOKです。
プロフィール画像のサムネイルの箇所は取り除くようにお願いします。

また、細かい部分ですが、

aipo.message.popupProfile(${key.OwnerId})
↓
aipo.message.popupProfile(${key.OwnerId}, arguments[0])

のような記述が必要ですので調整お願いします。


Uh... Only saw the modulo before and thought it would be fine... But right
it does a normal divide for the first index of course...

Was a normal std::map really too slow for this? This bucket thing only
comes with a lot of complexity...


On 26/04/15 20:17, Kenneth Heafield wrote:
> StringPiece has an implicit constructor from char * and std::string so
> there's no need for wrappers. More importantly, it's a char * and a
> size_t with no requirement that it be null terminated. This makes it
> particularly useful for tokenization tasks because it can be done with
> zero copying.

That sounds like it could save a lot of performance, if it happens in
hot portions of the code...  I'm not looking at performance yet, but at
some point I probably will.

Jeroen


A prime example of your great work.
You will be sorely missed.


@nicekiwi Well I considered it a fix since before it wasn't autoloading the classes correctly. What would you consider it to be?

I guess I could of said. I made a alteration to the composer.json file to autoload the classes correctly since the first alteration didn't work.

Do you see something wrong with this commit?


We'll work on trusting git so we can get rid of all these commented out lines of code. :)


It doesn't only break navigation - `VBProject` reference equality is also used in `CodeInspectionResultBase.FindComponent`, which starts returning `null`, on top of navigation being broken throughout the application. That's really bad because **we *want* background parsing!!**


You mentioned you are working on force touch drivers. By when do you expect it to be completed? Thanks..


This line throws the following warning when we build:
```
.../blocstagram3/Blocstagram/BLCDataSource.m:76:45: Data argument not used by format string
```
This line will only append an '@' symbol to the sentence, and discard the `randomWord` because of a small typo


This cast will actually check the type of the passed object and cause an early failure if it isn't a IGridHost


`__sync_and_and_fetch`? add? Does it compile?


Why do you add a space after the if ?


Initial Commit


mix-blend-mode는 지원하는 브라우저가 적음. 전적으로 의존하지 않도록 수정해야


@vu3rdd Should this be defined here or in the test file? Should the binary have Quickcheck as a dependency?


It's good for now.

I would rather that we were doing unit testing (mocking out the Google API calls with {requests, responses}, etc.

There seems to be some support for it in the google api, but I haven't found good documentation yet, so let's just go forward...


그거 이 다음 커밋에서 삭제되고 다른걸로 대치되는데, 걔도 문지가 있나염


/#google still works -- /?service=google just works in the same way.  (Facebook and G+ was destroying the hash urls when shared on their platforms)


@ipetkov Why is there a mouse click when we change to the gun?


Do you remember why v4.0.1 was an issue?


> for performance reasons.

Detect doesn't account for a significant portion of build time. You have some benchmarks?


I think this is to get around not having fast weapon switch enabled on games like HL Deathmatch or CS Source (tapping the key selects the weapon, clicking confirms the selection).


Ok. It's only there for the gun though. Should we take it out, or add it to the rest of them (maybe under a toggle)?


It could be that the key tap and mouse click events occur so quickly the game doesn't register the click in the case where quick selection is enabled, so we never noticed it during testing.


If it works without it, feel free to take it out


Remove this line and add a new one


@chrissprague explain please?


Ahh gotcha, yea mine is setup similarly, alright then, hope the other PR  helps at least :)


Such improvement.


at this point wont `user == principal`? Calling principal actually loads the user from the database by username.


bahkdwxwrzx
142179biptzdy


Should be fixed as of 6a366d535a6cbb6f524063da3b3134b6cf3d7093


@khipkin the make file now moves the output of make (`pdflatex`, etc) into directories for us to be more organized, and I needed a way to force those directories to exist. Otherwise the `mv` would fail by either saying the directory to move to didn't exist, or it would actually change the name of the files to what the directories were supposed to be called


@chrissprague that's pretty hacky... is there any way you could just add an `if` statement, and then create directories as needed?


BTW I was planning on testing this exact feature.  Glad to know it works. :)


Not sure what's wrong at the moment, but all the tuples in my song list are (0,0)


FYI I think soon you will be able to easily drop Typeable, as we won't be instantiating DS.Models upfront so it will be easy to change the type later on


Good catch.  Yes I think we should allow non-dialog forming requests to have no contact.  Will commit a fix.


# =============== #
# Unity generated #
# =============== #
Temp/
Obj/
UnityGenerated/
Library/
Sprite/
SpriteInServer/


Good catch.  I agree we should allow non-dialog forming requests to have no contact.


This is how we keep the screen alive on iOS. Then we immediately cancel that navigation action with a delayed window.stop on the following line


このリストはHatoholサーバーが実装しているプロシージャ一覧ですよね？
そうであればfetchと名のついた4つのプロシージャは必要ないのではないでしょうか。

各監視対象が使用可能なプロシージャリストと，Hatoholサーバーが受け入れ可能なプロシージャリストは
それぞれ別個に用意しておく必要があると思いました。


@zpforyou thanks! please make a pull request with these changes


Hi @jehanronald. I am unsure what your problem is.

If you are copying the example from this page, it will not work as this is just a diff. You can see the [readme.md file rendered for human reading here](https://github.com/GawainLynch/bolt-extension-bootstrap-carousel/blob/master/readme.md).

The best place to discuss this as a question though is in the [issue tracker here](https://github.com/GawainLynch/bolt-extension-bootstrap-carousel/issues/new).


Repo created


Verified and fixed. Thanks!


I just noticed that here, and for planets, you dropped the portion that would provide "unknown:<id>" if the system or planet could not be retrieved.  This would mean that if the calling code counted on getting an entry back it would have an error.


おぉ、そうですね。指摘ありがとうございます。
fetchと付いた４つのプロシージャ周りの動きが良く把握できていないので検討してみます。


人才呀，add 能写成 add。

@FrankHB 当然是有这个函数的。


Why did you not set cell's accessoryType to be DisclosureIndicator?


@lhmouse 是说使用这段代码的该用`++`的地方用了`&`会是什么情况。


this


Hi @tianon, we program arbitrary containers and at our level we do not know it is a WORDPRESS container. That's why we use only docker-standard environment variables.

The proposal above sounds good. Can we get this in? :)


*Still could not merge or intersect polygons together using ST_Union or ST_Intersection functions. Using the following sql statements below, I can get the populations and population changes of the 11 circuits that contain 1 county, and the 1 district that contains 1 county, but still cannot get the information for all districts and circuits.

CREATE VIEW population_change_districts AS (SELECT * FROM population_change_geom NATURAL JOIN districts)
CREATE VIEW population_change_circuits AS (SELECT * FROM population_change_geom NATURAL JOIN circuits)

Cannot determine population distribution of districts. However, based on the 11 circuits, I can state that they do not equal population distributions, and therefore thee circuit outlines are not determined strictly by population.


It's in the storyboard. If it's really not your preference I'll stop using
it, but I wanted to be consistent.
On Mon, Apr 27, 2015 at 1:09 AM Justin (Zihao) Zhang <
notifications@github.com> wrote:

> Why did you not set cell's accessoryType to be DisclosureIndicator?
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/huyouare/Duke-Study-Group/commit/99a3e8d9c5ecb66cf253008bfb11f662318fd2aa#commitcomment-10909261>
> .
>


Style nit: Please move this to the bottom of the file.


Thanks so much for keeping the docs up to date.  I owe you one :-)


@jaseemabid Yeah, it shouldn't be here. I plan to move it into a testinstance.hs file.


si van a entrar con el usuario de la central es mejor que entren por la url /central :+1:


After the last import please add:
# pylint: disable=superfluous-parens


I also get this warning while I'm building

    [4 of 8] Compiling FuncTorrent.Bencode ( src/FuncTorrent/Bencode.hs, dist/build/FuncTorrent/Bencode.o )

    src/FuncTorrent/Bencode.hs:30:10: Warning:
        Orphan instance: instance Arbitrary ByteString
    [5 of 8] Compiling FuncTorrent.Metainfo ( src/FuncTorrent/Metainfo.hs, dist/build/FuncTorrent/Metainfo.o )
    [6 of 8] Compiling FuncTorrent.Peer ( src/FuncTorre


Domotina ahora solo tiene una propiedad el resto fue repartido entre los demás usuarios.


So the mechanism to prevent screen from sleeping is different between Android and iOS? iOS's screen doesn't put to sleep if there is video playing as far as I know.


Irrelevant patch.


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.331](http://teamcity.monogame.net/viewLog.html?buildId=6375&buildTypeId=MonoGame_DevelopWin&guest=1) is now running


Was about to fix, sorry about that :)


> generators.assert

If this now lives in its own module, the test naming seems a little strange.


Thx for the changes, one small style nit but looks good to go in.


@webron this is kind of a bummer but I have no other way to run a series of tests without resetting the value of "initialized"


`Objects::Substation.where(location: {'$within' => {'$box' => locs}}).count`


/* quoting myself just to keep it in a single place */

> As for TAB, certain fonts don't have nbsp and/or tab, and most fonts don't have line separator, paragraph separator, and many other space characters.
> In my opinion, HarfBuzz should take care of (quite common) issue with missing glyphs for characters of property White_Space.

> Possible solution:
> - The glyph for White_Spaces should be replaced with the glyph for U+0020 (except for U+0020 itself). EDIT: perhaps in a missing glyph case only
>   This is a good first approximation which guarantees we would never get a box for White_Spaces.
> - If there is no glyph for White_Space in the font (and we just replaced it with the glyph for U+0020), simply dup the metrics for U+0020 as well; otherwise believe the font provides a correct metrics.
>   This doesn't care about ie. half-width spaces but also a good approximation for the most-common case.
> - A more sophisticated mechanism would also take care of glyph advances, making U+000A..U+000D, U+0085, U+2028..U+2029 occupy no space, U+202F occupy "narrow" space, and simply dub U+0020 metrics for other space characters.
> Of course, this only applicable when no HB_BUFFER_FLAG_PRESERVE_DEFAULT_IGNORABLES has been set; otherwise do nothing.


I get it too, I don't know how to resolve it at the moment. If I remove
the instance, code won't compile.

--
Ramakrishnan "Err and err and err again, but less and less and less"
⟶ Piet Hein


This can be simplified:
```moon
EnemyType = switch love.math.random numEnemies
	when 1,2 then Octorok
	when 3,4 then Tektite
	when 5,6 then Follower
	when 7   then HardOctorok
```


@saleemkce actually it was done few days ago: https://github.com/piwik/piwik/commit/90372750b039ce0b2150d4d6b1279fecbb245465

so this should be fixed now in git master!


What about having a YAML file in the content repo that has that list of major versions?


ramilkz, еще раз: у нас ДЛИННОЕ число.
Читай readme.md, там написано, как оно должно быть представлено. Это не исправление, прога с этой функцией не взлетит.


Use `==` operator in Scala. Read: http://stackoverflow.com/questions/24860919/use-instead-of-equals-for-string-comparison-in-scala


i have a sneaking suspicion that this actually has nothing to do with the window size (as you can resize it to whatever you like), a fact which I for one find rather disturbing.


maybe we should use the `cohesiveStep` or `swarmStep` for our demo, IDK?


@jdoliner Am I using FindNew correctly here? The btrfs man page describes `find-new` as having the behavior I'm expecting (I think). It seems like line 358 should be passing..


TeamCity MonoGame :: Develop (Win) [Build 3.4.0.331](http://teamcity.monogame.net/viewLog.html?buildId=6375&buildTypeId=MonoGame_DevelopWin&guest=1) outcome was **SUCCESS**
Summary: Tests passed: 484, ignored: 6 Build time: 00:14:53


FragMap.mlatLng is static. I use FragMap.mlatLng in my next code. I use  my next code for displaying of 24 hour logged path of the car. My next code is ready and currently I merge this code with current version of the project.

I have added the My Location button because irritates me an unexpected moving of  the map after moving of the car to another location. I think, that other users irritates this also. I think, good idea, do not move the camera after moving of vehicle. User can see his car on the map any time by click the My Location button. I have commented some code in the FragMap.update() functon for this.

See https://github.com/openvehicles/Open-Vehicle-Android/commit/4ff4140446eb39e66cba2977e0a78502d6f451e6


this is actually a fault of mine, eventually we need to do something like get the current year. 2015 is hard coded in :-1:


The graphics (`mode: "demonstration"`) were also posted to Openclipart: https://openclipart.org/detail/217669/wii-buttons-mouse-buttons-keyboard-keys

The cheat sheet itself was also posted to reddit: https://www.reddit.com/r/emulation/comments/3401m9/mayflash_wireless_sensor_dolphinbar_cheat_sheet/


Don't call self.delegate sliderLayoutWidth more than once. Also need curly brackets even for single-line conditional.


i was getting this issue when i upgraded mongoose
https://github.com/Automattic/mongoose/issues/2821


I think a better identifier should be in place; maybe apptType?


We don't use curly braces on single line blocks (same below).


clang: error: no such file or directory: '/Users/manak/Library/Developer/Xcode/DerivedData/VideoRecoderProj-frgckddgwcrnvjeqlserunssglge/Build/Products/Debug-iphonesimulator/libSCRecorder.a'


Why aren't these initially set to true like before?


@zperee-bbc Es funzt aber no easy nix...


for (var index = 0; index < atLeastOne.length; index++)

to

for (var index = 0; index < **advAtLeastOne**.length; index++)


advAtLeastOne


Die Kamera muss nicht unbedingt den ganzen Bereich erfassen, also könnte die auch bei Steuerung nach links u. rechts sich bewegen.

Im original ist die Ansicht ja so von oben Schräg drauf, ich weiß nicht ob ich das so einfach hinbekomm. Ich würde die Anischt eher von hinten machen d.h. er kann sich dann schräg links vor , schräg rechts vor und geradeaus bewegen.


You rock! I fixed it in c5052fb. Thanks.


no longer exists


I like this :+1:


defunct


github project is gone


No longer using docpad, AFAICT


github project defunct


재수없으면 여기에 도달하기 전에 load 이벤트가 이미 실행될 수 있음


guess we should add these rule to `pending` too.


done 0797e46608752c09b2388fd16c9da579a83c1054


So the checkbox doesn't actually have a major written to it, what's actually happening is it's grabbing the major from where the checkbox was selected, and verifying that we're accessing the correct advisor for the student's major


Commented individual lines for clarity. After rebasing the commits mushed together.


It works! You're amazing! Will push commit in a second - I am not going to merge because I made one slight change to use the same Paginator as the others. Thank you so much! :O)


This commit breaks image magnifier feature. Do not merge. This is just a proof of concept.


知っていたら申し訳ないですが、StringBuilderはメソッドチェーンをサポートしています。
どちらの書き方をするかは好みの問題だと思いますが

```
createUseInfoTable.append(〜)
    .append(〜)
    .append(〜)
    .append(〜);
```

という書き方ができます。PreferenceのEditorなんかも同様ですね。
追加が多い時に書く量を減らせるので覚えておいて損はないと思います。


FYI - fixed this in the latest version!


of course, i will add it back asap


:question: :ghost:


This still links to Fig.


네, 그럼 이건 문제 없겠네요! 좋아보여요.


__API Blueprint syntax error on line 788__: the use of tab(s) '\t' in source data isn't currently supported, please contact makers (Autogenerated message from apiary.io)


url?


Can you please delete this block if it's not needed anymore (this improves readability of code and diff, and history will be kept in git)


StringBuilderを文字列にするのにこの方法は初めて見ました。
`createUseInfoTable.toString()`でStringを生成するのが普通と思ってましたがどうなんでしょう？
有識者の意見求む！


Please use an enum for that.


PG 9.2 is the minimum.. thanks, I edited that other line I missed!


Good catch, thanks!
Yeah, I suppose I should have called `.json()` after the status check instead. Then if it doesn't parse there is a bigger issue with MyTardis and the program could report a server error.


What's written in the `.gtex` file changed and scores from 3.0 cannot be compiled with 4.0 if I understand correctly, so I think this requires a major version change?


I don't really know how to call what's before rc1... I didn't document it on the wiki, but the wiki could be improved on that


不需重複initialize