text:
---
layout: post
rel_link:  "9_4_0_pre1"
title:  "CMSSW_9_4_0_pre1"
date:   2017-09-16 12:54:33
categories: cmssw
relmajor: 9
relminor: 4
relsubminor: 0
relpre: _pre1
---

# CMSSW_9_4_0_pre1
#### Changes since CMSSW_9_3_0:
[compare to previous](https://github.com/cms-sw/cmssw/compare/CMSSW_9_3_0...CMSSW_9_4_0_pre1)

1. [20544](http://github.com/cms-sw/cmssw/pull/20544){:target="_blank"}  from **@cms-sw**: Updates to DQMServices/Core for new protobuf version `dqm`  created: 2017-09-16 08:37:40 merged: 2017-09-16 12:47:51

2. [20543](http://github.com/cms-sw/cmssw/pull/20543){:target="_blank"}  from **@cms-sw**: Revert "Updates to DQMServices/Core for new protobuf version." `comparison`  `dqm`  created: 2017-09-16 08:21:58 merged: 2017-09-16 08:22:05

3. [20541](http://github.com/cms-sw/cmssw/pull/20541){:target="_blank"}  from **@cms-sw**: fixes needed for llvm 5.0: use fully qualified clangcms::support namespace `core`  created: 2017-09-15 19:25:16 merged: 2017-09-16 11:09:36

4. [20527](http://github.com/cms-sw/cmssw/pull/20527){:target="_blank"}  from **@ianna**: Step 2 amendment: Simulation Clang tidy code-checks-all and Clang Warnings Removed `simulation`  `upgrade`  created: 2017-09-15 07:55:33 merged: 2017-09-16 12:48:52

5. [20524](http://github.com/cms-sw/cmssw/pull/20524){:target="_blank"}  from **@ianna**: Step 1 amendment: Simulation Clang tidy code-checks-all and Clang Warnings Removed `simulation`  `upgrade`  created: 2017-09-15 07:02:36 merged: 2017-09-15 12:33:23

6. [20503](http://github.com/cms-sw/cmssw/pull/20503){:target="_blank"}  from **@apana**: Fix to prevent possible crashes if the prescale table changes during job `l1`  created: 2017-09-13 16:27:05 merged: 2017-09-15 11:38:57

7. [20499](http://github.com/cms-sw/cmssw/pull/20499){:target="_blank"}  from **@ghellwig**: [94X] Fix geometry centering tool. `alca`  created: 2017-09-13 15:56:17 merged: 2017-09-14 13:34:36

8. [20498](http://github.com/cms-sw/cmssw/pull/20498){:target="_blank"}  from **@Dr15Jones**: Fix histogram limits in SiPixelClusterSource `dqm`  created: 2017-09-13 15:09:46 merged: 2017-09-14 13:35:01

9. [20496](http://github.com/cms-sw/cmssw/pull/20496){:target="_blank"}  from **@fioriNTU**: Fix hi phase1 `dqm`  created: 2017-09-13 10:13:10 merged: 2017-09-13 19:31:14

10. [20490](http://github.com/cms-sw/cmssw/pull/20490){:target="_blank"}  from **@dildick**: Code checks for PR19986 `simulation`  `upgrade`  created: 2017-09-13 00:08:46 merged: 2017-09-15 12:35:43

11. [20480](http://github.com/cms-sw/cmssw/pull/20480){:target="_blank"}  from **@swagata87**: create and clear vector of vertex index per-muon, not per event. `core`  `hlt`  created: 2017-09-12 18:06:56 merged: 2017-09-15 07:47:37

12. [20479](http://github.com/cms-sw/cmssw/pull/20479){:target="_blank"}  from **@felicepantaleo**: HGCal - bugfix - removing energy of out-of-range hits `reconstruction`  `upgrade`  created: 2017-09-12 17:45:33 merged: 2017-09-13 19:31:50

13. [20473](http://github.com/cms-sw/cmssw/pull/20473){:target="_blank"}  from **@arunhep**: remove LumiPixels from list of AlCaRecos from Matrix `alca`  created: 2017-09-12 10:33:47 merged: 2017-09-13 19:32:03

14. [20470](http://github.com/cms-sw/cmssw/pull/20470){:target="_blank"}  from **@makortel**: Fix summary harvesting for built tracks MTV `dqm`  created: 2017-09-12 09:45:50 merged: 2017-09-12 19:28:34

15. [20469](http://github.com/cms-sw/cmssw/pull/20469){:target="_blank"}  from **@ebrondol**: adding LogError for quality computation `simulation`  created: 2017-09-12 07:58:34 merged: 2017-09-12 19:29:03

16. [20468](http://github.com/cms-sw/cmssw/pull/20468){:target="_blank"}  from **@smuzaffar**: fix clang build error: replace static const with static constexpr `dqm`  `l1`  created: 2017-09-12 07:15:51 merged: 2017-09-12 19:31:52

17. [20467](http://github.com/cms-sw/cmssw/pull/20467){:target="_blank"}  from **@Dr15Jones**: Need to exclude PathInserter from the test `core`  created: 2017-09-12 01:04:09 merged: 2017-09-12 07:39:45

18. [20466](http://github.com/cms-sw/cmssw/pull/20466){:target="_blank"}  from **@Dr15Jones**: Simple configuration testing `core`  created: 2017-09-11 19:04:25 merged: 2017-09-12 07:39:58

19. [20461](http://github.com/cms-sw/cmssw/pull/20461){:target="_blank"}  from **@prebello**: updates in relvals  `pdmv`  `upgrade`  created: 2017-09-11 15:57:56 merged: 2017-09-15 07:46:53

20. [20458](http://github.com/cms-sw/cmssw/pull/20458){:target="_blank"}  from **@kpedro88**: reject seed candidates not part of superclusters `reconstruction`  `upgrade`  created: 2017-09-11 14:45:58 merged: 2017-09-13 19:32:34

21. [20455](http://github.com/cms-sw/cmssw/pull/20455){:target="_blank"}  from **@cms-tsg-storm**: HLT menu "Luna" V3.1 (94X) `core`  `hlt`  created: 2017-09-11 13:59:26 merged: 2017-09-12 16:04:27

22. [20454](http://github.com/cms-sw/cmssw/pull/20454){:target="_blank"}  from **@kurtejung**: RelVal fix for HI Jet DQM `dqm`  created: 2017-09-11 13:29:34 merged: 2017-09-12 19:29:58

23. [20450](http://github.com/cms-sw/cmssw/pull/20450){:target="_blank"}  from **@makortel**: Monitor seed stopping reason and number of trajectory candidates per seed in tracking DQM `alca`  `dqm`  `hlt`  `reconstruction`  created: 2017-09-11 10:11:51 merged: 2017-09-15 12:37:14

24. [20449](http://github.com/cms-sw/cmssw/pull/20449){:target="_blank"}  from **@fabozzi**: adding DQM-only wf on AOD input for HLT validation `pdmv`  `upgrade`  created: 2017-09-11 08:54:11 merged: 2017-09-15 07:49:18

25. [20448](http://github.com/cms-sw/cmssw/pull/20448){:target="_blank"}  from **@pieterdavid**: Update SiStripDetSummary usage in the SiStrip Payload Inspector `comparison`  `db`  created: 2017-09-09 18:42:43 merged: 2017-09-10 08:48:50

26. [20447](http://github.com/cms-sw/cmssw/pull/20447){:target="_blank"}  from **@Dr15Jones**: Minor Framework speed improvements `core`  created: 2017-09-09 16:31:52 merged: 2017-09-12 07:40:29

27. [20444](http://github.com/cms-sw/cmssw/pull/20444){:target="_blank"}  from **@wddgit**: Move functions filling common provenance to IOPool/Provenance `core`  created: 2017-09-08 21:06:33 merged: 2017-09-14 13:37:52

28. [20442](http://github.com/cms-sw/cmssw/pull/20442){:target="_blank"}  from **@Dr15Jones**: Converted test modules to global modules `core`  created: 2017-09-08 18:22:45 merged: 2017-09-10 16:09:04

29. [20441](http://github.com/cms-sw/cmssw/pull/20441){:target="_blank"}  from **@swagata87**: muon hit `hlt`  created: 2017-09-08 18:10:32 merged: 2017-09-11 15:47:34

30. [20440](http://github.com/cms-sw/cmssw/pull/20440){:target="_blank"}  from **@wddgit**: Add new function getProducerParameterSet `core`  created: 2017-09-08 17:51:10 merged: 2017-09-09 07:15:28

31. [20437](http://github.com/cms-sw/cmssw/pull/20437){:target="_blank"}  from **@bsunanda**: Run2-hcx153 Make correct usage of HcalGeometry `dqm`  created: 2017-09-08 15:30:22 merged: 2017-09-12 09:53:15

32. [20436](http://github.com/cms-sw/cmssw/pull/20436){:target="_blank"}  from **@Dr15Jones**: Capture initialization time in total job time `core`  created: 2017-09-08 15:01:29 merged: 2017-09-09 07:15:49

33. [20433](http://github.com/cms-sw/cmssw/pull/20433){:target="_blank"}  from **@ghellwig**: [94X] Fix static analyzer warnings in Alignment `alca`  created: 2017-09-08 09:42:36 merged: 2017-09-10 16:09:50

34. [20430](http://github.com/cms-sw/cmssw/pull/20430){:target="_blank"}  from **@ghellwig**: [94X] Replace GBL in CMSSW code with GBL code from external library. `alca`  created: 2017-09-08 08:51:13 merged: 2017-09-10 16:16:52

35. [20428](http://github.com/cms-sw/cmssw/pull/20428){:target="_blank"}  from **@bsunanda**: Run2-alca95 Modify the MIP calibration codes `alca`  created: 2017-09-07 20:37:06 merged: 2017-09-10 16:10:54

36. [20427](http://github.com/cms-sw/cmssw/pull/20427){:target="_blank"}  from **@bsunanda**: Run2-alca94 Add a new method to compute energy sum of ECAL towers preceding a HCAl cell `alca`  created: 2017-09-07 20:24:00 merged: 2017-09-12 16:04:40

37. [20426](http://github.com/cms-sw/cmssw/pull/20426){:target="_blank"}  from **@bsunanda**: Run2-hcx152 Test the constituent map of CaloTower `geometry`  created: 2017-09-07 19:21:02 merged: 2017-09-12 09:53:37

38. [20425](http://github.com/cms-sw/cmssw/pull/20425){:target="_blank"}  from **@Dr15Jones**: Allow edm::soa::Table<> as a data product `core`  created: 2017-09-07 18:49:39 merged: 2017-09-08 17:17:54

39. [20422](http://github.com/cms-sw/cmssw/pull/20422){:target="_blank"}  from **@kpedro88**: include dark current contribution in M2 pedestal constraint for Phase2 `hlt`  `reconstruction`  `upgrade`  created: 2017-09-07 16:33:02 merged: 2017-09-12 07:41:39

40. [20421](http://github.com/cms-sw/cmssw/pull/20421){:target="_blank"}  from **@jalimena**: bug fixes for RHStopTracer (94X) `simulation`  created: 2017-09-07 15:37:41 merged: 2017-09-15 12:31:18

41. [20420](http://github.com/cms-sw/cmssw/pull/20420){:target="_blank"}  from **@wddgit**: Apply scram b code-checks to Core bin files `core`  created: 2017-09-07 15:19:23 merged: 2017-09-08 17:18:05

42. [20419](http://github.com/cms-sw/cmssw/pull/20419){:target="_blank"}  from **@Dr15Jones**: Fix crashes in edmConfigBrowser `core`  created: 2017-09-07 14:37:58 merged: 2017-09-08 17:18:15

43. [20416](http://github.com/cms-sw/cmssw/pull/20416){:target="_blank"}  from **@bsunanda**: Run2-hcx151 Correct for geometry access for Hcal `fastsim`  created: 2017-09-07 13:48:03 merged: 2017-09-12 16:05:21

44. [20411](http://github.com/cms-sw/cmssw/pull/20411){:target="_blank"}  from **@jnsandhya**: adding special hgcal relval workflows in upgradeWorkflowComponents `pdmv`  `upgrade`  created: 2017-09-07 06:55:47 merged: 2017-09-08 17:18:40

45. [20409](http://github.com/cms-sw/cmssw/pull/20409){:target="_blank"}  from **@bsunanda**: Run2-hcx150 Correct access to Hcal geometry `fastsim`  created: 2017-09-06 19:45:46 merged: 2017-09-16 08:23:29

46. [20406](http://github.com/cms-sw/cmssw/pull/20406){:target="_blank"}  from **@gartung**: Updates to DQMServices/Core for new protobuf version. `dqm`  created: 2017-09-06 15:06:40 merged: 2017-09-16 08:19:47

47. [20403](http://github.com/cms-sw/cmssw/pull/20403){:target="_blank"}  from **@dan131riley**: add option for sequential RootEmbeddedFileSequence to not recycle files `core`  `dqm`  created: 2017-09-06 14:31:46 merged: 2017-09-08 17:19:24

48. [20397](http://github.com/cms-sw/cmssw/pull/20397){:target="_blank"}  from **@lpernie**: GT Updates with L1T updates and tracker ideal alignment `alca`  created: 2017-09-06 10:04:44 merged: 2017-09-11 10:03:11

49. [20396](http://github.com/cms-sw/cmssw/pull/20396){:target="_blank"}  from **@folguera**: [MuonHLT]: BugFix for TSGforOI in 93X `hlt`  `reconstruction`  created: 2017-09-06 09:48:50 merged: 2017-09-12 07:43:32

50. [20394](http://github.com/cms-sw/cmssw/pull/20394){:target="_blank"}  from **@gmandorl**: Updated vbf filter v2 `generators`  created: 2017-09-06 08:40:12 merged: 2017-09-12 07:44:40

51. [20372](http://github.com/cms-sw/cmssw/pull/20372){:target="_blank"}  from **@fwyzard**: TriggerBxMonitor: add support for 2D plots `dqm`  `hlt`  created: 2017-09-04 16:40:53 merged: 2017-09-11 15:48:27

52. [20368](http://github.com/cms-sw/cmssw/pull/20368){:target="_blank"}  from **@archiron**: Add the HGCAL-Seeded ElectronSeed collection to the FEVT and RECO event contents. `reconstruction`  `upgrade`  created: 2017-09-04 13:49:37 merged: 2017-09-06 15:57:22

53. [20367](http://github.com/cms-sw/cmssw/pull/20367){:target="_blank"}  from **@gpetruc**: Small miniAOD improvements `analysis`  `reconstruction`  created: 2017-09-04 12:26:12 merged: 2017-09-08 17:22:34

54. [20366](http://github.com/cms-sw/cmssw/pull/20366){:target="_blank"}  from **@argiro**: Ecal pedestal PCL improvements : fix for Nans, added histos, added check, added exclusion of non-stabl `alca`  `pdmv`  `upgrade`  created: 2017-09-04 11:49:32 merged: 2017-09-09 07:15:15

55. [20362](http://github.com/cms-sw/cmssw/pull/20362){:target="_blank"}  from **@makortel**: Add primary vertex resolution to tracking DQM `dqm`  created: 2017-09-04 08:32:38 merged: 2017-09-12 07:46:16

56. [20359](http://github.com/cms-sw/cmssw/pull/20359){:target="_blank"}  from @natalia-korneeva: btag**@HLT** paths modification to be consistent with the new HLT menu `dqm`  created: 2017-09-03 14:41:48 merged: 2017-09-12 09:16:43

57. [20358](http://github.com/cms-sw/cmssw/pull/20358){:target="_blank"}  from **@Dr15Jones**: limited:: module types `core`  created: 2017-09-02 19:20:06 merged: 2017-09-06 11:55:27

58. [20356](http://github.com/cms-sw/cmssw/pull/20356){:target="_blank"}  from **@jhgoh**: RPC DQM occupancy bugfix + cleanup `dqm`  created: 2017-09-01 21:47:35 merged: 2017-09-11 09:03:45

59. [20349](http://github.com/cms-sw/cmssw/pull/20349){:target="_blank"}  from **@bsunanda**: Run2-hcx148 Correct the access of Geometry information for Hcal `analysis`  created: 2017-09-01 18:30:16 merged: 2017-09-11 15:50:00

60. [20344](http://github.com/cms-sw/cmssw/pull/20344){:target="_blank"}  from **@npostiau**: Update smp validation paths `dqm`  created: 2017-09-01 13:12:19 merged: 2017-09-13 19:35:23

61. [20329](http://github.com/cms-sw/cmssw/pull/20329){:target="_blank"}  from **@jnsandhya**: updating splitting function for DIGI step `pdmv`  `upgrade`  created: 2017-08-31 09:17:26 merged: 2017-09-11 07:36:27

62. [20327](http://github.com/cms-sw/cmssw/pull/20327){:target="_blank"}  from **@Dr15Jones**: Async global end LuminosityBlock transition `core`  created: 2017-08-30 23:17:58 merged: 2017-09-06 11:55:45

63. [20322](http://github.com/cms-sw/cmssw/pull/20322){:target="_blank"}  from **@mtosi**: add sequence for HLTDQM only step on AOD `dqm`  created: 2017-08-30 19:26:37 merged: 2017-09-08 17:28:13

64. [20319](http://github.com/cms-sw/cmssw/pull/20319){:target="_blank"}  from **@pgunnell**: New tune snippets `generators`  created: 2017-08-30 15:41:31 merged: 2017-09-12 16:05:35

65. [20309](http://github.com/cms-sw/cmssw/pull/20309){:target="_blank"}  from **@cms-met**: propagation of hcal geometry changes for the csc halo algo `reconstruction`  created: 2017-08-30 07:06:51 merged: 2017-09-14 13:36:32

66. [20298](http://github.com/cms-sw/cmssw/pull/20298){:target="_blank"}  from @mtosi: fix # MEs in pixel DQM**@HLT** as requested by #20192 `dqm`  created: 2017-08-29 14:25:39 merged: 2017-09-06 15:58:45

67. [20274](http://github.com/cms-sw/cmssw/pull/20274){:target="_blank"}  from **@pieterdavid**: Port SiStripDetSummary from subdetector-DetId classes to TrackerTopology `alca`  `analysis`  `db`  `dqm`  `reconstruction`  created: 2017-08-25 14:16:54 merged: 2017-09-08 17:27:28

68. [20253](http://github.com/cms-sw/cmssw/pull/20253){:target="_blank"}  from **@mtosi**: fix num and den selection for the fractionOfGoodTracks plots [tracking DQM] `dqm`  created: 2017-08-24 13:35:23 merged: 2017-09-08 17:28:02

69. [20153](http://github.com/cms-sw/cmssw/pull/20153){:target="_blank"}  from **@Sam-Harper**: Adapting Single Leg Conversions to PhaseI Pixels `reconstruction`  created: 2017-08-14 11:26:38 merged: 2017-09-06 11:58:18

70. [20143](http://github.com/cms-sw/cmssw/pull/20143){:target="_blank"}  from **@bbockelm**: Add per-site Xrootd statistics to the HTCondor monitoring. `core`  created: 2017-08-11 20:20:22 merged: 2017-09-06 16:03:06

71. [20051](http://github.com/cms-sw/cmssw/pull/20051){:target="_blank"}  from **@abbiendi**: Updated muon mc classifier `analysis`  `simulation`  created: 2017-08-03 22:03:38 merged: 2017-09-12 07:48:36

72. [20019](http://github.com/cms-sw/cmssw/pull/20019){:target="_blank"}  from **@mdelcourt**: Updates on SiStrip G2 and calibtree `alca`  created: 2017-08-02 10:09:07 merged: 2017-09-12 07:48:08

73. [20010](http://github.com/cms-sw/cmssw/pull/20010){:target="_blank"}  from **@dimattia**: Memory reduction of the Cluster Charge Histogram used in SiStrip gain calibration `alca`  `dqm`  created: 2017-08-01 21:08:36 merged: 2017-09-15 09:50:28

74. [19935](http://github.com/cms-sw/cmssw/pull/19935){:target="_blank"}  from **@lgray**: Vectorized 2D simulated annealing vertexing `dqm`  `reconstruction`  `upgrade`  created: 2017-07-27 11:23:55 merged: 2017-09-12 19:34:31

75. [19896](http://github.com/cms-sw/cmssw/pull/19896){:target="_blank"}  from **@lgray**: Add in CCE degradation and add HGCal to aging customizations `reconstruction`  `simulation`  `upgrade`  created: 2017-07-25 12:04:31 merged: 2017-09-06 15:54:55

76. [19874](http://github.com/cms-sw/cmssw/pull/19874){:target="_blank"}  from **@depasse**: Ecal payload inspector with plot image (v2) `db`  created: 2017-07-24 09:19:05 merged: 2017-09-12 07:51:34

77. [19853](http://github.com/cms-sw/cmssw/pull/19853){:target="_blank"}  from **@perrozzi**: introduce MINIGEN step and output to replace GenOnly workflows `analysis`  `operations`  `reconstruction`  created: 2017-07-21 09:36:52 merged: 2017-09-12 19:31:34

78. [19671](http://github.com/cms-sw/cmssw/pull/19671){:target="_blank"}  from **@mengleisun**: Add photons to TopMonitor and run MuonEG path in SUSY monitor `dqm`  created: 2017-07-11 03:16:23 merged: 2017-09-12 09:58:31

#### CMSDIST Changes between Tags REL/CMSSW_9_3_0/slc6_amd64_gcc630 and REL/CMSSW_9_4_0_pre1/slc6_amd64_gcc630:
[compare to previous](https://github.com/cms-sw/cmsdist/compare/REL/CMSSW_9_3_0/slc6_amd64_gcc630...REL/CMSSW_9_4_0_pre1/slc6_amd64_gcc630)

1. [3415](http://github.com/cms-sw/cmsdist/pull/3415){:target="_blank"}  from **@mkirsano**: upgrade to lhapdf 6.2.1 created: 2017-09-13 21:28:17 merged: 2017-09-15 08:08:51

2. [3409](http://github.com/cms-sw/cmsdist/pull/3409){:target="_blank"}  from **@cms-sw**: apply dmtcp-3.0.0-dev-ptr-int-comp patch created: 2017-09-13 11:01:09 merged: 2017-09-13 11:01:14

3. [3406](http://github.com/cms-sw/cmsdist/pull/3406){:target="_blank"}  from **@cms-sw**: Revert "Update data-L1Trigger-L1TMuon.spec" created: 2017-09-12 22:25:49 merged: 2017-09-12 22:25:55

4. [3405](http://github.com/cms-sw/cmsdist/pull/3405){:target="_blank"}  from **@cms-sw**: update sherpa to 2.2.4 created: 2017-09-12 14:37:28 merged: 2017-09-15 08:12:46

5. [3392](http://github.com/cms-sw/cmsdist/pull/3392){:target="_blank"}  from **@cms-sw**: Backport gcc630next changes created: 2017-09-08 09:32:07 merged: 2017-09-12 14:18:21

6. [3390](http://github.com/cms-sw/cmsdist/pull/3390){:target="_blank"}  from **@vkuznet**: New dasgoclient version created: 2017-09-07 12:06:38 merged: 2017-09-08 05:41:29

7. [3387](http://github.com/cms-sw/cmsdist/pull/3387){:target="_blank"}  from **@cms-sw**: applied clang-tidy on thepeg created: 2017-09-07 07:36:14 merged: 2017-09-07 09:00:24

8. [3385](http://github.com/cms-sw/cmsdist/pull/3385){:target="_blank"}  from **@cms-sw**: downgrade herwigpp until herwig 7 in CMSSW starts to work created: 2017-09-06 09:28:05 merged: 2017-09-06 09:30:47

9. [3384](http://github.com/cms-sw/cmsdist/pull/3384){:target="_blank"}  from **@ghellwig**: [94X] Add GeneralBrokenLines as external library. created: 2017-09-06 08:53:06 merged: 2017-09-10 16:16:36

10. [3382](http://github.com/cms-sw/cmsdist/pull/3382){:target="_blank"}  from **@gartung**: Use version of protobuf used internally by Tensorflow. created: 2017-09-05 16:33:09 merged: 2017-09-16 12:47:19

11. [3380](http://github.com/cms-sw/cmsdist/pull/3380){:target="_blank"}  from **@cms-sw**: Update data-L1Trigger-L1TMuon.spec created: 2017-09-05 13:10:14 merged: 2017-09-12 14:20:28

repository: cms-sw/ReleaseNotes

repo_name: cms-sw/ReleaseNotes


text:
# 0.10.0

## Breaking changes

- `clamp01` has been restricted to `AbstractGray` and `AbstractRGB`, as it did not make sense for colors like `HSV` (#181)
- Step 3 of [ColorVectorSpace's `abs2` transition has been completed](https://github.com/JuliaGraphics/ColorVectorSpace.jl#abs-and-abs2); users and developers should now replace any `ColorVectorSpace.Future.abs2` calls with `abs2` to prevent breakage when the final step completes.

## Other changes

- AbstractFFTs.jl is no longer a dependency; error hints are now used for `fft` operations on deliberately-unsupported `Colorant` types
- Graphics.jl is no longer a dependency
- PrecompileTools.jl is now used for precompilation

# 0.7.0

## Breaking changes

- Switch to Julia 0.7
- Because of changes to Julia's own `reinterpret`, ImageCore now
  defines and exports `reinterpretc` for reinterpreting
        numeric arrays <----> colorant arrays (#52)
- The ColorView and ChannelView types are deleted; their functionality
  is now handled via `reinterpret` (#52)

# 0.6.0

- Last minor version with Julia 0.6 support

license: MIT

branch_name: refs/heads/master

extension: md

gha_language: Julia

gha_license_id: NOASSERTION

license_type: permissive


text:
# dialog

[![Filament Group](http://filamentgroup.com/images/fg-logo-positive-sm-crop.png) ](http://www.filamentgroup.com/)

Just a simple, minimal, Responsive jQuery/Shoestring dialog with typical interactivity

See demo page for how-to and examples:

- https://master-origin-dialog.fgview.com/demos/
- OR if it's a branch you want to see: https://BRANCHNAMEHERE-origin-dialog.fgview.com/demos/

[![Build Status](https://travis-ci.org/filamentgroup/dialog.svg)](https://travis-ci.org/filamentgroup/dialog)

repository: uschmelzer/dialog

repo_name: uschmelzer/dialog


text:
![Katharsis logo](http://katharsis.io/assets/img/engine_katharsis_github_4.png)

Katharsis library adds an additional layer on top of RESTful endpoint to provide easy HATEOAS support for Java by implementing JSON API standard.

# katharsis-framework

[![Build Status](https://travis-ci.org/katharsis-project/katharsis-framework.svg?branch=develop)](https://travis-ci.org/katharsis-project/katharsis-framework)

Systems nowadays utilize data from various systems to leverage the business needs. To achieve that, many of them provide usually inconsistent REST interface.

__Providing homogeneous REST interface__

Katharsis implements JSON API standard which introduces consistent REST interface definition. Now it can be easy to integrate with other systems through uniform mechanisms.

__Use the purest form of REST__

JSON API is based on HATEOAS which means Hypermedia as the Engine of Application State. It is the highest form of REST which allows producing and storing as little documentation as possible.

---

By using Katharsis it is easier to develop both Customer Facing Applications and server side services. The developers can have one unified base for their work.

__Consistent resources and repositories__

Katharsis introduces a way of defining both resources which can be shared over the REST interface and a repository for their handling.

__Integration with other libraries__

Because of the usage of JSON API, Katharsis can be used with many other libraries which support the standard.

## Documentation and examples
Documentation, along with example projects and project details are available on project website [katharsis.io](http://katharsis.io) and [katharsis-jsonapi.readthedocs.io](http://katharsis-jsonapi.readthedocs.io/)

## Chat
Need to directly talk to us? Write on gitter:

[![Join the chat at https://gitter.im/katharsis-project/katharsis-framework](https://badges.gitter.im/Join%20Chat.svg)](https://gitter.im/katharsis-project/katharsis-framework?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)

repository: Cropster/katharsis-framework

branch_name: refs/heads/develop

repo_name: Cropster/katharsis-framework


text:
# ShadowSatyr

A simple CMS developed in Java

__Features__:
* Hibernate 4.3.9 with JPA 2.1
* Configurable
* Apache Shiro 1.2.3
* Apache Tiles 3.0.5
* SeiferNet web framework 1.3.6
* Markdown support
* Microblog client
* Article publishing
* Gravatar integration

It's intended to be deployed in a __JBoss__ application
server version __7.1__ or higher.

repository: seiferson/shadowsatyr

repo_name: seiferson/shadowsatyr


text:
# react-pdf-js-infinite-slugs
---
[![npm version](https://badge.fury.io/js/react-pdf-js-infinite-slugs.svg)](https://badge.fury.io/js/react-pdf-js-infinite-slugs)

`react-pdf-js-infinite-slugs` provides a component for rendering PDF documents using [PDF.js](http://mozilla.github.io/pdf.js/). Written for React 15 and ES2015 using the Airbnb style guide. Include onclick callbacks to specific locations.

---

Usage
-----

Install with `npm install react-pdf-js-infinite-slugs`

Use in your app

```js
import React, { Component } from 'react';
import PDF from 'react-pdf-js-infinite-slugs';

export default class Viewer extends Component {

  render() {
    return (
      <div>
        <PDF
          file="somefile.pdf"
          scale={1.5}
          onClick={(e,coordinates) => {
            console.log(coordinates);
          }}
        />
      </div>
    )
  }
}
```

## Credit

This project is a fork of [react-pdf-js-infinite](https://github.com/McRipper/react-pdf-js-infinite) which is a fork of [react-pdf-js](https://github.com/mikecousins/react-pdf-js) which is a fork of [react-pdfjs](https://github.com/erikras/react-pdfjs) which itself was a port of [react-pdf](https://github.com/nnarhinen/react-pdf), so thank you to
the original authors.

repository: freeslugs/react-pdf-js-infinite

repo_name: freeslugs/react-pdf-js-infinite


text:
---
title: ISTIO-SECURITY-2019-004
subtitle: Security Bulletin
description: Security vulnerability disclosure for multiple CVEs.
cve: [CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9518]
publishdate: 2019-08-13
keywords: [CVE]
skip_seealso: true
---

{{< security_bulletin
        cves="CVE-2019-9512, CVE-2019-9513, CVE-2019-9514, CVE-2019-9515, CVE-2019-9518"
        cvss="7.5"
        vector="CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
        releases="1.1 to 1.1.12, 1.2 to 1.2.3" >}}

## Context

Envoy, and subsequently Istio are vulnerable to a series of trivial HTTP/2-based DoS attacks:

* HTTP/2 flood using PING frames and queuing of response PING ACK frames that results in unbounded memory growth (which can lead to out of memory conditions).
* HTTP/2 flood using PRIORITY frames that results in excessive CPU usage and starvation of other clients.
* HTTP/2 flood using HEADERS frames with invalid HTTP headers and queuing of response `RST_STREAM` frames that results in unbounded memory growth (which can lead to out of memory conditions).
* HTTP/2 flood using SETTINGS frames and queuing of SETTINGS ACK frames that results in unbounded memory growth (which can lead to out of memory conditions).
* HTTP/2 flood using frames with an empty payload that results in excessive CPU usage and starvation of other clients.

Those vulnerabilities were reported externally and affect multiple proxy implementations.
See [this security bulletin](https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md) for more information.

## Impact and detection

If Istio terminates externally originated HTTP then it is vulnerable.   If Istio is instead fronted by an intermediary that terminates HTTP (e.g., a HTTP load balancer), then that intermediary would protect Istio, assuming the intermediary is not itself vulnerable to the same HTTP/2 exploits.

## Mitigation

* For Istio 1.1.x deployments: update to a [Istio 1.1.13](/news/releases/1.1.x/announcing-1.1.13) or later.
* For Istio 1.2.x deployments: update to a [Istio 1.2.4](/news/releases/1.2.x/announcing-1.2.4) or later.

{{< boilerplate "security-vulnerability" >}}


text:
# Lumen PHP Framework

[![Build Status](https://travis-ci.org/laravel/lumen-framework.svg)](https://travis-ci.org/laravel/lumen-framework)
[![Total Downloads](https://poser.pugx.org/laravel/lumen-framework/d/total.svg)](https://packagist.org/packages/laravel/lumen-framework)
[![Latest Stable Version](https://poser.pugx.org/laravel/lumen-framework/v/stable.svg)](https://packagist.org/packages/laravel/lumen-framework)
[![License](https://poser.pugx.org/laravel/lumen-framework/license.svg)](https://packagist.org/packages/laravel/lumen-framework)

Laravel Lumen is a stunningly fast PHP micro-framework for building web applications with expressive, elegant syntax. We believe development must be an enjoyable, creative experience to be truly fulfilling. Lumen attempts to take the pain out of development by easing common tasks used in the majority of web projects, such as routing, database abstraction, queueing, and caching.

## Official Documentation

Documentation for the framework can be found on the [Lumen website](https://lumen.laravel.com/docs).

## Contributing

Thank you for considering contributing to Lumen! The contribution guide can be found in the [Laravel documentation](https://laravel.com/docs/contributions).

## Security Vulnerabilities

If you discover a security vulnerability within Lumen, please send an e-mail to Taylor Otwell at<EMAIL_ADDRESS>All security vulnerabilities will be promptly addressed.

## License

The Lumen framework is open-sourced software licensed under the [MIT license](https://opensource.org/licenses/MIT).

## Requirement

1. Make sure already installed composer https://getcomposer.org/
2. Clone the git project
3. On the terminal prompt make sure already point to apps, run "composer install"
4. Set environtment first, rename the ".env.example" into ".env" and
   change DB_DATABASE, DB_USERNAME and DB_PASSWORD
5. Migrate table into databse with run this command "php artisan migrate"
6. Seeding fake data with run this command "php artisan db:seed"
7. Serve project Using this command "php -S localhost:8000 -t public"

repository: dinailman/rdtx-backend-test

repo_name: dinailman/rdtx-backend-test


text:
# 2. frontend architecture patterns

Date: 2021-04-01

## Status

2021-04-01 proposed

## Context

Context here...

## Decision

 - [ ] component-based architecture
 - [ ] component-based layered architecture

## Consequences

Consequences here...

repository: inherd/forming

repo_name: inherd/forming


text:
---
layout: post
title: TodoBackend Benchmarks
tags: [rails, elixir, sinatra, expressjs, nodejs, maru, phoenix, ruby, rails5]
---

I compared some of the framworks on [TodoBackend](http://todobackend.com/) project with some tweaks.

All these are backed by `postgres`. So obviously these benchmarks are not purely for the framework itself but the whole stack.

# Phoenix

[https://github.com/jeffweiss/todobackend-phoenix](https://github.com/jeffweiss/todobackend-phoenix){:target="_blank"}

{% highlight bash %}
wrk -t20 -c100 -d30S --timeout 2000  "http://localhost:3000/api/todos"
Running 30s test @ http://localhost:3000/api/todos
  20 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    23.76ms    3.25ms 114.35ms   96.11%
    Req/Sec   212.01     16.17   252.00     80.19%
  126864 requests in 30.09s, 82.27MB read
Requests/sec:   4216.04
Transfer/sec:      2.73MB
{% endhighlight %}

# Sinatra

[https://github.com/moredip/todo-backend-sinatra](https://github.com/moredip/todo-backend-sinatra){:target="_blank"}

- removed the logging

{% highlight bash %}
wrk -t20 -c100 -d30S --timeout 2000  "http://localhost:3000/todos"
Running 30s test @ http://localhost:3000/todos
  20 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    13.63ms   11.83ms 173.18ms   88.35%
    Req/Sec   324.15    119.35   690.00     70.84%
  106624 requests in 30.10s, 93.75MB read
Requests/sec:   3542.85
Transfer/sec:      3.12MB
{% endhighlight %}

# ExpressJs

[https://github.com/dtao/todo-backend-express](https://github.com/dtao/todo-backend-express){:target="_blank"}

Non Cluster mode

{% highlight bash %}
wrk -t20 -c100 -d30S --timeout 2000  "http://localhost:3000/"
Running 30s test @ http://localhost:3000/
  20 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    81.96ms   97.83ms 498.72ms   79.26%
    Req/Sec   144.97     93.23   540.00     63.28%
  81397 requests in 30.10s, 44.48MB read
Requests/sec:   2704.28
Transfer/sec:      1.48MB
{% endhighlight %}

Cluster mode

- added cluster mode

{% highlight bash %}
wrk -t20 -c100 -d30S --timeout 2000  "http://localhost:3000/"
Running 30s test @ http://localhost:3000/
  20 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    21.58ms   20.51ms 408.22ms   90.05%
    Req/Sec   273.38     58.89   550.00     73.69%
  163169 requests in 30.07s, 89.16MB read
Requests/sec:   5425.57
Transfer/sec:      2.96MB
{% endhighlight %}

# Elixir Maru

[https://github.com/whitfieldc/maru_todo](https://github.com/whitfieldc/maru_todo){:target="_blank"}

{% highlight bash %}
wrk -t20 -c100 -d30S --timeout 2000  "http://localhost:3000/tasks"
Running 30s test @ http://localhost:3000/tasks
  20 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    21.77ms    5.43ms 143.73ms   95.62%
    Req/Sec   232.93     23.00   272.00     88.08%
  139189 requests in 30.07s, 68.25MB read
Requests/sec:   4628.15
Transfer/sec:      2.27MB
{% endhighlight %}

# Vanilla Rails

[https://github.com/hammerdr/todo-backend-rails](https://github.com/hammerdr/todo-backend-rails){:target="_blank"}

{% highlight bash %}
wrk -t20 -c100 -d30S --timeout 2000  "http://localhost:3000"
Running 30s test @ http://localhost:3000
  20 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    61.33ms   16.54ms 247.46ms   76.96%
    Req/Sec    60.09     32.24   141.00     60.18%
  26936 requests in 30.08s, 24.30MB read
Requests/sec:    895.37
Transfer/sec:    827.20KB
{% endhighlight %}

# Rails 5

{% highlight bash %}
wrk -t20 -c100 -d30S --timeout 2000  "http://localhost:3000"
Running 30s test @ http://localhost:3000
  20 threads and 100 connections
  Thread Stats   Avg      Stdev     Max   +/- Stdev
    Latency    41.48ms   27.82ms 417.76ms   65.79%
    Req/Sec    90.61     63.23   280.00     63.91%
  29777 requests in 30.10s, 26.16MB read
Requests/sec:    989.23
Transfer/sec:      0.87MB
{% endhighlight %}


text:
# Introduction

This Project deals with the total dataset used in a previous project for improved performance. Here two types of techniques are
used (i.e) Deep Learning and XGBoost

# Dataset Source

The Dataset link is: https://archive.ics.uci.edu/ml/datasets/bank+marketing#

# Summary

## Deep Learning -

Training Accuracy - 92 % and Test Accuracy - 91.80 %

## XGBoost-

Training Accuracy - 94 % and Test Accuracy - 92.85 %


text:
# Frequently Asked Questions

This page is a compilation of frequently asked questions and answers.

## An old version of CUDA.jl keeps getting installed!

Sometimes it happens that a breaking version of CUDA.jl or one of its dependencies is
released. If any package you use isn't yet compatible with this release, this will block
automatic upgrade of CUDA.jl. For example, with Flux.jl v0.11.1 we get CUDA.jl v1.3.3
despite there being a v2.x release:

```
pkg> add Flux
  [587475ba] + Flux v0.11.1
pkg> add CUDA
  [052768ef] + CUDA v1.3.3
```

To examine which package is holding back CUDA.jl, you can "force" an upgrade by specifically
requesting a newer version. The resolver will then complain, and explain why this upgrade
isn't possible:

```
pkg> add CUDA.jl@2
  Resolving package versions...
ERROR: Unsatisfiable requirements detected for package Adapt [79e6a3ab]:
 Adapt [79e6a3ab] log:
 ├─possible versions are: [0.3.0-0.3.1, 0.4.0-0.4.2, 1.0.0-1.0.1, 1.1.0, 2.0.0-2.0.2, 2.1.0, 2.2.0, 2.3.0] or uninstalled
 ├─restricted by compatibility requirements with CUDA [052768ef] to versions: [2.2.0, 2.3.0]
 │ └─CUDA [052768ef] log:
 │   ├─possible versions are: [0.1.0, 1.0.0-1.0.2, 1.1.0, 1.2.0-1.2.1, 1.3.0-1.3.3, 2.0.0-2.0.2] or uninstalled
 │   └─restricted to versions 2 by an explicit requirement, leaving only versions 2.0.0-2.0.2
 └─restricted by compatibility requirements with Flux [587475ba] to versions: [0.3.0-0.3.1, 0.4.0-0.4.2, 1.0.0-1.0.1, 1.1.0] — no versions left
   └─Flux [587475ba] log:
     ├─possible versions are: [0.4.1, 0.5.0-0.5.4, 0.6.0-0.6.10, 0.7.0-0.7.3, 0.8.0-0.8.3, 0.9.0, 0.10.0-0.10.4, 0.11.0-0.11.1] or uninstalled
     ├─restricted to versions * by an explicit requirement, leaving only versions [0.4.1, 0.5.0-0.5.4, 0.6.0-0.6.10, 0.7.0-0.7.3, 0.8.0-0.8.3, 0.9.0, 0.10.0-0.10.4, 0.11.0-0.11.1]
     └─restricted by compatibility requirements with CUDA [052768ef] to versions: [0.4.1, 0.5.0-0.5.4, 0.6.0-0.6.10, 0.7.0-0.7.3, 0.8.0-0.8.3, 0.9.0, 0.10.0-0.10.4] or uninstalled, leaving only versions: [0.4.1, 0.5.0-0.5.4, 0.6.0-0.6.10, 0.7.0-0.7.3, 0.8.0-0.8.3, 0.9.0, 0.10.0-0.10.4]
       └─CUDA [052768ef] log: see above
```

A common source of these incompatibilities is having both CUDA.jl and the older
CUDAnative.jl/CuArrays.jl/CUDAdrv.jl stack installed: These are incompatible, and cannot
coexist. You can inspect in the Pkg REPL which exact packages you have installed using the
`status --manifest` option.

## Can you wrap this or that CUDA API?

If a certain API isn't wrapped with some high-level functionality, you can always use the
underlying C APIs which are always available as unexported methods. For example, you can
access the CUDA driver library as `cu` prefixed, unexported functions like
`CUDA.cuDriverGetVersion`. Similarly, vendor libraries like CUBLAS are available through
their exported submodule handles, e.g., `CUBLAS.cublasGetVersion_v2`.

Any help on designing or implementing high-level wrappers for this low-level functionality
is greatly appreciated, so please consider contributing your uses of these APIs on the
respective repositories.


text:
# bioloid_common
This ROS package contains description's files to simulates and visualizes the bioloid humanoid robot.

## ROS Dependecies
Install message-to-tf to convert odometry to tf:
```
$ sudo apt install ros-kinetic-message-to-tf
```
Case you are using ROS melodic you can download this package from [here](https://github.com/tu-darmstadt-ros-pkg/hector_localization).

## RViz Usage
Standalone (using TF transform from fake joint state publisher GUI):
```
$ roslaunch bioloid_description rviz.launch standalone:=true
```

With ros control (using TF from robot joint publisher's joint state from ros control):
```
$ roslaunch bioloid_description rviz.launch
```

![system](bioloid_description/assets/images/bioloid_rviz.png)

## Gazebo Usage
You can launch the simulation with:

```
$ roslaunch bioloid_gazebo gazebo.launch
```

PRESS PLAY IN GAZEBO ONLY WHEN EVERYTHING IS LOADED (wait for controllers)

![system](bioloid_gazebo/assets/images/bioloid_gazebo.png)

If you want to launch gazebo headless (without GUI) uses:
```
$ roslaunch bioloid_gazebo gazebo.launch uses_gui:=false
```

In order to move the joints using trajectory controller uses:
```
rosrun rqt_joint_trajectory_controller rqt_joint_trajectory_controller
```

To start the simulation call this service:
```
$ rosservice call /gazebo/unpause_physics "{}"
```

## Topics
```
$ rostopic list
  /clock
  /rosout
  /rosout_agg
  /tf
  /tf_static
  /typea/footl_contact_sensor_state
  /typea/footr_contact_sensor_state
  /typea/imu
  /typea/joint_states
  /typea/joint_trajectory_controller/command
  /typea/joint_trajectory_controller/follow_joint_trajectory/cancel
  /typea/joint_trajectory_controller/follow_joint_trajectory/feedback
  /typea/joint_trajectory_controller/follow_joint_trajectory/goal
  /typea/joint_trajectory_controller/follow_joint_trajectory/result
  /typea/joint_trajectory_controller/follow_joint_trajectory/status
  /typea/joint_trajectory_controller/state
  /typea/odom
```


text:
## pytorch Implementation

[Google Colaboratory](https://colab.research.google.com/drive/1FPcPOsv0Vp9g_l4MXj3sag8UfXacslhk?usp=sharing)

## What is Style Transfer?

- For  style, the earlier layers provide for a more "localized" representation. This is opposed to the content model, where the later layers represent a more "global" structure.

![https://s3-us-west-2.amazonaws.com/secure.notion-static.com/0feb0811-f9e6-4a3d-a908-30094a227252/st1.jpeg](https://s3-us-west-2.amazonaws.com/secure.notion-static.com/0feb0811-f9e6-4a3d-a908-30094a227252/st1.jpeg)

## Creating  the VGG model function

1. VGG19 features portion is the CNN layers
2. keeping requires grad = False keeps the parameters unaffected during gradient decent and backpropogation
3. torch.device function to use GPU
4. connect the model to the device

## Image preprocessing function

1. Unsqueeze adds an extra dimension (just like np.expand.dims) (batch size, H, W, channel)
2. Image is resized to the maximum (400 pixel this case) dimension
3. Image is normalized to mean=0.5 and stdv= 0.5
4. Image is converted to a tensor

## Loading the content and the style image

1. Convert the image into 'RGB' format
2. Load the images and converted into TENSOR
3. Pass in the shape parameter so as the two images are of the same size

## Convert the images into numpy array for Visualization

1. Tensor passed in is in shape (batch_size, color channel, H, W)
2. Clone before to converting to numpy array
3. then squeeze the batch_size dimension
4. Transpose the array in shape (H,W, color channel) for matplotlib
5. denormalize the image
6. Clip the image so that it is in 0 to 1 range

![https://s3-us-west-2.amazonaws.com/secure.notion-static.com/8ee47872-dc3d-4b1d-b2ba-c91b0687d25f/Untitled.png](https://s3-us-west-2.amazonaws.com/secure.notion-static.com/8ee47872-dc3d-4b1d-b2ba-c91b0687d25f/Untitled.png)

## Get Features for the intermediate layers for content and style layer outputs (Targets)

1. Initializing the layers that will be used for content and style output
2. Create a dictionary to store the output of the image at each layer
3. Create a feature dictionary for content image
4. Create a feature dictionary for style image

## Define function for Gram Matrix for  style loss

1. Create a gram matrix function
2. Loop in each output of the style features and create a gram matrix dictionary.

$$style loss = mean((gram_matrix(y) - grammatrix(t))**2)$$

Gram Matrix :

- Input Shape: (H,W,C)
- It’s then converted into (H*W, C) named as X
- Multiply with its transpose.
- Resulting Shape: (C,C)
- This makes the network loses the spatial information and only keep the style features of the style image

$$X^TX/N$$

![https://s3-us-west-2.amazonaws.com/secure.notion-static.com/eb242b54-5a78-4725-a8cf-5dadce9de997/899C3830-D192-4979-B960-94E9F8E1707D.jpeg](https://s3-us-west-2.amazonaws.com/secure.notion-static.com/eb242b54-5a78-4725-a8cf-5dadce9de997/899C3830-D192-4979-B960-94E9F8E1707D.jpeg)

## Assigning weight to style and content layer loss

1. In style features earlier layers are more important than the later layers opposite of the content extraction
2. Ratio is set for each of the style layer outputs
3. also alpha/beta is the ratio of content_weight/style weigh can have a big affect on the final image transfer

## Initializing the Input Image (Inputs)

1. Initializing the Input Image
2. This can be random noise for an image but we will be taking the clone of the content image
3. Using the requires_grad_(True) parameter to optimize the input image wrt to style and content images.

## Declaring the *"Adam"* optimizer to the Input image.

1. show_every = 300, to show our style transfer progress at every 300 steps.
2. Initializing the optimizer to optimize the input image
3. Run the optimization for 300 steps to get decent results

## Optimization and loss calculation

1. Create a loop to optimize for "steps" count.
2. calculate the features using the input image and VGG model.
3. calculate the content loss using MSE.

    $$Content Loss =  mean((target - Input)**2)$$

    - Here the target is the predicted value from the content image with pre-trained weights and bias, (like the one image where to want to copy the content from eg image of a cricketer MS Dhoni here.)
    - Input is the randomly initialized image  (starting with randomly initialized value and trying to minimize the loss with respect to the content image (target) so that we capture/copy good features from the content image to the randomly initialized image.
4. calculate the style loss
    - Calculate the gram matrix for input image and the target image at each of the convolution (the one which is randomly initialized and the style image)
    - At each step calculate the difference between the two and MSE on top of it calling the style loss function and sum it up at the end of all conv blocks

    $$Style  Loss = mean((gram_matrix(y) - grammatrix(t))**2)$$

5. Calculate total loss and apply the weights

$$totalloss = contentloss + styleloss *styleweight$$

6.  Update the gradients with respect to the input image

- These input image is optimized  to make it  similar to the content image at the chosen convolution (5th out of 16 here in this example, can be anything) and style is optimized from the style image using the loss optimization at each of the chosen convolution.

Here Loss is calculated after each convolution using the Style Loss function

The gradients are calculated, loss with respect to input image and not the parameters like (W and b in neural networks).

## Final Output

![https://s3-us-west-2.amazonaws.com/secure.notion-static.com/be3f8eea-1708-44e4-bf52-099c0c315dcb/Untitled.png](https://s3-us-west-2.amazonaws.com/secure.notion-static.com/be3f8eea-1708-44e4-bf52-099c0c315dcb/Untitled.png)


text:
Saxondale

ETags for assets that are delivered with Rails controllers

#####Purpose

The assets in FedoraCommons are expensive to load.  This gem uses Rails conventions
to cache and compare the hashes of ETags.

#####Add to your Gemfile

```ruby
  gem 'saxondale'
```

#####Examples

```ruby
# app/controllers/image_controller.rb
etag :thumbnail

def thumbnail
  @image = Image.find(params[:id])
  authorize! :read, @image
  data_stream = @image.datastreams['thumbnail']
  send_data data_stream.content,
    filename: 'thumbnail',
    disposition: :inline,
    type: ds.mimeType)
end
```

```ruby
 # app/models/image.rb
  expire_etag :thumbnail

```

repository: atomical/saxondale

repo_name: atomical/saxondale


text:
# Shell completion

To enable tab completion for the `gdk` command in Bash, add the following to your `~/.bash_profile`:

```shell
source ~/path/to/your/gdk/support/completions/gdk.bash
```

For Zsh, you can enable Bash completion support in your `~/.zshrc`:

```shell
autoload bashcompinit
bashcompinit

source ~/path/to/your/gdk/support/completions/gdk.bash
```

repository: nberveiler/gitlab-development-kit

branch_name: refs/heads/main

repo_name: nberveiler/gitlab-development-kit


text:
---
title: ICoinExClientSpotApi
has_children: true
parent: Rest API documentation
---
*[generated documentation]*
`CoinExRestClient > SpotApi`
*Spot API*

***
*Get the ISpotClient for this client. This is a common interface which allows for some basic operations without knowing any details of the exchange.*
**ISpotClient CommonSpotClient { get; }**
***
*Endpoints related to account settings, info or actions*
**ICoinExClientSpotApiAccount Account { get; }**
***
*Endpoints related to retrieving market and system data*
**ICoinExClientSpotApiExchangeData ExchangeData { get; }**
***
*Endpoints related to orders and trades*
**ICoinExClientSpotApiTrading Trading { get; }**

gha_language: C#

gha_license_id: MIT


text:
---
redirect_from:
  - /competition-simulator
  - /programming/simulator
layout: page
title: Simulator
---

# Simulator

## Installation

### Prerequisites

You need to download and install [Webots](https://cyberbotics.com/#download) (the download is around 300MB).
This is the platform we run our simulation in.

Versions "R2022b" and "R2023a" of Webots are supported.
*Note*: versions of the simulation prior to sr2023.3 did not support Webots "R2023a".

#### Python Version

You will also need Python installed.

| Platform | Supported Python Version |
|----------|--------------------------|
| Windows  | 3.8-3.10 (64-bit)        |
| macOS    | 3.8-3.10                 |
| Linux    | 3.8-3.10                 |

There are a small number of [external libraries]({{ site.baseurl }}/programming/python/libraries#simulator)
which will be available to your robot code during the competition. Note that for
local development you will need to install these yourself.

### Installing the simulation

1. Create a directory, perhaps called `simulation` where you will store your robot code.
2. [Download the simulation](https://github.com/srobo/competition-simulator/releases/download/sr2023.5/competition-simulator-sr2023.5.zip), the latest version is sr2023.5, released on 2023-02-22.
3. Unzip the simulation as a subdirectory of the directory you created in the first step:
    ```
    simulation
    ├── competition-simulator-<version>
    │   ├── ...
    │   └─ worlds
    │       └── Arena.wbt
    └── robot.py
    ```
    If there is not an existing `robot.py` an example one will be created when the simulator first runs.

4. Using the Webots IDE, open the `worlds/Arena.wbt` file.

You may receive a warning about your computer's GPU not being good enough, which can be ignored.

  On recent versions of macOS you may need to give Webots permission to access the directory where you have extracted the simulation files.

#### Changing your version of Python

If webots is not picking any version of Python or is picking up the wrong one then you'll need to change it.
When this happens Webots will print errors to its console and your robot will not move.

You will need the full path to the version of Python that you want to use.
This will vary based on the system you have.
One way to find the path is by launching the version of Python that you want to
use and running the following code:

~~~~~ python
import sys
print(sys.executable)
~~~~~

On Windows you can set the path to the Python version to use in Webots UI via
**Tools** → **Preferences** → **General** → **Python command**.
Your Python path is likely similar to `C:\Users\<USERNAME>\AppData\Local\Programs\Python\Python39\python.exe` when using Python 3.9, where `<USERNAME>` is your login.

On Mac you can set the path to the Python version to use via **Webots** → **Preferences** ⌘,.
Your Python path is likely similar to `/Library/Frameworks/Python.framework/Versions/3.9/bin/python3` when using Python 3.9.

You'll need to ensure a matching version of Python is installed. If you're still
having problems, ask for help in [`#simulator-help`][simulator-help] in
[Discord][discord].

### Updates

Occasionally, we may release an update to the simulation. To update, you will need to delete the `competition-simulator-<version>` directory, and re-download it using the above link.

If you need a specific version of the simulator, or want to see what changes
have been made with each version, please see the
[list of releases](https://github.com/srobo/competition-simulator/releases).

[discord]: {{ site.baseurl }}/team_admin/discord
[programming-help]: https://discord.com/channels/900501415548579842/900501416269971457
[simulator-help]: https://discord.com/channels/900501415548579842/900501416269971458

## Overview

Within the Webots IDE, there are a few different panels:

- In the centre of your screen is the 3D simulated view of the arena
- On the left is a tree hierarchy of all elements in this "world"
- At the bottom is the console, where output from your robot code will be displayed
- At the top are your general controls which include the time controls. Press the centre play button to run the simulation at normal speed.

### Useful links

- [Camera Controls](https://www.cyberbotics.com/doc/guide/the-3d-window#navigation-in-the-scene)
- [Graphics settings](https://www.cyberbotics.com/doc/guide/preferences#opengl) (Useful if Webots is running slowly)

## Time

In the simulated environment, time advances only at the pace that the simulator
is run. The relation between this time and the real passage of time depends on a
couple of factors: the speed the simulation is configured to run at and the
ability of the computer running the simulation to process it fast enough.

You can configure and observe the speed the simulator is running at from the toolbar in webots:

![]({{ site.baseurl }}/images/content/simulator/speed-toolbar.png)

Here the simulation has run for 13.28 seconds, but is currently paused (the
speed multiplier shows 0.00×). You could choose to step a single time increment,
run the simulator at real speed (▶), or run the simulator at various faster
speeds (▶▶ and ▶▶▶).

These differences mean that your code will need to use a different mechanism to
find the current time or to sleep within the simulation. Find out more by
heading over to the [simulator programming docs](./programming).

## Programming

Once you have the simulator installed you can begin [programming your robot](./programming) in the simulator.

repository: srobo/docs

gha_language: HTML

repo_name: srobo/docs


text:
# CHASS
Code Hide And Seek Surveillance

A user friendly CLI debugging tool exclusively for bash scripts.
## Table of Content
* [Installation](#installation)

* [Usage](#usage)

   * [Default Mode](#default)

   * [Variable Mode](#variable)

   * [Variable Line Mode](#line)

   * [Code Line Mode](#code)

   * [Code Segment Mode](#codeline)

   * [Debug Particualar section Mode](#breakpoints)

   * [Function Mode](#function)

   * [Printall Mode](#printall)

   * [Printall Variable Mode](#printall_variable)

   * [Loops Mode](#loops)

   * [Conditions Mode](#conditions)

   * [Sed Mode](#sed)

   * [Actual Output Mode](#output)

   * [Expression Mode](#expr)

   * [PWD Mode](#pwd)

   * [Code at any point in Default Mode](#c)

   * [Quit](#quit)

* [Limitations](#limitations)

* [Contributing](#contributing)

---

## Installation

If you don't have virtualenv installed
```bash
sudo pip3 install virtualenv
```
Now make a virtual env inside the repo
```bash
python3 -m venv chassenv
```
Activate the virtual env
```bash
source chassenv/bin/activate
```
Now install the chass package
```bash
python3 -m pip install .
```
---

## Usage
For all options available

```bash
chass --help
```

File path is the argument that must be provided.

  #### Default mode():

   Get the value of changed variables lines by line (functions are to be dealt with separately using function mode given below)

   ```bash
   chass {path-to-file}
   ```

   #### Variable mode():

   Get the value of specific multiple variables line by line

   ```bash
    chass {path-to-file} --variable={variable-name_1} --variable={variable-name_3_(optional)}
   ```

   or

   ```bash
   chass {path-to-file} -v {variable-name_1} -v {variable-name_2_(optional)}
   ```

   #### Variable at given line mode():

   Get the value of a specific variable at a specific line

   ```bash
   chass {path-to-file} --variable={variable-name} --line={line-number}
   ```

   or

   ```bash
   chass {path-to-file} -v {variable-name} -l {line-number}
   ```

   #### Code at a given line mode():

   Get code at a specified line
   ```bash
   chass {path-to-file} --code {line-number}
   ```
   or

   ```bash
   chass {path-to-file} -c {line-number}
   ```

   #### Get Particular segment of your code :

   Get a particular section of code present between two line numbers

   ```bash
   chass {path-to-file} --codeline {start-line-number} {end-line-number}
   ```

   #### Debug only a particular section of your code :

   Debugs only the section present between two line numbers

   ```bash
   chass {path-to-file} --breakpoints {start-line-number} {end-line-number}
   ```

   #### function mode() :

   Debug a function by providing the name of the function

   ```bash
   chass {path-to-file} -f {function_name}
   ```
   or

   ```bash
   chass {path-to-file} --function {function_name}
   ```

   #### printall mode() :

   Prints all the changed variables' values at every line in one go

   ```bash
   chass {path-to-file} --printall
   ```
   or

   ```bash
   chass {path-to-file} -p
   ```

   #### printall values of given multiple variables mode() :

   Prints values of the given multiple variables at each line in one go

   ```bash
   chass {path-to-file} --printall --variable={variable_name_1} --variable={variable_name_2(optional)}
   ```

   or

   ```bash
   chass {path-to-file} -p -v {variable_name_1} -v {variable_name_2(optional)}
   ```

   #### loops mode():

   Debug only loops iteration wise

   ```bash
   chass {path-to-file} --loops
   ```

   or

   ```bash
   chass {path-to-file} -r
   ```

   #### conditions mode():

   Debug only conditions line by line

   ```bash
   chass {path-to-file} --cond
   ```
   or

   ```bash
   chass {path-to-file} -i
   ```

   #### Debugging only sed commands mode():

   Debug only sed commands. You can specify line_number also to debug a specific sed command

   ```bash
   chass {path-to-file} --sed -l {line_number}(optional)
   ```

   or

   ```bash
   chass {path-to-file} -s -l {line_number}(optional)
   ```

   #### get actual output :

   Shows the actual output of the file

   ```bash
   chass {path-to-file} --output
   ```
   or

   ```bash
   chass {path-to-file} -o
   ```

   #### EXPRESSION MODE ():

   At any given line you can write valid syntax bash expression involving any of defined variables. We will give value of that expression by using values of variables upto that line

   Step 1 :
   write expr in the default mode() at any line (Note: line should not be in any loop,if and case)

   ```bash
   expr
   ```

   Step 2 :
   write the expression in bash syntax

   ```bash
   {expression_to_be_calculated_in_valid_bash_syntax}
   ```

   #### PWD mode():

   At any line inside default mode() you can print working directory (Note: line should not be in any loop,if and case)

   ```bash
   pwd
   ```

   #### Get code of any particular line in Default mode():

   At any line inside default mode you can get the line written by you in the original code by just typing "c"

   ```bash
   c
   ```

  #### Quit():

  You can exit the process at any stage by typing quit. If you are inside any loop, a single quit will get you out of the loop and typing quit again will terminate chass

  ```bash
   quit
   ```

---

## Limitations

1. Absolute File paths should be given everywhere inside the code
2. Avoid using recursive functions for best usage
3. Any String should not contain " sed ", " cd " and other keywords as a part of it
4. Syntax of the file is assumed to be correct
5. rm command should not be present inside file

---

## Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.


text:
# android-mvp-movies-app
### This is a movies Android sample app in java. It shows basics of MVP architectural pattern.

# Architectural approach: Model-View-Presenter (MVP)

![gitDiagramCapture](https://user-images.githubusercontent.com/49270391/55721947-69589b00-5a0d-11e9-862a-342852128c82.PNG)

# Project layer structure

1. **Data layer**:  It contains POJOs and means to get Data from cloud or local storage.

2. **Domain layer**: It contains all business logic and interact between Data and Presentation layer - via interface and interactors.

3. **Presentation layer**: It contains Activities, Fragments and views, which will only handle rendering views and will follow MVP pattern.

#### Used libraries:
1. [Retrofit](https://github.com/square/retrofit)
2. [Gson](https://github.com/google/gson)
3. [Picasso](https://github.com/square/picasso)
4. [RoomDatabase](https://developer.android.com/topic/libraries/architecture/room)

#### Used data from:
- [themoviedb](https://www.themoviedb.org) - A database for movies and TV shows.

# Demo screenshot

## Contributing
If you want to contribute to this project check if there are any open issues
or just send a pull request and I'll do my best to look at it

### License
```
  MIT License

Copyright (c) 2018 Julie Dai

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
```

repository: julietadai/android-mvp-movies-app

repo_name: julietadai/android-mvp-movies-app


text:
# Deploy to Kubernetes

## Add API

- 👉"one" APIM
  - 🖥no APIs
- 👉"httpbin" web app
  - 🖥container
  - 📢new integration with APIM
  - 🖱link and export to APIM
    - suffix: "httpbin"
  - 📢expose only small subset of operations
  - 🖱test each op explaining its function

## Add gateway

- 👉"one" APIM (from the web app)
  - Add gateway
    - ❗name: "gateway"
    - ❗location: "Seattle"
  - 🖱gateway resource
    - 🖥gateway blades
    - 🖱Deployment
      - ❗token autogenerated using primary key with max expiry
      - 🖥changing key or expiry generates new token

## Deploy gateway

- 👉 VSC
  - 🖥APIM extension
    - 🖥API can be added in VSC
    - 🖥gateway can be added in VSC
    - 🖱set subscriptionRequired to false on httpbin API
    - 🖱rename key header and query to "api-key"
    - 🖱add httpbin API to the "Private" product
  - 🖥Minikube
- 👉 "one" APIM
  - 🖱copy create secret command
  - 🖱download yaml
- 👉 VSC
  - 🖱copy yaml to the 1-/yaml folder
  - 🖱cd into the 1- folder
  - 🖥gateway yaml and explain it
  - 🖱run command to create api-gateway namespace
  - 🖱paste create secret command to the cmd.sh and add api-gateway namespace
  - 🖱run create secret command
  - 🖱run command to deploy gateway into api-gateway namespace
  - 🖥created Kubernetes artifacts
  - 🖱run command to view pod logs
  - 🖱run command to forward service ports
  - 🖱make sure REST-Client is set to use local-api
  - 🖱call an op from REST-Client - 404
  - 🖱add httpbin API to the gateway
  - 🖱call all ops from REST-Client - 200
  - ❗cloud and local gateways use cloud backend
- 👉"one" APIM
  - 🖥show nodes and status of the gateway

## Add and test rate limit

- 👉 VSC
  - 🖥artillery rate-limit yaml
  - 📢should expect 50 200 OK
  - run artillery
    - ❗200 - 200 OK
  - 🖱add rate limit to httpbin API in before of base
    - `<rate-limit-by-key calls="10" renewal-period="1" counter-key="@(context.Request.IpAddress)" />`
  - run artillery
    - ❗50 - 200 OK

## Show telemеtry in Application Insights

- 👉Application Insights
  - 🖥application map
  - 🖥run artillery while showing live metrics

## Legend

- 👉Go
- 🖥Show
- 📢Explain
- ❗Highlight
- 🖱Click


text:
fezpak
======

Because I am the way I am the first thing what I did after I bought [FEZ](http://fezgame.com/)
is not to play it, but to reverse engineer the package format so I can listen to the
music outside of the game.

Basic usage:

	fezpak.py list <archive>                 - list contens of .pak archive
	fezpak.py pack <archive> [files...]      - create a new .pak archive
	fezpak.py unpack <archive>               - extract .pak archive
	fezpak.py mount <archive> <mount-point>  - mount archive as read-only file system

The `mount` command depends on the [llfuse](https://code.google.com/p/python-llfuse/)
Python package. If it's not available the rest is still working.

This script is compatible with Python 2.7 and 3 (tested with 2.7.5 and 3.3.2).

File Format
-----------

The .pak file format is extremely simple. It has no file magic. The "header" is
just the number of entries it contains. A entry is just a file name (with `\`
as path seperator) and the contens of the file. All integers are encoded as
little endian.

File names don't have extensions (like `.ogg`). I don't know if this has a special
reason just happens to be the way the FEZ developers named the files.

**Note:** File names may conflict with directory names. If you unpack such an archive
you need to specify `-x EXT` or `--guess-extension` to add file name extension to all
extracted files in order resolve the name confilct.

Sometimes there is the exact same file name twice in the archive. In this case the
second occurance will overwrite the first when unpacking. When the archive is mounted
as a file system name conflict resolution is a bit different. In this case `~number`
is added between the file name and the extension. `number` is the first number that
doesn't produce a confict.

I noticed that all doubled file names in the archives of FEZ contain the exact same
content, so I guess their existance is a mistake.

	┌──────────────────────────────┐
	│                              │
	│ Header                       │
	│                              │
	│    number of entries         │
	│                              │
	│ ┌──────────────────────────┐ │
	│ │                          │ │
	│ │ Entry                    │ │
	│ │                          │ │
	│ │    file name size        │ │
	│ │    file name             │ │
	│ │    file size             │ │
	│ │    file data             │ │
	│ │                          │ │
	│ └──────────────────────────┘ │
	│                              │
	│ ...                          │
	│                              │
	└──────────────────────────────┘

### Archive

	Offset  Size  Type        Description
	     0     4  uint32_t    number of entries (N)
	     1   N/A  Entry[N]    entries

### Entry

	Offset  Size  Type        Description
	     0     1  uint8_t     file name size (N)
	     1     N  char[N]     file name, the path seperator is "\"
	   N+1     4  uint32_t    file size (S)
       N+5     S  uint8_t[S]  file data

Related Projects
----------------

 * [psypak](https://github.com/panzi/psypak): unpack, list and mount Psychonauts .pkg archives
 * [bgebf](https://github.com/panzi/bgebf): unpack, list and mount Beyond Good and Evil .bf archives
 * [unvpk](https://bitbucket.org/panzi/unvpk): extract, list, check and mount Valve .vpk archives
 * [u4pak](https://github.com/panzi/u4pak): unpack, list and mount Unreal Engine 4 .pak archives
 * [t2fbq](https://github.com/panzi/t2fbq): unpack, list and mount Trine 2 .fbq archives

BSD License
-----------
Copyright (c) 2014 Mathias Panzenböck

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.

repository: dashxdr/fezpak

repo_name: dashxdr/fezpak


text:
# Integration Testing Analysis and Failure Report

In integrating the buy, sell and update features into the current build, some considerations to the current project template were made.
Specifically, previous modifications which were made to drop all data from the database each time the server was started, were reverted.
We then get that database entries persist between test cases using the regular "server" pytest fixture. A new pytest fixture was
created (in Web-App/qa327_test/conftest.py), called "fresh_server", where, when used, database entries are dropped between test cases.
This fixture was used for the integration testing.

Integration testing was implemented in three test cases, the first of which follows the path of a user registering, logging in,
and posting a ticket for sale. In the second test case, as a setup we recreate the selling path from the first test case (wihtout
any of the assertions), then, logged in as the same user, we attempt to update ticket information for the ticket we just sold.
In the last test case, we once again set up the test case with the ticket selling path, then follow the path of a second user registering,
logging in, and buying the tickets listed from the first user.

In implementing and running these test cases, multiple failures were encountered which lead to some drastic changes in the buy, sell and
update backend functions, which were previously simply mocked in testing and were not implemented properly. Failures and their appropriate
fixes are documented below.

### Failure Report

#### Ticket Selling
* Failure in selling path, SQLAlchemy IntegrityError
    * We had persistent ticket data from a previous testing, and we can't sell two tickets from same account
        * Fixed by decorating integration test with "fresh_server" fixture
        * Fixed by removing UNIQUE constraint to Tickets "email" field in database (in models.py)
        * Added proper error handling in frontend /sell POST for selling tickets of name already listed

#### Ticket Updating
* Ambiguous specifications while implementing test case; what exactly are we updating?
    * Going forward, assuming we specify a ticket name to update (from your own listings)
    * Other fields (quantity, price, expiry date) are the values to change
    * Updated field labels in index.html to make this functionality more obvious
* Previous fix of making ticket email non-unique breaks current implementation
    * Fixed by adding UNIQUE constraint to (email, name) pair in Tickets table, in models.py
    * Re-implemented backend function to properly query for, and update the specified ticket
    * Added extra error handling in frontend /update POST
    * Added proper error handling in frontend /sell POST for selling tickets of name already listed
        * Retroactive /sell path fix needed, since new (email, name) UNIQUE constraint can throw more IntegrityError's

#### Ticket buying
* Failure in ticket buying: backend function is not implemented
    * Implemented backend.buy_ticket
    * Migrated calls to validateEnoughTickets and validateBalanceEnough from frontend to backend
    * Fixed with proper querying of database by ticket name
        * Iterates through through results, sorted by price
        * Buys from first result with sufficient quantity (which will be cheapest option)
    * Returns error message, if any, to frontend
* Failure in user balance deduction: invalid operation between database Numeric type and python float
    * Fixed by converting total ticket price to Decimal before deduction, in backend.buy_ticket
    * Also applied conversion to test case implementation accordingly

#### Previous testing failure
* From having changed a few backend function return styling (returning error message string instead of True/False)
    * Updated backend patching accordingly
* From having changed html template (exact wording of headings/text)
   * Updated appropriate assertions in test cases accordingly


text:
django-pubsub-couch
===================

This is a Django PubSubHubbub module using CouchdB as a backend.

Code is at:

    https://github.com/stefankoegl/django-pubsub-couch

A fork of

    https://git.participatoryculture.org/djpubsubhubbub

License information is in the LICENSE file.

repository: stefankoegl/django-pubsub-couch

repo_name: stefankoegl/django-pubsub-couch


text:
# Required Files:
To reproduce a calculation from Hsu et al. (2019), you will need the following data files (under the 'data' sub-directory of the repository):
* "DR25topwinfuncs.jld": Summary of window function data taken from the DR25 Completeness Products
* "dr25fgk_osds.jld": One-sigma depth functions for the filtered catalog of Kepler planet search targets (Not part of the repository, download from: https://scholarsphere.psu.edu/resources/460cb19b-86e9-4c04-ac17-69950444437f).
* "KeplerMAST_TargetProperties.csv": Summary of key properties for Kepler Targets that are not included in the other catalogs.
* "q1q17_dr25_gaia_fgk.jld": Filtered DR25 stellar catalog of FGK targets (see Hsu et al. 2019 for explanation of cuts).
* "q1_q17_dr25_koi.csv": DR25 KOI catalog with transit depths replaced with median depths from the MCMC posterior chains.

# Running Calculation:
To perform the actual calculations, you run:
```
> julia abc_run.jl
```

This defaults to computing a planet candidate occurrence rate and rate density for 5 period-radius bins spanning 0.5-1.75 R_Earth and 237-500 days.
For other ranges, you'd edit the values of p_bin_lim and r_bin_lim in param.in.