text:
# Douglas Hadje --- 2325

> **May Then My Name Die With Me:** I am surprised to see you online, Douglas!
>
> **Douglas Hadje:** Remember how I said my workload as launch director would be starting to decrease after launch?
>
> **Douglas:** Well, now I'm only working a few days at a time, and most of that is writing up documentation and collating reports for the launch commission. Soon, even that will disappear, and I suspect I'll be out of a job unless I decide to take on another position.
>
> **May Then My Name:** Do you think that you will?
>
> **Douglas:** I don't know. Maybe? Probably. Once I'm out of a job, my reason to be here is kind of gone, and I imagine whatever goodwill I've built up will start to run out and they won't let me stay on the station. It's mostly self-sufficient, but resources are limited and I'm sure there's someone who would like to take my spot.
>
> **Ioan Bălan:** And you mentioned not wanting to go back planet-side.
>
> **Douglas:** God no, not if I can help it.
>
> **May Then My Name:** Either way, I am happy to see you about. Did you have any particular topics you wanted to discuss today? If not, I am sure that Ioan has some.
>
> **Douglas:** Nothing in particular. I've got a few minor questions outstanding, I think, but I'm starting to get the sense that you'll only answer those when you're ready.
>
> **May Then My Name:** That is a very good sense that you have.
>
> **Ioan:** May's obstinate, ignore her.
>
> **Ioan:** She also kicks pretty hard, but then, I deserved that.
>
> **May Then My Name:** You did.
>
> **Ioan:** Alright, well, the topic I was thinking of asking you about is that of the political side of the launch. One of the instances on one of the launches conducted an interview that suggested that there was actually quite a lot of political machinations behind the scenes.
>
> **Douglas:** Oh! Yes! I'm surprised you didn't get much news of that in there.
>
> **May Then My Name:** I am sure that we could look it up, but you are in a unique position to tell us more directly, and after it has been all mixed around in your head.
>
> **Douglas:** True. Well, where do you want to start?
>
> **Ioan:** How about you start most recently, actually, and then work your way backwards.
>
> **Douglas:** Alright.
>
> **Douglas:** There was one last spate of protesting right before the launch. I saw some of the videos from planet-side, and a lot of it was just talking-heads discussing the fact that some had tried to shut down portions of the net, and even tried to take down one of the Ansible stations. Most of it was the same stuff we saw during the planning phase. I guess it kind of broke down into three complaints:
>
> **Douglas:** 1. Expenses --- this one was diminished toward the end, as there's not really a whole lot of expense required in popping some explosive bolts to set the launches flying, and all the material used out here was from scavenged Trojan asteroids. The protests that we saw around this were mostly griping about how much had already been spent. "Think of how much could have gone to deacidifying projects, etc etc"
>
> **Douglas:** 2. Brain/workforce drain --- This is a perennial topic with the system. All those smart minds out there focusing on pie-in-the-sky dreams instead of 'real problems' back there on Earth. What they imagine someone with a masters in spaceflight or astronomy or whatever can do back on Earth to better an overheated dustball is beyond me.
>
> **Douglas:** 3. Earth vs space sentiments --- This one is probably the most common, and also the hardest to explain. Even I don't totally understand it. I think I mentioned before that, the harder things get, the less time and energy you have to focus on those pie-in-the-sky ideas. You're too busy scraping by or focus on growing soybeans or trying not to burn up or whatever, you don't have much time to do anything but dream about space and watch movies in your hour before bed or however your day looks.
>
> **Douglas:** You have to remember that my opinion of the place is colored by the fact that I lived where I did with the family that I did while the city was in a state of decline, so.
>
> **Douglas:** Anyway, a lot of these people seemed to be just plain angry that there were people doing things that were not for helping improve the general condition of life. There's still six or seven billion people down there, when you mesh birth rates with death and upload rates, and a good chunk of those people have no wish to upload, so they're stuck in a life that's uncomfortable enough to make them angry at those who have what feels like (and might as well be) unlimited potential, as they imagine the System to be.
>
> **Douglas:** Does that make sense?
>
> **Ioan:** I think so. You've got people who are unhappy, and part of that unhappiness is the fact that others are happy.
>
> **Douglas:** More than that. They're unhappy, and part of that is that those others are not helping to make life better for them. It's usually not even making life better for humanity, but for them specifically, for the world as they specifically view it.
>
> **Ioan:** Was there any sentiment that they were being abandoned by those who left on the launches?
>
> **Douglas:** Yes and no. You have to understand that most people still struggle to think of the uploads as human. Thus calling them 'uploads', even, rather than 'uploaded personalities' or whatever. It's not just shorthand, it's a way of separating them into some other idea. They aren't people, anymore, they're programs, in their minds.
>
> **May Then My Name:** There has always been this argument of speciation, and the instinct to make us the other continues apace, I see.
>
> **Douglas:** I'll take your word for it. It's difficult to persuade the average person that those in the System are still human, or if not human, then at least still people. They're not the types to listen to all the arguments for why we know that you're still you after you upload. They duck-type you into being programs.
>
> **May Then My Name:** 'Duck-type'?
>
> **Ioan:** Looks like a duck, quacks like a duck, must be a duck.
>
> **Douglas:** Is that what it means? It's just come to mean a false-equivalency of any kind. Few enough ducks, anymore.
>
> **Ioan:** I only learned it from an assignment talking with some perisystem specialists.
>
> **Douglas:** I guess it doesn't surprise me that you have those inside as well as outside. Sometimes, I get these little jolts about how little I actually know about the System, compared to how much I know about the launch.
>
> **May Then My Name:** It does not help that many of us --- not just me --- are obtuse on purpose.
>
> **Douglas:** You said there was some grumbling sys-side, as well, right?"
>
> **Ioan:** Yes, though I don't totally understand it. Some of it sounds like that like, "Why bother? We've got a good life here, and there's no reason to be putting that in any kind of danger just to throw copies of us out at the stars." The bits that I mentioned earlier, however, have more to do with the Dreamer Modules than the launch itself, though.
>
> **Douglas:** Oh? There was a little bit of chatter about those here, but I didn't pay a whole lot of attention to it.
>
> **Ioan:** That's okay. I'll dig, myself.
>
> **May Then My Name:** We were working backwards from present. Was there much in the way of disruptions in the middle of the launch construction process?
>
> **Douglas:** Not as much, no. There was a lull in overall protests. A lot of the grumbling about the Dreamer Module came during this time. There were one or two other sabotage attempts. Do you want to hear about those?
>
> **May Then My Name:** We will, yes, but there is time. For now, we are curious about the macro-scale political landscape before, during, and after launch.
>
> **Douglas:** Alright. That'll give me some time to remember more about what happened with them.
>
> **Douglas:** Large scale, hmm.
>
> **Douglas:** Well, most of the government side goes way over my head. In the WF, there was always a bit of waffling, even on the majority coalition side, but whenever sentiment in a member party of the majority drifted away from the launch, they never seemed to last all that long in power.
>
> **Douglas:** I talked about protests and sentiments before, but for the most part, folks were either on board, didn't care, or didn't know about the launch. It was just another satellite in their eyes, or some deep space probe.
>
> **Douglas:** Early on was when it was talked about most. There wasn't a whole lot of questions asked about whether or not the launch would happen, weirdly. I remember it just kind of popping up in the news as a foregone conclusion. "The launch was happening, how's everyone feeling about that?"
>
> **Douglas:** I think some were pretty unhappy with that, at first. Like, where did this decision even come from? Obviously, the System is its own authority and can do whatever it wants, but someone has to manage the phys-side work, so who, phys-side, actually had those conversations? There were a few gestures at investigation, but they fizzled out. Mostly, people were just confused. Some people get upset when they're confused, but for the rest, it just left them shaking their heads. It was the politicians who were dealing with it after that initial shock.
>
> **Douglas:** Building the launches wasn't too expensive, honestly, because almost all of that was done in an automated fashion here on the station. That said, retrofitting the station for the launch struts, building the launch arms, expanding the production sector...all that took time, energy, and money. I'm surprised it went as smoothly as it did, despite all the grumbling.
>
> **Ioan:** So it just popped up on the scene, then interest waned, then ramped up before the launch, then dropped? Like an 'M' shape?
>
> **Douglas:** I suppose so, yeah. After the launch happened, there was nothing that could be done, so everyone lost interest or lost steam in their protests.
>
> **May Then My Name:** We had a conversation a while back about our own point of no return. It was actually a year and change before the launch itself. By then, individuals were already transferring, and even if something went wrong, the cheapest solution would have been to launch anyway, and just take the hit on final velocity.
>
> **Ioan:** Really?
>
> **Ioan:** It makes sense, I suppose. What would you have done? Un-built the struts/arms and LVs?
>
> **Douglas:** Basically. That would require dealing with yet more conservation-of-momentum issues, which would've required more money to build *that* infrastructure, etc etc.
>
> **Douglas:** None of which really seemed to matter to the protestors.
>
> **May Then My Name:** You said that parties whose sentiments veered away from supporting the launch often wound up leaving the leading coalition. What was the general sentiment of the leading coalition in the WF? Elsewhere on Earth?
>
> **Douglas:** Oh, good question. I guess most of them wound up being the types that pushed for higher taxes while playing to humanity. They're all named something different, I guess. It was the liberal democrats for most of the time in the WF. The demsocs felt that the money that was going to the launch was better served on Earth. The libertarians were here and there on the issue. Sometimes they felt like it would be a net win for humanity, sometimes they felt like the burden of the launch was too much. The conservatives spent most of the last twenty years as the shadow government. Their arguments were mostly what I said before. It was money that was going to a thing that wasn't them or their financial interests.
>
> **May Then My Name:** The way you talk, I assume that you are a liberal democrat?
>
> **Douglas:** We don't get a vote up here.
>
> **Douglas:** I'm with whatever party allows the System to continue and helped the launch move forward.
>
> **May Then My Name:** A single issue voter, then?
>
> **Douglas:** I guess so!
>
> **Ioan:** Well, we appreciate that, given where we live.
>
> **Douglas:** Haha, well, good.
>
> **Douglas:** Any other questions? I don't have any in particular, and would like to go grab dinner.
>
> **Ioan:** Not from me.
>
> **May Then My Name:** When will you be uploading, Douglas?
>
> **Douglas:** I don't know. Some day, I promise.
>
> **May Then My Name:** When you do, I hope that you will tell us, so that we can meet you face to face.
>
> **Douglas:** Of course! After all this time, I'd be disappointed if we didn't.
>
> **May Then My Name:** We will have many stories to tell you.
>
> **Douglas:** I look forward to them all. Goodnight, you two.
>
> **Douglas:** Or morning.
>
> **Ioan:** Afternoon, actually. Enjoy your dinner!

repository: makyo/writing

gha_language: TeX

repo_name: makyo/writing


text:
# Mr.Roboger Neighborhood

#### User type the number to get the result, Created 06/12/2020

#### Created by Mook Dang

## Description
User type whatever number they want to see the result.

## Behavior Driven Development

| Behavior | Input | Output |
| -------- | ----- | ------ |
| The program returns a range of numbers from 0 to the users inputted number | "4" | "0,1,2,3,4" |
| If a number contain a one | "1" | Beep! |
| If a number contain a two | "2" | Boop! |
| If a number contain a three | "3" | "Won't you be my neighbor?" |
| The exceptions number are written from least to most important | number 13 | Replaced with "Won't you be my neighbor?" |
| The exceptions number are written from least to most important | number 23 | Replaced with "Boop!" |
| If user enter number beside exceptions number | "5" | "5" |

## Links

## Setup/Installation Requirements

1. Open up the application on Web-brower
2. Type any number wanted
3. The return will give back depend on what number is inputted

## Known Bugs
No Known Bugs - 06/12/2020

## Support and contact details
For support contact Mook Dang

## Technologies Used
Used HTML, CSS, jQuery and Bootstrap

### License

Copyright (c) 2016 Mook Dang

This software is licensed under MIT license.

license: MIT

repository: mookdang/mr-roboger

branch_name: refs/heads/master

extension: md

license_type: permissive

repo_name: mookdang/mr-roboger


text:
---
title: "Mathematics for Engineers II"
subtitle: "Spring 2020"
summary: University of Cyprus, School of Mathematics
date: "2020-01-12"
slug: "mas026-spring2020"

reading_time: false  # Show estimated reading time?
share: false  # Show social sharing links?
profile: false  # Show author profile?
comments: false  # Show comments?

# Optional header image (relative to `static/img/` folder).
header:
  caption: ""
  image: ""
---

Mathematics for Engineers II is a course offered to the students of the three Engineering Departments of the University of Cyprus. Its content is that of a multivariable calculus course, namely vectors in n-dimensional spaces, limits and continuity of multivariable functions, differentiability and extrema, multiple integrals, line and surface intergrals, fundamental theorems of vector calculus (Green, Stokes, Gauss).

The content for the course can be found (in greek) [here]({{< relref "ucy-mas026-spring2022.md" >}}).

repository: st-dimopoulos/academic-kickstart

gha_license_id: MIT

repo_name: st-dimopoulos/academic-kickstart


text:
Nominatim Docker container
==========================

Fully-featured container for geocoding, reverse geocoding and address lookup based on [Nominatim](https://github.com/openstreetmap/Nominatim) and [Open Street Map](http://www.openstreetmap.org) data.

## Table of content
- [Build](#build)
- [Run](#run)
- [Develop](#develop)

## Build
The build process is fairly straightforward, but requires lots of computer resources and can take days to complete.

To build, install [Docker](https://get.docker.com) and run following command:
```shell
docker build github.com/merlinnot/nominatim-docker \
  -t nominatim \
  --build-arg BUILD_THREADS=16 \
  --build-arg BUILD_MEMORY=32GB \
  --build-arg OSM2PGSQL_CACHE=28000 \
  --build-arg RUNTIME_THREADS=2 \
  --build-arg RUNTIME_MEMORY=8GB
```

Full list of build arguments:

| Name                  | Default | Description |
| --------------------- | ------- | ----------- |
| BUILD_THREADS         | 16      | Number of threads used during build process. |
| BUILD_MEMORY          | 32GB    | Memory dedicated to postgresql during build process. |
| PGSQL_VERSION         | 9.6     | [PostgreSQL](https://www.postgresql.org) version. |
| POSTGIS_VERSION       | 2.4     | [PostGIS](http://postgis.net) version. |
| OSM2PGSQL_CACHE       | 24000   | [osm2pgsql](https://github.com/openstreetmap/osm2pgsql) cache size in MB, should be set to about 75% of memory available during build process, to a maximum of about 30000. Additional RAM will not be used. |
| PBF_URL               | [planet](https://planet.osm.org/pbf/planet-latest.osm.pbf) | URL to OpenStreetMap data in PBF format. See [geofabrik.de](http://download.geofabrik.de) for extracts. |
| REPLICATION_URL       | [planet](https://planet.osm.org/replication/hour/) | URL to directory with periodic updates. I recommend using [geofabrik.de](http://download.geofabrik.de) (see `raw directory index` and lookup `updates`). |
| IMPORT_ADMINISTRATIVE | false   | Data provided in `PBF_FILE` might be used to import only administrative boundaries. Importing only administrative boundaries is much faster and is useful for tasks like country code reverse geocoding. |
| RUNTIME_THREADS       | 2       | Estimated number of threads available to the running container. |
| RUNTIME_MEMORY        | 8GB     | Estimated memory size available to the running container. |

## Run
To run container built in the [previous step](#build) use
```bash
docker run --restart=always -d -p 80:80 merlinnot/nominatim-docker
```
API will be available at port `80` under `/nominatim/` directory.

## Develop
This project uses [Devver](https://github.com/merlinnot/devver), but feel free to use any of your favorite editors.

For development purposes I strongly encourage to start a build process using URLs for Monacco, it makes the process much faster:
```shell
docker build github.com/merlinnot/nominatim-docker \
  -t nominatim \
  --build-arg BUILD_THREADS=2 \
  --build-arg BUILD_MEMORY=8GB \
  --build-arg OSM2PGSQL_CACHE=2000 \
  --build-arg RUNTIME_THREADS=2 \
  --build-arg RUNTIME_MEMORY=8GB \
  --build-arg PBF_URL=http://download.geofabrik.de/europe/monaco-latest.osm.pbf \
  --build-arg REPLICATION_URL=http://download.geofabrik.de/monaco-updates
```

repository: merlinnot/nominatim-docker

gha_language: Dockerfile

repo_name: merlinnot/nominatim-docker


text:
Cell Society
====

This project implements a cellular automata simulator.

Names:
Ji Yun Hyo - jh160

Shaw Phillips - sp422

Harrison Huang - hlh38

### Timeline

Start Date: February 6th

Finish Date: February 21st

Hours Spent:
Jiyun - 80 hours (weeks 1 + 2)

Harrison - 40 hours (weeks 1 + 2)
Shaw - 30 hours (weeks 1 + 2)
### Primary Roles

Shaw: I created the Decoder class along with the XMLParser and XMLException classes, which dealt with
prompting the user to select a file, parsing it, and passing the appropriate parameters to the Simulation
Engine in order to setup the simulation. I added the XML template files and setup the ability to save
the simulation's configuration. I also implemented error checking and exception handling for the XML files through the use of
JavaFX alerts.

Jiyun: I designed the overall structure of the project using StarUML. Facilitated better work
communication by integrating Gitlab to Slack (all members get notified with Gitlab notifications in
real-time through Slack). Was in charge of 1) Main.java, simulationengine package, grid package (3
parts of Controller component) and 2) entirety of Models. I also wrote the templates and its
descriptions, formatted the files according to Google format, and helped refactor parts of the
classes for better design. I also followed up with team members to facilitate communication and to
make sure we have implemented everything specified by the spec. Spent time refactoring.
Implemented classes: Main, model package

Harrison: I created the view component of the project, of which the main three components are the
SimulationScreen, GridGraphics, and SidePanel. I also had to provide functionality of the controls
put in SidePanel by coordinating with the SimulationEngine. I implemented the resource property
file and CSS file for the front end in order to have more flexibility in the display. I had
to manage the view and state of the grid, as well as allow for resizing. This was extended in the
complete version with the addition of an independent Graph view, multiple simultaneous simulations,
additional language support, and color palette functionality, among other things.

### Resources Used

1. Shaw
    - [Example XML Parser](https://coursework.cs.duke.edu/compsci308_2021spring/spike_cellsociety/-/blob/master/src/xml/XMLParser.java)
    - [XML Java Tutorial](https://www.tutorialspoint.com/java_xml/index.htm)
    - [Java FileChooser Tutorial](https://docs.oracle.com/javase/8/javafx/api/javafx/stage/FileChooser.html)
    - [Java PrintWriter Tutorial](https://docs.oracle.com/javase/7/docs/api/java/io/PrintWriter.html)
    - [ResourceBundle Tutorial](https://www.geeksforgeeks.org/resourcebundle-and-listresourcebundle-class-in-java-with-examples/)
    - [Exception Handling](https://www.tutorialspoint.com/java/java_exceptions.htm)
    - [JavaFX Alerts](https://docs.oracle.com/javase/8/javafx/api/javafx/scene/control/Alert.html)
2. Harrison Huang
    - [JavaFX Tutorial](https://zetcode.com/gui/javafx/intro/)
    - [Layout Panes](https://docs.oracle.com/javafx/2/layout/builtin_layouts.htm)
    - [GridPane Tutorial](https://www.tutorialspoint.com/javafx/layout_gridpane.htm)
    - [Slider documentation](https://docs.oracle.com/javase/8/javafx/api/javafx/scene/control/Slider.html)
    - [Changing speed of AnimationTimer](https://stackoverflow.com/questions/30146560/how-to-change-animationtimer-speed)
    - [Label text wrapping](https://stackoverflow.com/questions/30146560/how-to-change-animationtimer-speed)
    - [CSS Guide](https://openjfx.io/javadoc/11/javafx.graphics/javafx/scene/doc-files/cssref.html)
    - lab_bounce code for Resource Property and CSS
    - [Tiling hexagons guide](https://www.redblobgames.com/grids/hexagons/)
    - [Grid design notes](http://www-cs-students.stanford.edu/~amitp/game-programming/grids/)
    - [Realtime Charts in JavaFX](https://levelup.gitconnected.com/realtime-charts-with-javafx-ed33c46b9c8d)
    - [Multiseries JavaFX chart](https://www.tutorialspoint.com/javafx-line-chart-example-with-multiple-series-lines)
    - Google Translate
3. Ji Yun Hyo
    - [Branching and Merging](http://gitready.com/beginner/2009/01/25/branching-and-merging.html)
    - [Enumerated types](https://docs.oracle.com/javase/tutorial/java/javaOO/enum.html)
    - [MVC model](https://www.tutorialspoint.com/mvc_framework/mvc_framework_introduction.htm)
    - [Game of Life rules](https://playgameoflife.com/)
    - [Schelling's simulation](http://jasss.soc.surrey.ac.uk/15/1/6.html#:~:text=The%20Schelling%20model%20of%20segregation%20(Schelling%201971%2C%201978)%20is,148$)$.)
    - [WaTor Model Wikipedia](https://en.wikipedia.org/wiki/Wa-Tor)
    - [WaTor Model simulation example](https://beltoforion.de/en/wator/)
    - [Modeling and simulation](https://maxstrauch.github.io/projects/mod-sim/index.html)
    - [Four Pillars of Object Oriented Programming](https://medium.com/@benjaminpjacobs/the-four-principle-of-object-oriented-programming-f78600f62608)
    - [MVC model 2nd resource](https://www.educative.io/blog/mvc-tutorial)
    - [StarUML Documentation](https://docs.staruml.io/)
    - [Ant Foraging](https://greenteapress.com/complexity/html/thinkcomplexity013.html)
    - example_encapsulation code for refactoring
    - [Rock Paper Scissors](https://softologyblog.wordpress.com/2018/03/23/rock-paper-scissors-cellular-automata/)
    - [Arrangement of Neighbors](http://golly.sourceforge.net/Help/Algorithms/QuickLife.html#nontotal)
    - [Grid shape](https://mathworld.wolfram.com/Grid.html)
    - [Hexagonal neighborhood](https://www.conwaylife.com/wiki/Hexagonal_neighbourhood)
    - [A Systematic Approach to Write Better Code With OOP Concepts](https://dzone.com/articles/object-oriented-programming-concepts-with-a-system)
    - Liskov Substitution Principle

### Running the Program

Main class: Main.java

Data files needed: All necessary XML files are under "data" folder

Features implemented: WaTor Simulation, Percolation, Spreading of Fire, Game of Life, Segregation; 6
templates for each; simulation screen with functional start/stop/reset buttons, speed slider,
ability to load new XML files, dynamically updating and sized grid, independent grid and graph
views, multiple simultaneous simulations, simulation appearance selection in colors and language, ForagingAnt,
Rock scissor paper, different number of neighbors (3, 4, 6, 8, 12).

### Notes/Assumptions

Assumptions or Simplifications: The assumption in the beginning was that we would need a bunch of
classes for each model. However, along the way, I realized that all the models did not really need
to have a lot of the same classes. For example, I ended up getting rid of the Cell classes for all
the rules because it was evident that State and Cell performed the same thing. Also, because I came
up with the Rule abstract class, we did not need to have a separate builder for each one.
GridManager was able to take in all the parameters for all models and produce the starting states
and update the cell states successfully. Therefore, the design became much "simpler" and more
efficient than what we had initially imagined. As of the basic implementation, all three
components (MVC) are working together by informing each other of its states but do not specifically
have to know the inner-workings of each class in order to cooperate. One area that should be
a focus for potential future improvement is removing the cyclic dependency between the controller
and view, between SimulationEngine and SimulationScreen.

Interesting data files: (Jiyun) I manually tested out the templates and have selected the ones that
produce interesting results. I think all the templates are worth your time to checkout. I tried to "
model" real life situations with the models.

Known Bugs:
   - The grid resizing only works when the simulation is running, so when the simulation is
     stopped, the grid will not resize if the window size is changed.
   - When Load New is pressed but no file is selected, the program will throw a
     NullPointerException, though this does not affect the overall program functionality. The
     descriptions can also disappear too soon if a new file is not selected. The Load New button
     can be pressed multiple times before actually triggering, which can result in weird behavior.
   - The graph window doesn't plot the initial states when it is first created, though it updates
     correctly.
   - Changing the stylesheet/CSS file will result in a strange warning in the console, though this
     does not ultimately impact the overall functionality.

Extra credit: None

### Impressions

Jiyun: Personally, I really liked working on this project. I liked how Cellular Automata could be
used to simulate real-life situations. I also liked witnessing how a good design could help out
immensely throughout the project. I also appreciate everyone putting in the effort.

Harrison: I think it was really cool that we were all able to put together a working project all
while trusting each other to do our own part. While largely independent of the Model, I could focus
more on implementing features for the view and improving the UI.

repository: harrison-lh/cellsociety

gha_language: Java

repo_name: harrison-lh/cellsociety


text:
# Online Cloud Storage

藍白色系搭配的扁平風格設計；並且有整合搜尋和排序功能。

DEMO: https://easonchiang7178.github.io/f2e-cloud-storage/

---

Designed by [Letitia73](https://challenge.thef2e.com/user/1930?schedule=4169#works-4169)

gha_language: JavaScript


text:
# Changelog

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

---

## [Unreleased]

## [2.2.0] 2022-04-27

### Added

- A secondary foreground color in `Colors` (and a default value in `DefaultColors`).

## [2.1.0] 2020-08-08

### Added

- Ability to pass a custom view for app-specific debug views when installing Pippin debugging views for the menu.

## [2.0.2] 2020-04-15

### Fixed

- Use correct bundle ID in `DefaultDefaults`, `LogLevel`, `LaunchArgument` and `EnvironmentVariable` descriptions, as well as errors and internal components.

## [2.0.1] 2020-04-05

### Fixed

- Set the `Environment` reference for `Defaults` in `connectEnvironment()`.

## [2.0.0] 2020-03-08

### Changed

- Added a parameter to `AppInfoPresenter.init` to specify the logical (not direct container) parent `UIViewController`, if any, to corrently stack modally presented view controllers. For example, if an `InfoViewController` is modally presented, and it modally presents another `UIViewController`, then treat the new modal's parent as the original `InfoViewController`'s parent. This helps with layouts that use margins, so the Nth modal doesn't get shifted down by N x margin.
- Updated bundle identifier for `Pippin.framework`.
- Bumped podspec's `deployment_target` to iOS 12.0 to workaround a CocoaPods bug: https://github.com/CocoaPods/CocoaPods/issues/7111#issuecomment-589048018.

### Fix

- rDNS raw values for `LaunchArgument` members to use `Pippin.framework`'s bundle ID instead of the app, to help avoid potential collisions.

### Added

- `Colors` protocol and `DefaultColors` struct to help with Dark Mode (or more generally, configurable color systems).

## [16.0.0] 2019-09-21

### Changed

- Guard usage of debug APIs within `#if DEBUG` conditional compilation directives.
- `AuthorizedCLLocationManager` now returns a token to retain while prompting user for permission instead of the old singleton pattern.
- Moved `InfoViewController`, `CRUDViewController` and `FormController` to `PippinAdapters` spec.

### Added

- Function on `LaunchArgument` to query whether a calling case was supplied in a launch.
- `AuthorizedCLLocationManager` now returns a token to retain while prompting user for permission instead of the old singleton pattern.

### Fixed

- Improved `AuthorizedCLLocationManager` handling of possible authorization states at the time it is used to request authorization from the user.

## [15.0.0] 2019-09-18

### Changed

- Removed iOS 11 minimum requirement for `DebugController`.
- `XCGLoggerAdapter.init` is now optional, as it will return `nil` if called with the new `XCGLogger.LogLevel` cases `notice`, `emergency` and `alert`.

### Added

- Declare `Debuggable` conformance to `BugReporter`, `Logger` and `TouchVisualization` seeds.
- Extension to construct a `CGRect` centered on a `CGPoint` with a given `CGSize`.

### Fixed

- Swift 5.1 support.
- `WindowLevel` now includes a level for `TouchVisualizer`.

## [14.1.0] 2019-09-04

### Added

- A way to tell `CrudViewController` all the edit actions to show for an item cell, instead of actions to add to default Edit and Delete actions. This helps if you want Delete without Edit, or totally different set of options.
- ObjC access to `UIAlertControllerFactory` functions.

### Fixed

- `CrudViewController` now transitions to nonempty states when calling `reloadData()` that causes a fetch of newly added entities.
- New compiler warning about redun

## [14.0.0] 2019-03-20

### Changed

- Converted remaining implicitly unwrapped optionals in `Environment` to optionals.
- Make `TouchVisualization` `EnvironmentallyConscious` so it can use logging etc.
- Consolidate `FileManager` errors in an extension to get standard user directories.

### Added

- `NSErrorConvertible` protocol for Swift errors to be able to produce an `NSError` version of themselves.
- `Environment` errors for when an expected piece of infrastructure necessary for a particular function is not present, like an `InAppPurchaseVendor`.

### Fixed

- `FormController` no longer shows disabled "Next" and "Previous" buttons when only one input is currently managed.

## [13.0.0] 2019-01-29

### Changed

- Fixed up the APIs in `FileManager+URLs` for better consistency in naming and error throwing.

### Added

- Extension on `CGFloat` describing the amount of alpha a disabled UI element should have.
- Teach `UIFont` instances how to grow a bit bigger or smaller.
- New parameter on `CoreDataController.save(context:)` to provide a custom failure message to display in an alert and in the logs.
- Expose more extensions to `public` and also explicitly declare a few `internal` and `private` ones that were missing any protection type.

## [12.1.0] 2019-01-09

### Added

- `CompoundOperation` and test/demo code ported from [FABOperation](https://github.com/google-fabric/faboperation).
- JSON extensions for `Dictionary`, `String` and `Data`.
- Reusable `ColorGradientLayer` and `ColorSliderCell` subclasses of `CALayer` and `UITableViewCell`, respectively.
- Function to split an `Array` into subarrays of a specified size.
- Function to test if an object instance is one of a set of types.
- `Model` seed protocol.
- Taught `UITableViewCell` how to draw a cell separator on its top edge.
- Let `Date.elapsedTime(since:)` default to time since now if called with no parameter.
- Taught `Dictionary` how to initialize from a Plist file, as well as how to return a list of its keys ordered by their associated values, or an array of `(key, value)` tuples ordered by key, in various ways.
- Definitions and a `String` extension function to parse CSV files.
- Add a way to insert a new key/value pair into a `Dictionary`, or if there's already a value mapped to the key, a way to update the value using a block.

### Fixed

- When `AsyncOperation`s are cancelled in-flight, their `completionBlock` inherited from `Operation` is not executed, in accordance with `Operation`'s behavior.

## [12.0.1] 2018-10-29

### Fixed

- Remove all pod dependencies (so, just Anchorage) from `Pippin/Extensions` subspec.
- Rename Core subdirectory to Seeds, to disambiguate between the Core subspec and the subdirectory containing the Core protocols and data structures.

## [12.0.0] 2018-10-25

### Changed

- Adapters to Pippin protocols now live in the separate `PippinAdapters.podspec`.

## [11.0.0] 2018-09-23

### Changed

- Make `Defaults` `EnvironmentallyConscious`.
- Functions on `ActivityIndicator` to show and hide UI now have completion block parameters.
- In `Environment.logLevel`, always return `LogLevel.verbose` when running UI tests.

### Added

- Extension on `UserDefaults` to set and a key/value pair and immediately synchronize the backing store.
- Parameter to specify a title font on `UIButton` factory function, and use it in `InfoViewController` for the app detail stack buttons.
- `TouchVisualization` protocol and `COSTouchVisualizer` adapter.
- Parameterize `DismissableModalViewController`'s insets instead of hardcoding it to inset by 30 from the top to avoid a status bar, something not all apps may want to do.
- Extension on `UIView` to round corners and style borders.
- Keep a reference to the `Bundle` containing any shared assets catalog, which defaults to the main bundle if one isn't specified in `Environment`'s init.
- A `LaunchArgument` to wipe any stored user defaults the app uses at launch.
- A static extension function on `ProcessInfo` to test if any launch argument was provided during app launch, to help test app-specific launch arguments.

### Fixed

- Fixed layout issues in `DismissableModalViewController` when there is no title to display or in less than full-screen layouts.
- `Date+TimeElapsed` now returns sub-minute scale results as a string describing seconds elapsed.
- `InfoViewController` now shows in-app acknowledgements using a styled `NSAttributedString`.

## [10.0.0] 2018-09-05

### Changed

- Rewrite `NSDate+Components` and `NSDate+TimeSince` in Swift and rename to `Date+Components` and `Date+ElapsedTime`, respectively.

#### Locator

- Make `Locator`s conform to `Debuggable`, and provide debugging controls for `CoreLocationSimulator`.
- Instead of setting a property on `CoreLocationSimulation` with the location data, pass in the raw string from e.g. the environment variable value and parse it internally.
- Add new `LocationError` enum and change `Locator`'s callback to pass this type. Currently just wraps `NSError`s reported by `CoreLocation`.

#### Debugging

- `DebugFlowController` now delegates model deletion back to the consumer app, instead of directly deleting the sqlite database files. Prevents a forced restart of the app to reconstruct the database.
- `DatabaseFixsturePickerViewController` now requires a parameter of type `Environment` instead of `CoreDataController`, which it can get from the environment parameter, as well as logging/alerting/etc.
-

#### Model

- Always require a `NSManagedObjectContext` for fetching, instead of falling back to acquiring a new vended context. Helps with context confinement of model entity instances.
- Instead of requiring an instantiated `NSManagedObjectModel` in init, just get the bundle identifer of the bundle that contains it, and use the model name it already has to construct the instance internally.

#### CrudViewController

- No longer sets the Add Item cell's accessibility label to the reuse identifier of the cell. Now just lets the accessibility subsystem automatically infer it.
- Remove `reloadTableView()` as it is already used in `reloadData()`.

### Added

- Add case to `LaunchArgument` to delete all core data models on launch.
- Add asynchronous `Operation` subclass, `AsyncOperation`.
- Add function on `CoreDataController` to directly vend a context, instead of through a closure parameter via `perform(with:)`.
- Added property on `Environment` to hold reference to a `Locator?`.

### Fixed

- Hide debugging menu button when the menu is visible.
- Prevent double insertions of the same row in `CrudViewController`, due to multiple callbacks from the `NSFetchedResultsController` (in testing, also observed multiple `Notification`s sent for the same insertion).

## [9.0.3] 2018-08-24

### Fixed

- Improved keyboard avoidance in `FormController` when used in conjunction with a `UIScrollView`.
- Fixed issues in `AuthorizedCLLocationManager` and `CoreLocationAdapter` that prevented themt from calling back to consumers.

## [9.0.2] 2018-08-24

### Changed

- Renamed a parameter in a `UIEdgeInset+Factory.swift` init to remove ambiguity with its stock `init(top:right:bottom:left)`

## [9.0.1] 2018-08-23

### Fixed

- Prepopulated app name and version into subject and body of feedback emails sent from InfoViewController. Also dismiss the mail view, where it previously hung on the screen.

## [9.0.0] 2018-08-23

### Changed

- `InfoViewController` is constructed differently, with changes to how acknowledgements are passed in.

### Added

- Automatically add buttons for bug reporting, acknowledgements, contact, and in app purchases in `InfoViewController`.
- `Debuggable` protocol specifying that conformers will return a `UIView` containing controls a tester may use to exercise the component. Add implementations for `SwiftMessagesAdapter` (`Alerter`), `JGProgressHUDAdapter` (`ActivityIndicator`), `CrashlyticsAdapter` (`CrashReporter`) and `CoreDataController`.
- Parameter on `Environment` for a `Fonts` conforming object, and a default `Fonts` implementation, `DefaultFonts`, provided as the default value if one is not provided. This helped to remove the fonts parameter from `InfoViewController`, and is used in several other places that already benefited from `EnvironmentallyConscious` conformance.

### Fixed

- Thread child view controller `title` value through `BlurViewController`. Helps when embedding a vc into `BlurViewController` and then in a `DismissableModalViewController`, which displays a `UILabel` with the child vc's `title`.
- Fixed `hitTest` override in `DebugWindow` that caused touches on anything other than `UIButton`s in the `DebugViewController`.

## [8.0.0]

## [2.0.0] 2017-12-31

### Changed
- Update String rDNS constructors
- Require iOS 11
- Reorganize debugging sources under Core
- Remove default log level function

### Added
- Add Core protocols:
- Alerter + SwiftMessagesAdapter
- InAppPurchaseVendor
- Fonts
- Environment struct
- LaunchArgument/EnvironmentVariable enums
- Allow passing custom managed object model to CoreDataController
- FormController now manages UITextViews
- Theming/customizing CrudViewController:
- Custom cells
- Empty state
- Look/feel

### Fixed
- Fix warnings:
  - deprecated usage of `characters` property of a Swift string to determine its length
  - unreachable code around fatal error
- Improvements:
  - FlowController
  - Debugging

## [1.0.0] 2017-11-29

- The official version 1 release!

repository: TwoRingSoft/Pippin

gha_language: Swift

repo_name: TwoRingSoft/Pippin


text:
# stm32h
Universal "stm32.h" CMSIS include
+ Put stm32.h file into your CMSIS/Device/ST folder
+ Include stm32.h into your project
+ define family and device variables for preprocessor
+ enjoy

|family variable | family             | device variables (see the revelant include from ST)|
|----------------|--------------------|-------------------------------------------------|
| STM32F0        | STL32F0 family     | STM32F030x6 STM32F030x8 STM32F031x6 STM32F098xx |
| STM32F1        | STL32F1 family     | STM32F100xB STM32F101x6 STM32F103xE STM32F107xC |
| STM32F2        | STL32F2 family     | STM32F205xx STM32F215xx STM32F207xx STM32F217xx |
| STM32F3        | STL32F3 family     | STM32F301x8 STM32F302x8 STM32F303xC STM32F373xC |
| STM32F4        | STL32F4 family     | STM32F405xx STM32F417xx STM32F429xx STM32F412Cx |
| STM32F7        | STL32F7 family     | STM32F756xx STM32F746xx STM32F745xx STM32F767xx |
| STM32H7        | STL32H7 family     | STM32H750xx                                     |
| STM32L0        | STL32L0 family     | STM32L051xx STM32L052xx STM32L053xx STM32L061xx |
| STM32L1        | STL32L1 family     | STM32L100xB STM32L151xC STM32L152xC STM32L162xD |
| STM32L4        | STL32L4 family     | STM32L431xx STM32L443xx STM32L462xx STM32L485xx |


text:
# xero-sdk-py
Python SDK to access Xero APIs

## Requirements

1. [Python 3+](https://www.python.org/downloads/)
2. [Requests](https://pypi.org/project/requests/) library

## Installation

Install Xero SDK using [pip](https://pypi.org) as follows:

```
pip install xerosdk
```

## Usage

This SDK requires OAuth2 authentication credentials such as
**client ID**, **client secret** and **refresh token**.

1. Create a connection using the XeroSDK class.

```python
from xerosdk import XeroSDK

connection = XeroSDK(
    base_url='<XERO_BASE_URL>',
    client_id='<YOUR CLIENT ID>',
    client_secret='<YOUR CLIENT SECRET>',
    refresh_token='<YOUR REFRESH TOKEN>'
)

# tenant_id is required to make a call to any API
tenant_id = connection.tenants.get_all()[0]['tenantId']
connection.set_tenant_id(tenant_id)
```

2. Access any of the API classes

```python
"""
USAGE: <XeroSDK INSTANCE>.<API_NAME>.<API_METHOD>(<PARAMETERS>)
"""

# Get a list of all Invoices
response = connection.invoices.get_all()

# Get a list of all Invoices using generator
for response in invoices.list_all_generator():
   print(response)

# Get an Invoice by id
response = connection.invoices.get_by_id(<invoice_id>)
```

**NOTE**: Only Tenants, Invoices, Accounts, Contacts, Items and TrackingCategories
API classes are defined in this SDK.

## Integration Tests

1. Install [pytest](https://pypi.org/project/pytest/) package using pip as follows:

```
pip install pytest
```

2. Create a 'test_credentials.json' file at project root directory and enter Xero OAuth2 authentication credentials of
your Xero app.

```json
{
  "base_url": "<xero_base_url>",
  "client_id": "<client_id>",
  "client_secret": "<client_secret>",
  "refresh_token": "<refresh_token>"
}
```

3. Run integration tests as follows:

```
python -m pytest tests/integration
```

repository: fylein/xero-sdk-py

gha_language: Python

repo_name: fylein/xero-sdk-py


text:
# @crossroad/schema

This service extends `@forrestjs/service-express-graphql` and allows to dynamically
extend the running `GraphQLSchema` with **extensions** using `graphql-extension` package
to parse the extension definition.

An extension looks something like:

```json
{
  "name": "ExtensionName",
  "queries": {
    "users": {
      "type": "JSON",
      "resolve": {
        "type": "rest",
        "url": ""
      }
    }
  }
}
```

and you can add this to the schema with the follwing mutation:

```gql
mutation extendSchema {
    registerExtensionJSON(definition: { ... })
}
```

finally you can query the extension:

```gql
query getUsers {
  ExtensionName {
    users
  }
}
```

repository: marcopeg/crossroad

repo_name: marcopeg/crossroad


text:
# Dalamud.SmartVote

A copy from Bluefissure's SmartVote.

this plugin is stored in [HERE](https://github.com/Bluefissure/DalamudPlugins/tree/Bluefissure-api4)

and you can add this repository through [DalamudRepoBrowser](https://github.com/UnknownX7/DalamudRepoBrowser) or use the direct link https://raw.githubusercontent.com/Bluefissure/DalamudPlugins/Bluefissure-api4/pluginmaster.json

branch_name: refs/heads/main


text:
---
layout: post
title: OCaml and IOCaml on Android
categories: [ocaml]
tags: [ocaml, iocaml, gnuroot]
author: Martyn Riley
disqus: true
---

Recently I was looking for an Ocaml solution for the Nexus 7. There are a
couple of ocaml top-levels available but neither offer the ability to open
packages or support for [opam](http://opam.ocamlpro.com).  Enter gnuroot.

The excellent [gnuroot]( https://play.google.com/store/apps/details?id=champion.gnuroot&hl=en)
application enables a linux image to be run alongside Android on an unrooted
device. I determined to use this to install a full ocaml development
environment and then to install the [iocaml]( https://github.com/andrewray/iocaml )
package and the [hardcaml]( https://github.com/ujamjar/hardcaml ) package to
support hardware design. iocaml is used to serve an iocaml notebook to an Android
web-browser providing a great graphical development environment complete with any
opam packages that you decide to install.

The procedure to get this all running is documented below and has been tested on
a 2nd generation Nexus 7 and a Minix Neo X7 media hub. It *should* work on any
Android device with enough memory. A bluetooth keyboard is a very useful addition!

- Install [gnuroot]( https://play.google.com/store/apps/details?id=champion.gnuroot&hl=en) and the gnuroot debian wheezy or wheezyX image from the play store.

Open gnuroot and login using the fake root option. It is then necessary to
install opam from sources.

~~~
$ apt-get update
$ apt-get install ca-certificates
$ cd ~
$ wget https://github.com/ocaml/opam/archive/master.zip
$ apt-get install unzip
$ unzip master.zip
$ cd opam-master
$ apt-get install build-essential
$ apt-get install ocaml ocaml-findlib
$ make lib-ext
$ ./configure
$ make
$ make install
~~~

I then install ocaml 4.01.0

~~~
$ opam init
$ opam switch 4.01.0
~~~

Install your editor of choice e.g `apt-get install vim`

Add the line ... `deb http://http.debian.net/debian wheezy-backports main` to sources.list.

~~~
$ vim /etc/apt/sources.list
~~~

Install library dependencies

~~~
$ apt-get install m4 zlib1g-dev libffi-dev libssl-dev libzmq3-dev
~~~

Finally install the opam packages [iocaml]( https://github.com/andrewray/iocaml )
and [hardcaml]( https://github.com/ujamjar/hardcaml ).

~~~
$ opam install hardcaml iocaml
~~~

Execute iocaml and then access `localhost:8888` from your Android web-browser.


text:
---
slug: apply-now-for-instructional-science-technology-program
title: "Apply now for instructional science, technology program"
date: January 01 2020
---

Open house scheduled for Oct. 29 at CSUMB

  California State University, Monterey Bay invites the public to learn more
  about the master’s degree program in
  Instructional Science and Technology at an
  open house on Oct. 29.

  The event will be held from 4:30 to 6 p.m. in the Alumni and Visitors Center
  on Gen. Jim Moore Boulevard. Several current students and graduates of the
  program will share their experience and how they are applying the skills they
  acquired to their current work.

  The 16-month program will start in the fall of 2014. Application deadline is
  March 15.

  The Master’s in Instructional Science and Technology program prepares students
  for positions in the fast-changing fields of modern education and training.
  The hybrid learning experience – which integrates several days on campus at
  the beginning of each semester with online classes – enables graduates to
  advance in their current careers and will position them to assume leadership
  roles in education and training.

  Successful educators and e-learning developers in the knowledge-based, global
  economy require command of all the technological tools and methodologies
  available to them; the MIST program is designed to provide students with those
  skills.

  More information about the MIST program is available
  here, by calling the School of School of
  Computing and Design at 582-4790, or by e-mailing
  <a
    href="mailto:mist@csumb.edu"
<EMAIL_ADDRESS>  >.

Driving directions and a campus map.

repository: csumb-archives/news-gatsby

repo_name: csumb-archives/news-gatsby


text:
Plugin Execution
=================

    mvn org.vromero:gist-maven-plugin:snippet
    mvn org.vromero:gist-maven-plugin:deploy

This can be simplified by adding the following ```pluginGroup``` to the ```pluginGroups``` section of your
```$HOME/.m2/settings.xml``` .

```xml
<pluginGroups>
    <pluginGroup>org.vromero</pluginGroup>
</pluginGroups>
```

With this ```pluginGroup``` added we can invoke the mojos with:

    mvn gist:snippet
    mvn gist:deploy

repository: vromero/gist-maven-plugin

repo_name: vromero/gist-maven-plugin


text:
## Requested Update

## Why Is This Update Needed?

## Are There Examples Of This Requested Update Elsewhere?

> Read about references issues [here](https://help.github.com/articles/closing-issues-using-keywords/). Provide paragraph text responses to each header.

repository: dollarshaveclub/es-check

repo_name: dollarshaveclub/es-check


text:
# data-resolver
A small module for resolving values, paths (relative and absolute) and arbitrarily complex functions across a data structure and computation context.

A demo app for trying out resolvables can be found on this project's [docs page](https://lukepur.github.io/data-resolver). This demo includes some examples of complex queries using resolvables.

## Why
On first inspection, the resolvable concept may seem overly verbose and more complicated than simply programmatically achieving the same outcomes. However the motivation is that once a solid library of context functions is created, then advanced tooling could be used to build arbitrarily complex data transformations or queries at runtime (and without code modifications).

This could further be enhanced to build a user system that manages such transformations and queries against a large data store to provide fast, dynamic solutions to fluid business questions.

## Installation
```
npm i -S data-resolver
```

## Usage
The primary resolve function has the following signature:

```
const resolve = require('data-resolver');

let resolved = resolve(resolvable, data, context, targetPath);
```

### Resolve function parameters
The parameters are as follows:

| Param | Description |
|---|---|
| `resolvable` | The description of how to resolve this value. See the [resolvable section](#resolvable) for details |
| `data` | The data context to perform the resolve. This is a plain old javascript object |
| `context` | The context to perform function lookups for `fn` and `fnRefLookup` resolution. This is simply an object with function members |
| `targetPath` | The path of the data node to use as the reference point for relative resolve paths. Defaults to root of data object. Can be specified as a `.` delimited path, or an array of strings representing the property hierarchy. |

Simple example:

```
const resolve = require('data-resolver');

const data = {
  a: 1,
  b: {
    b1: 'b1',
    b2: 2
  }
};

const ctx = {
  add: (a, b) => a + b
};

let result = resolve({
  resolvableType: 'fn',
  value: 'add',
  args: [
    { resolvableType: 'lookup', value: '$.a' },
    { resolvableType: 'lookup', value: '$.b.b2' }
  ]
}, data, ctx);

// result -> 3
```

## Resolvable
A 'resolvable' is a serializable object with specific properties to describe how to resolve a value at runtime, in the context of a data object and optional relative path.

### Resolvable structure
A 'resolvable' has the following structure:

```
{
  resolvableType: 'literal' | 'lookup' | 'fn' | 'fnRefLookup',
  value: Any (althoug constraints apply depending on the 'resolvableType'),
  args: Array (array of values or resolvables. Only applicable for 'fn' resolvableType)
}
```

### resolvableType
How each 'resolvableType' is resolved is described below.
| resolvableType | Description |
|---|---|
`literal` | The value provided in the `value` property is returned unchanged. This is the same result as would occur if the value was provided instead of a resolvable.
`lookup` | The value provided in the `value` property of the resolvable is used to extract specific data from the data context. It must be a string. See [Lookup Rules](#lookup-rules) for more details.
`fn` | The value provided in the `value` property of the resolvable must be a string that points to the member name of a function in the [`context`](#resolve-function-parameters). The optional `args` array is used to specify the arguments which are passed to the target `fn` at resolve time. Each `arg` item can be a literal or a resolvable. See [fn resolvables](#fn-resolvables) for more information.
`fnRefLookup` | The value provided in the `value` property of the resolvable must be a string that points to the member name of a function in the [`context`](#resolve-function-parameters). Unlike `fn`, the function is not invoked with `args`, but rather returns a reference to the function. This is useful, for example, to indicate an iteratee for a map `fn`. See [fnRef resolvables](#fnref-resolvables) for more information.

### Lookup Rules
The string provided as the `value` property for a lookup resolvable is used to extract specific data from the complete data context. This mechanism can target specific properties (of any type) as well as use relative references to target data related to a specific subset. Furthermore, wildcard selection allows collecting related data from across multiple entities. The special characters used to define a path are detailed below. The result column is what would be returned if the [Example Data Structure](#example-data-structure) was used as the data context for the example usages.

| Character | Description | Example usage | Result |
|---|---|----|--- |
| `$` | Root data pointer. Returns the entire data context | `$` | `{ movies: [ ...all movie data ] }` |
| `.` | Path separator. Used to indicate the path to take through the data context | `$.movies.1.name` | `'Snatch'` |
| `*` | Wildcard indicator. Used to collect all same-level array values into the resolved value. Can occur multiple times. | `$.movies.*.actors.*` | `['Arnold Schawarzenegger', 'Linda Hamilton', 'Brad Pitt', 'Jason Statham', 'Brad Pitt', 'Christoph Waltz', 'Christian Bale', 'Jared Leto']` |
| `^` | Relative path indicator. Used in conjunction with the `targetPath` to refer to sibling data. | `$.movies.^.year` assuming the target path is `['movies', 1, 'name']` | `2000` |

### fn resolvables
`fn` resolvables provide a mechanism for invoking functions over specific data to compute the resolved value. Used in conjuction with `lookup`s and `fnRef`s, this provides a powerful way to transform data in arbitrarily complex ways. Note that if an `fn` resolvable returns a function (e.g. it is a function factory) then it is a function reference rather than a value. This allows function factories to be used to, for example, build custom iteratees for collection maps.

#### fn examples
The examples below relate to the [example data and context](#example-data-structure).

      Description
      Resolvable
      Result

      Get the set of all actors across all movies

{
  resolvableType: 'fn',
  value: 'uniq',
  args: [
    {
      resolvableType: 'lookup',
      value: '$.movies.*.actors'
    }
  ]
}

      ['Arnold Schawarzenegger', 'Linda Hamilton', 'Jason Statham', 'Brad Pitt', 'Christoph Waltz', 'Christian Bale', 'Jared Leto']

      Get the latest movie

{
  resolvableType: 'fn',
  value: 'arrayMax',
  args: [
    {
      resolvableType: 'lookup',
      value: '$.movies.*.year'
    }
  ]
}

{
  name: 'Inglorious Basterds',
  year: 2008,
  directors: 'Quentin Tarantino',
  actors: ['Brad Pitt', 'Christoph Waltz']
}

### fnRefLookup resolvables
`fnRefLookup` resolvables provide a mechanism for obtaining a reference to a function in the `context`. This is generally useful for providing collection iteratees to collection `fn`s. `fnRefLookup` simply returns a reference to a function by name in the `context`.

#### fnRef examples
The examples below relate to the [example data and context](#example-data-structure).

      Description
      Resolvable
      Result

      Get the set of all actors in movies before 2000

{
  resolvableType: 'fn',
  value: 'uniq',
  args: [
    {
      resolvableType: 'fn',
      value: 'pick',
      args: [
        {
          resolvableType: 'fn',
          value: 'filter',
          args: [
            {
              resolvableType: 'lookup',
              value: '$.movies.*
            },
            {
              resolvableType: 'fn',
              value: 'propLessThanFactory',
              args: [2000, 'year']
            }
          ]
        },
        'actors'
      ]
    }
  ]
}

      ['Arnold Schawarzenegger', 'Linda Hamilton']

#### Example data structure

```
const dataStructure = {
  movies: [
    {
      name: 'The Terminator'
      year: 1984,
      director: 'James Cameron',
      actors: ['Arnold Schwarzenegger', 'Linda Hamilton']
    },
    {
      name: 'Snatch',
      year: 2000,
      director: 'Guy Ritchie',
      actors: ['Brad Pitt', 'Jason Statham']
    },
    {
      name: 'Inglorious Basterds',
      year: 2008,
      director: 'Quentin Tarantino',
      actors: ['Brad Pitt', 'Christoph Waltz']
    },
    {
      name: 'American Psycho',
      year: 2000,
      director: 'Mary Harron',
      actors: ['Christian Bale', 'Jared Leto']
    }
  ]
};
```

#### Example context

```
const ctx = {
  uniq: (array) => { /* array unique implementation */},
  filter: (array, filterFn) => { /* array filter implementation */},
  pick: (array, prop) => { /* return array of props */}
  propLessThanFactory: (target, prop) => item => item[prop] < target,
  arrayMax: (array) => { /* return max value in array */}
};
```

## Tips

By allowing a custom context, the customisation of resolvables is practically unlimited. However the real power comes from being able to achieve complex queries from a relatively small set of generic context functions.

For example, the [demo UI](https://lukepur.github.io/data-resolver) achieves fairly complex queries using only the functions exposed by lodash. By utilising the function factory utilites, like `partial`, `overArgs` and the `_` placeholder along with collection transforms like `map` and `filter`, complex queries can be constructed without having to resort to coding specific context functions.

repository: lukepur/data-resolver

repo_name: lukepur/data-resolver


text:
```BasicVal.integer([required], [flags])```

Checks if the value is an integer.

Set ```{parse: true}``` in the flags object to attempt to parse the value.


text:
# Contributing
Contributions are more than welcome! Just open an issue to discuss your proposal, or fork this repo directly and submit a PR.

## General guidelines
- Please adhere to the style conventions followed in the existing codebase.
- Check that the code changes you made do not result in a failing `gulp` build, before submitting the merge request.

## Static content

### Adding new main-pages
To add a new main-page,
1. Create the page. Create the content of the page as a `.pug` file, in the folder `views`, e.g., `views/traces.pug`. Typically, a main page `extends skeleton`, and further includes a title and some text, for example:
    ```
    block content
        .container.page-container
            h1.page-title #{pageTitle}

            h2 Example Level-2 Heading
            p Example paragraph under heading.
    ```

2. Ensure the page is generated by `gulp`. Add the name of the file in `app/view-controller.js`, in function `createTemplateContextsFromDB`, under `templateContexts`, as follows.
   For `awards`:
    ```
    awards: generateAwardContext(databaseController.database.awards),
    ```
   For `traces`:
    ```
    traces: {
        pageTitle: 'Traces',
        pageId: 'traces'
    },
    ```

3. Link the page in the jumbotron/main head-menu. Add the name of the `.pug` file in the list used by the jumbotron, in `views/skeleton.pug`:
    ```
    #navbar.navbar-collapse.collapse
        ul.nav.navbar-nav.navbar-right
            each page in ['traces', 'trace format', 'about', 'talks', 'publications',]
    ```

## Templates
If you want to contribute to the page templates, see the `views` folder for all Pug template files (these are the ones being compiled into HTML). The template logic to compile them is contained in the `app` directory.

## Styles
Want to improve the styling of some part of the webpage? Have a look in the `public/src/styles` folder.

repository: atlarge-research/wta-website

gha_language: Pug

repo_name: atlarge-research/wta-website


text:
---
layout: post
title: "Rails conventions"
date: 2013-06-13 12:25
comments: true
categories:
- Clips
---

I came across this on the [parley mailing list](http://rubyrogues.com/parley/) and thought it was a wonderful idea.
I've seen coding style guides on projects before, but documenting conventions as well should go a long way into getting
new developers up to speed. This is something I'll probably try in the future.

[Rails conventions](https://github.com/barsoom/devbook/blob/master/rails_conventions/README.md)

repository: tjsingleton/blog

extension: markdown

repo_name: tjsingleton/blog


text:
sensu-check-log
===============

TravisCI: [![TravisCI Build Status](https://travis-ci.org/sensu/sensu-check-log.svg?branch=master)](https://travis-ci.org/sensu/sensu-check-log)

`sensu-check-log` is a log file analyzer plugin for Sensu Go. The program scans
a log file, checks it for matches, and sends a special failure event to the
agent events API when a match is detected.

The check itself will always return a 0 status, unless execution fails for
some reason.

The check must be configured with `stdin: true` so that failure events can
be formed correctly. If the check is not configured with `stdin: true`, then
it will fail to execute.

```
Usage of sensu-check-log:
  -api-url string
    	agent events API URL (default "http://localhost:3031/events")
  -event-status int
    	event status on positive match (default 1)
  -log string
    	path to log file (required)
  -match string
    	RE2 regexp matcher expression (required)
  -max-bytes int
    	max number of bytes to read (0 means unlimited)
  -procs int
    	number of parallel analyzer processes (default 4)
  -state string
    	state file for incremental log analysis (required)
```

repository: sensu-og/sensu-check-log

repo_name: sensu-og/sensu-check-log


text:
# PuffinCoin
A decentralised python cryptocurrency

Work in progress!
Mainnet launch soon.

## Requirements
* ```Python3```
* ```pip3```

## Usage

Run the following in the command line:
```
cd PuffinCoin
pip3 install requirements.txt
python3 PuffinCoin.py
```

## Contributing
If you wont to contribute, just open a pull request.

IMPORTANT: If you changed anything major, please tag your commit and change ```blockchain.VER``` in ```blockchain.py```

## Versioning
1.2.3

1: major releases

2: features

3: patches/small changes

repository: PuffinDev/PuffinCoin

repo_name: PuffinDev/PuffinCoin


text:
# ssec

A Spring Boot - Spring Security project for quick development process.

Initially it includes only one branch with Basic Authentication so you can run the project immediately and is configured with a stateless policy.
This setup includes a controller loaded up with resources in order to build the project the way you want it.

You are advised to implement a proper authentication mechanism (ldap,jwt, etc..) if you are to use this as a backbone for serious development purposes.

More branches will be added to showcase different approaches

So , just clone it and start building!

repository: xzinoviou/ssec

repo_name: xzinoviou/ssec


text:
# Serializing Dates in JSON

DateTimes in JSON are hard.

The problem comes from the [JSON spec](http://www.ietf.org/rfc/rfc4627.txt) itself: there is no literal syntax for dates in JSON. The spec has objects, arrays, strings, integers, and floats, but it defines no standard for what a date looks like.

## Dates and Json.NET

The default format used by Json.NET is the [ISO 8601 standard](http://en.wikipedia.org/wiki/ISO_8601): `"2012-03-19T07:22Z"`.

Prior to Json.NET 4.5 dates were written using the Microsoft format: `"\/Date(1198908717056)\/"`. If you want to use this format, or you want to maintain compatibility with Microsoft JSON serializers or older versions of Json.NET, then change the [DateFormatHandling](/api/newtonsoft/json/dateformathandling/)
setting to MicrosoftDateFormat.

The [DateTimeZoneHandling](/api/newtonsoft/json/datetimezonehandling/) setting can be used to convert a DateTime's [DateTimeKind](https://docs.microsoft.com/en-us/dotnet/api/system.datetimekind) when serializing. For example set DateTimeZoneHandling to Utc to serialize all DateTimes as UTC dates. Note that this setting does not effect DateTimeOffsets.

If your dates don't follow the ISO 8601 standard, then the DateFormatString setting can be used to customize the format of date strings that are read and written using .NET's [custom date and time format syntax](https://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx).

## DateTime JsonConverters

With no standard for dates in JSON, the number of possible different formats when interoping with other systems is endless. Fortunately Json.NET has a solution to deal with reading and writing custom dates: JsonConverters. A JsonConverter is used to override how a type is serialized.

:::code source="../../Src/Newtonsoft.Json.Tests/Documentation/SerializationTests.cs" region="SerializingDatesInJson" title="DateTime JsonConverters Example" :::

Simply pass the JsonConverter you wish to use to the Json.NET serializer.

## JavaScriptDateTimeConverter

The JavaScriptDateTimeConverter class is one of the two DateTime JsonConverters that come with Json.NET. This converter serializes a DateTime as a [JavaScript Date object](http://msdn.microsoft.com/en-us/library/cd9w2te4.aspx): `new Date(1234656000000)`

Technically this is invalid JSON according to the spec, but all browsers and some JSON frameworks, including Json.NET, support it.

## IsoDateTimeConverter

:::
From Json.NET 4.5 and onwards dates are written using the ISO 8601 format by default, and using this converter is unnecessary.
:::

IsoDateTimeConverter serializes a DateTime to an [ISO 8601](http://en.wikipedia.org/wiki/ISO_8601) formatted string: `"2009-02-15T00:00:00Z"`

The IsoDateTimeConverter class has a property, DateTimeFormat, to further customize the formatted string.

## See Also

- [DateFormatHandling](/api/newtonsoft/json/dateformathandling/)
- [DateTimeZoneHandling](/api/newtonsoft/json/datetimezonehandling/)
- [JavaScriptDateTimeConverter](/api/newtonsoft/json/converters/javascriptdatetimeconverter/)
- [IsoDateTimeConverter](/api/newtonsoft/json/converters/isodatetimeconverter/)

gha_language: C#


text:
## Mini-Tutorial: Run Cycle

￼￼￼￼

Run cycles are much more difficult to get right than walk cycles. This is because a run cycle involves much more sudden movements (a runner is essentially jumping from one foot to the other and then back again). A run cycle will generally be shorter than a walk cycle.

The key underlying insight when animating a run cycle is that running is really a series of alternating one-legged jumps (think of the way the tentacle moves) whereas walking is a series of balance-shifts.

As a starting point, I’d suggest making a 0.6s take (let’s call it “run cycle”). You’ll want four base keyframes, but they’re not going to be evenly spaced. We’ll call them “Compress”, “Takeoff”, “Passing”, “Touchdown” and try putting them on frames 0, 1, 4, and 7. Then copy frame 0 to frames 9 and 18, and frames 1, 4 and 7 to 10, 13 and 16 respectively. Then you need to “flip” frames 9, 10 13, and 16.


text:
---
title: "photos.photo"
description: "Photo with auxiliary data."
nav_exclude: true
image: https://docs.madelineproto.xyz/favicons/android-chrome-256x256.png
redirect_from: /API_docs/constructors/photos_photo.html
---
# Constructor: photos.photo
[Back to constructors index](/API_docs/constructors/index.html)

Photo with auxiliary data.

### Attributes:

| Name     |    Type       | Required | Description |
|----------|---------------|----------|-------------|
|photo|[Photo](/API_docs/types/Photo.html) | Optional|Photo|
|users|Array of [User](/API_docs/types/User.html) | Yes|Users|

### Type: [photos.Photo](/API_docs/types/photos.Photo.html)

### Example:

```
$photos_photo = ['_' => 'photos.photo', 'photo' => Photo, 'users' => [User, User]];
```

repository: danog/MadelineProtoDocs

gha_language: PHP

repo_name: danog/MadelineProtoDocs


text:
Snake in PyQt
==========

Simple snake game coded in python, using PyQt.

`pyqt_snake_raspberry.py` instead is the same code but support 8/10/12/16 pin of Raspberry Pi to move the snake.

![screenshot of game over](screenshot_pyqt_snake.png)

license: Unlicense

gha_license_id: Unlicense


text:
# A simple Flutter Web project
### Configured for VS Code Development Container mode

This is the hello world sample project of Flutter Web that you can execute with **[VS Code Remote - Containers](https://aka.ms/vscode-remote/containers)** extension in few easy steps.

## Setting up the development container

Follow these steps to open this sample in a container:

1. If this is your first time using a development container in Visual Studio Code, please follow the [getting started steps](https://aka.ms/vscode-remote/containers/getting-started).

2. If you're not yet in a development container:
   - Clone this repository.
   - Press F1 and select the **Remote-Containers: Open Folder in Container...** command.
   - Select the cloned copy of this folder, wait for the container to start, and try things out!

## Things to try

One you have this sample opened in a container, you'll be able to work with it like you would locally.

Some things to try:

1. **Edit:**
   - Open `lib/main.dart`
   - Try adding some code and check out the language features. Notice that `dart.dart` and the `dart.flutter` extensions are already installed in the container.
2. **Terminal:** Press Ctrl+Shift+\`</kbd> and type `uname` and other Linux commands from the terminal window.
3. **Run with auto reload:**
   - Open container terminal and, inside /workspace folder, type: `livecode` (it's a bash alias executing `flutter packages pub global run webdev serve --hostname <IP_ADDRESS> --auto restart`)
   - Open a local browser and go to `http://localhost:8080` and note you can connect to the server in the container.

## Optional ToDo

Add git configuration to work inside container


text:
---
layout: article
title:	"Last Christmas"
date:	2014-12-29
author: CANADALEK
categories: review doctorwho
tags: doctorwho
show_tags: true
aside:
    toc: true
---

I just finished watching the 2015 Doctor Who Christmas special “Last Christmas” and I quite enjoyed it. I’m going to talk about it not so you know…*spoilahs*.

### Things I’m Happy About

It was Santa, with cheeky elves and the Doctor. Fantastic. It was worth it for that shot of Santa riding Rudolph in and sauntering in to save the day. Lots of fun.

The biggest thing I’m happy about is that Santa didn’t turn out to be the Doctor somehow embedding himself into the dream. *Gawd* that would have hurt, it’s a good trick but one that has been used too often in the past few seasons. I really liked Time Heist despite this but it was a close run thing.

 It’s a great show and they should be proud of it.

That being said…I was fundamentally disappointed with the resolution in this episode. It’s not the Danny Pink thing, that was very nice. Clara got a chance to properly say goodbye to her boyfriend and he got to save her one last time without having his face mangled in a Cyberman or talking to her across a cloud out of the Netherspace. It’s a good resolution.

They should have ended it there when she woke up **or** done something truly original rather than the Clara turns old thing. She just woke up one more time and it was fine. I don’t know what the resolution could have been but something beyond waking up from a third dream and redoing the Inception plot again. Seriously something out there. Maybe a hint about Gallifrey that breaks the dream or something else. It was a chance to be original and it was missed.

*More to be updated as I think of it and watch the ‘Extras’ episode.*


text:
# How to complete this Code Adventure!

In this workspace, you'll find a file that contains four sections:
the description, the code, the output, and the tests.

### Purpose
The purpose of a code adventure is practice, repitition,
and to get you to think about how you would implement
your own algorithm. Except in a code adventure
we will attempt to tackle more "low-level"
like approaches, avoiding all the more
"magical" high-level language features
that Python has built into it.

### The description
Read the description at the top of the `code.py` file to understand
the details of the problem for this code adventure.

### The code
Below the description, there may be some pre-written code. Look for
the `# add your code here` comments. These are where you will
be filling in all your bits of code to complete the code adventure.

Note: We encourage you to use the most explicit
and verbose way you can for writing it out. You
should try to avoid using any other built-ins functions
that do most of the work for you and really be
trying to use the foundations of the language.

This means things like:
 - Setting variables
 - Built-in datatypes:
    List, Tuple, Dict, Set, Class, Integer, String, Float...
 - Loops (for or while)
 - Conditional if statements
 - Using Comparison operators ( ==, !=, >=, <=, <>, is, is not)
 - Using Logical operators ( AND, OR, NOT  )
 - Using Numeric operators ( +, -, *, /, //, %)
 - Using Bitwise operators (&, ^, |, <<, >>, ~x)
 - str(), int(), float() for converting types into other types.

(definitely use these where you see fit)

### The output
Below the function, a few `print` statements have been included
to print the output of the function. Feel free to change the input
of your function here to help you debug.

### The tests
(**Do not change any code in the tests section**)
These `if` statements will "test" the return of your function
to let you know if your function meets all the criteria of a correct answer.
When you're ready to test your function, go to the console below
the code editor (you can open the console by selecting "show console"
in the view menu if the console is closed) and enter

```python test.py```

The output will tell you which tests passed and which ones failed.
When all the tests pass, you have a working solution! Keep an eye
on Slack because we will have a day in which we post solutions in
the [#code-adventures](https://treehouse-python-td.slack.com/messages/C9564GYV7)
channel and compare your solution with other students so please DO NOT immediately post solutions.


text:
## code challenge 33 :

* Write a function that LEFT JOINs two hashmaps into a single data structure.

* Write a function called left join :
1. Arguments: two hash maps
2. The first parameter is a hashmap that has word strings as keys, and a synonym of the key as values.
3. The second parameter is a hashmap that has word strings as keys, and antonyms of the key as values.
4. Return: The returned data structure that holds the results is up to you. It doesn’t need to exactly match the output below, so long as it achieves the LEFT JOIN logic .

## code challenge 33 whiteboard :

![image](./whiteboard33.png)


text:
Network interface screen for [lcdproc](http://lcdproc.omnipotent.net/)
======================================================================

This is a quick python hack to display the network interfaces using
[lcdproc](http://lcdproc.omnipotent.net/).

Install
-------

Start it up as root, e.g. from `/etc/rc.local`. It will daemonize itself and log to `syslog`.

Contributing
------------

You can reach me at [attila.lendvai@gmail.com](mailto:attila.lendvai@gmail.com).

Patches are welcome, especially to fix the sometimes missed button
events. Although once these servers are gone from me, I'll have no
means to test the patches, so please pay extra attention when testing!

The easiest way:

1. Fork it on github.
2. Create a branch (`git checkout -b my_changes`)
3. Commit your changes (`git commit -am "Added foobar"`)
4. Push to the branch (`git push origin my_changes`)
5. Open a [Pull Request](https://github.com/attila-lendvai/lcdproc-ifaces/pulls)
6. Wait
7. If nothing happens after a couple of weeks, bug the maintainer...

repository: darcyg/lcdproc-ifaces

repo_name: darcyg/lcdproc-ifaces


text:
 Sprint Planning Service :pear:

### Config
The [config](SPU/config.py) file is used to:
1. Set the `operational_q1_start`
1. Set the `default_jira_instance` and other JIRA credentials
1. Teams and relevant information
1. Finally add the following environmental variables:

    `GLOBAL_BOARD :: Name of the global JIRA board`

    `GLOBAL_BAD_BOARD : Name of the global bad JIRA board`

Optionally the `run_for_quarter` field can be set to run the utility for a specific quarter

### Running
You can run the program by installing it first:

    > python setup.py install

Set up the [config](SPU/config.py) file.

Then run the program by typing:

    > spu

### Troubleshooting

If you get a SSL: CERTIFICATE_VERIFY_FAILED error. Please try to run this in your terminal:

    > export REQUESTS_CA_BUNDLE=/etc/pki/tls/certs/ca-bundle.trust.crt

repository: sidpremkumar/Sprint-Planning-Utility

repo_name: sidpremkumar/Sprint-Planning-Utility


text:
# dotfiles

## Getting Started (Linux)

```shell
curl -L https://raw.githubusercontent.com/yutoma/dotfiles/master/setup | sh
```

or

```shell
git clone --recursive --depth=1 https://github.com/yutoma/dotfiles.git ~/dotfiles
~/dotfiles/apply
```

## submodules

In `.vim/pack/plugins/start`:

* [dense-analysis/ale](https://github.com/dense-analysis/ale.git)
* [editorconfig/editorconfig-vim](https://github.com/editorconfig/editorconfig-vim.git)
* [fatih/vim-go](https://github.com/fatih/vim-go.git)
* [francoiscabrol/ranger.vim](https://github.com/francoiscabrol/ranger.vim.git)
* [junegunn/fzf.vim](https://github.com/junegunn/fzf.vim.git)
* [mattn/vim-lsp-settings](https://github.com/mattn/vim-lsp-settings.git)
* [prabirshrestha/async.vim](https://github.com/prabirshrestha/async.vim.git)
* [prabirshrestha/asyncomplete-lsp.vim](https://github.com/prabirshrestha/asyncomplete-lsp.vim.git)
* [prabirshrestha/asyncomplete.vim](https://github.com/prabirshrestha/asyncomplete.vim.git)
* [prabirshrestha/vim-lsp](https://github.com/prabirshrestha/vim-lsp.git)
* [preservim/nerdtree](https://github.com/preservim/nerdtree)
* [rust-lang/rust.vim](https://github.com/rust-lang/rust.vim.git)
* [tpope/vim-repeat](https://github.com/tpope/vim-repeat.git)
* [tpope/vim-surround](https://github.com/tpope/vim-surround.git)

repository: yutoma/dotfiles

repo_name: yutoma/dotfiles


text:
#Naive Bayes
====

NB scores
- gaussian NB 0.05
- categorical on Breed1 NB 0.06
- extended (Gaussian + categorical) 0.087
- ensemble only cats  0.10249, only dogs 0.0730

__________________________________________________________

NOTE on validation:
====

https://www.youtube.com/watch?v=pA6uXzrDSUs&index=23&list=PLpQWTe-45nxL3bhyAJMEs90KF_gZmuqtm
- Holdout (split in 2 groups) : sklearn.model_selection.ShuffleSplit
- KFold (split in K+1 groups): sklearn.model_selection.Kfold
- Leave-one-out (split in len(train) groups) : sklearn.model_selection.LeaveOneOut

all this above methods are rowwise random splits, **we could also split data based on pet id**, this is a bit more complicated but we can comeback later on this if we find problem in validation.

NOTE on how to run test/code coverage:
====

pytest and coverage is installed and correctly set up
to run coverage you can use the command, **you need to be inside this folder (/models/KNN)**

```
pytest tests --cov=./ --cov-report html
open htmlcov/index.html
```

repository: SolbiatiAlessandro/kaggle-pets

gha_language: Jupyter Notebook

repo_name: SolbiatiAlessandro/kaggle-pets


text:
# ⛏ Balin, the job scraper
[![forthebadge](https://forthebadge.com/images/badges/made-with-ruby.svg)](https://forthebadge.com)
[![forthebadge](https://forthebadge.com/images/badges/open-source.svg)](https://forthebadge.com)

A job board scraper for remote software engineering jobs for my personal job search.
Balin digs up the best job for software engineering job searches from several websites. Run it locally to customize which jobs Balin prioritizes!

Themed and named after Balin, one of the many dwarfs who led Bilbo to the Lonely Mountain in the Hobbit.

## Customizing for your Search
Want Balin to help dig up great software engineering jobs for you? Follow these steps:

- Ensure that you have a modern version of Ruby installed
- Clone this repository
- `cd` into the repo
- Run `bundle`
- In your code editor, head to `./lib/scrapers/blockers_n_boosters.rb`
- Add or subtract words from the "BLOCKERS" constant to filter out jobs containing those keywords
- Add or subtract words from the "BOOSTERS" constant to add a bump to jobs containing those keywords
  - Note that a posting's recency is also considered for most of the scrapers included.

- Run `ruby server.rb` to start the server
- Visit `localhost:4567` to see what Balin digs up!

## Current job boards being scraped

- [RemoteOK](https://remoteok.io)
- [Remotive](https://remotive.io)

## Contributing
If you see something you'd like to fix, there's a job board you'd like to scrape, or any other enhancement, create a pull request!
Make sure that the feature you build is something that adds to the project as whole, rather than tailoring the job search to your particular needs.

MIT Licensed.

repository: SaalikLok/balin-the-job-miner

gha_language: Ruby

repo_name: SaalikLok/balin-the-job-miner


text:
Trigger geometries provide the following interfaces:
* Mapping between HGCAL sensor cells, trigger cells, modules, lpGBTs and backend FPGAs

The available HGCAL trigger geometries are the following:
* `HGCalTriggerGeometryV9Imp3` (DEFAULT)
  - Compatible with the HGCAL geometries >= V9
  - All links mapping are available (elinks, lpGBT, BE links)
  - Backend FPGA mappings are available
  - Links and FPGA mappings are defined in external JSON files
  - Mapping configs are available for 72 and 120 input links per Stage 1 FPGA.
  - These mappings correspond to a PU-driven distribution of elinks; there is no configuration corresponding to signal-driven elink distribution at the moment.
* `HGCalTriggerGeometryV9Imp2`
  - Compatible with the HGCAL geometries >= V9
  - No links mapping. Only the number of elinks per module/ECON-T is available. Both PU-driven and signal-driven elink distributions can be used.
  - Backend FPGA mappings are not available

repository: cms-sw/cmssw

repo_name: cms-sw/cmssw


text:
# fxToolTip Change Log

>  **Tags:**
>
> - :boom:       		 Breaking Change
> - :eyeglasses: 		 Spec Compliance
> - :rocket:     		 New Feature
> - :bug:        		 Bug Fix
> - :pencil:       		 Documentation
> - :house:      		 Internal
> - :hammer_and_wrench:  Improvement

# Version 2

### v2.4.8
_Jan 12, 2023_
- :bug: Updated dev dependencies to resolve vulnerabilities in json5 and terser.
- :house: Removed support for ie in .browserslistrc.

### v2.4.7

_Apr 25, 2022_
- :house: Updated jest to 28.0.0.

## v2.4.6

_Apr 4, 2022_
- :house: Fixes to package.json.

## v2.4.5

_Apr 4, 2022_
- :house: Updated license.md.

## v2.4.4

_Apr 4, 2022_
- :pencil: Various typo fixes to the documentation.

## v2.4.3

_Apr 3, 2022_
- :bug: Updated babel-core to resolve vulnerability in minimist.

## v2.4.2

_Feb 3, 2022_
- :pencil: FIxed documentation link.

## v2.4.1

_Feb 3, 2022_
- :pencil: Fixed link to demos.

## v2.4.0

_Feb 3, 2022_
- :hammer_and_wrench: Updated all dev dependencies.

## v2.3.0

_Feb 3, 2022_
- :eyeglasses: Renamed .babelrc to babel.config.json.
- :hammer_and_wrench: Added some unit tests using jest.
- :hammer_and_wrench: Improvements to *parseColor* and *hexToRgb* utilities.
- :bug: Fixed bug in *getElementCoordiates* overlap bottom.
- :hammer_and_wrench: Added dev-dependency for *fxStripJsDoc* since terser has depreciated the *beautify* option.
- :pencil: Improvement to docs.
- :bug: Updated dev dependencies to resolve vulnerability in jsdoc.

## v2.2.0

_Oct 11, 2021_
- :bug: Fixed tooltip overflow into scrollbar
- :bug: Addressed edge cases where tooltip is too large for the client viewport.
- :hammer_and_wrench: Improved deconfliction of position, auto-positioning, and preferred-orientation options.
- :hammer_and_wrench: Implemented new algorithm for auto-positioning.
- :hammer_and_wrench: Added additional error checking for tooltip options.
- :boom: Added the ability to set appropriate options to percentage values.
- :hammer_and_wrench: Updated dev-dependencies.
- :pencil: Updated docs.

## v2.1.1

_Oct 6, 2021_
- :bug: Fixed broken docs link
- :pencil: Docs updates
- :boom: Added new method to the fxToolTip object to suspend or enable checking the DOM for deleted DOM elements.

## v2.1.0

_Oct 5, 2021_
- :pencil: Updated Readme.md - clarified cursor usage
- :bug: change default orientation to 'right' to provide a default if autoPosition is false
- :hammer_and_wrench: Added error checking code to several options
- :hammer_and_wrench: Converted the fxTooltip code to and ES6 class and incorporated tip.js
- :bug: Improved mouseout delay
- :bug: Corrected bug in code that automatically shuts down the fxToolTip environment
- :pencil: Added jsDoc annotations throughout - created new documentation github.io

## v2.0.1

_Sept 25, 2021_
- :bug: fixed typo in autoPosition option code
- :bug: fixed typo in autoSize option

## v2.0.0

_Sept 24, 2021_
- :warning: Set default max/min height/width to *none*
- :warning: Stopped transpiling src directory code (dist directory files are still transpiled)
- :bug: Resolved conflicts between .autoSize() and .width() and .height() methods
- :pencil: Updated readme.md

# Version 1

## v1.4.6

_Sep 17, 2021_
- :hammer_and_wrench: updated babel to resolve dependency vulnerability
- :hammer_and_wrench: Bump path-parse from 1.0.6 to 1.0.7
- :hammer_and_wrench: Bump browserslist from 4.13.0 to 4.16.5
- :hammer_and_wrench: Bump lodash from 4.17.19 to 4.17.21

## v1.4.5

_Oct 13, 2020_
- :hammer_and_wrench: updated links to demos

## v1.4.4

_Oct 12, 2020_
- :hammer_and_wrench: fixed broken link to demos

## v1.4.3

_Aug 18, 2020_
- :pencil: Updated readme.md

## v1.4.2

_Jul 16, 2020_
- :bug: updated babel to remove dependency vulnerability

## v1.4.1

_Mar 17, 2020_
- :bug: updated babel to resolve dependency vulnerability

## v1.4.0

_Dec 24, 2019_
- :boom: added method to temporarily suspend or re-enable tooltip function

## v1.3.0

_Dec 22, 2019_
- :bug: minor bug fix to style regexes
- :bug: updated eslint to address dev vulnerability
- :bug: fixed lodash dev dependency vulnerability

## v1.2.4

_Jul 13, 2019_
- :bug: fixed dev dependency vulnerability in babel

## v1.2.3

_Jun 27, 2019_
- :bug: fixed vulnerability in dependency yaml

## v1.2.2

_Jun 27, 2019_
- :bug: corrected bug in getRule
- :bug: updated eslint to fix vulnerability

## v1.2.1

_Nov 29, 2018_
- :bug: bug fix

## v1.2.0

_Nov 29, 2018_
- :hammer_and_wrench: improved dynamic content changes

## v1.1.1

_Oct 26, 2018_
- :pencil:egregious typos
- :boom: added global option setting capability
- :bug: minor bug fix
- :boom: added the ability to retrieve fxToolTip object by DOM node id

## v1.0.13

_Oct 14, 2016_
- :bug: Reorganized distro and fixed a few bugs

## v1.0.12

_Sep 23, 2016_
- :pencil:Changed script name from publish to docs
- :hammer_and_wrench: Added install instructions
- :pencil:Fixed a typo
- :pencil:Clean up code example
- :hammer_and_wrench: Clean up of the repository
- :hammer_and_wrench: Updated dev dependencies
- :hammer_and_wrench: reorganized repository, aded package.json and rollup.config.js

## v1.0.11

_Jun 30, 2016_
- :hammer_and_wrench: Merge branch 'master' of https://github.com/MichaelRFox/foxToolTip.js update

## v1.0.10

_Jun 29, 2016_
- :pencil: Changed D3 links to d3.org
- :hammer_and_wrench: Added another demo bl.ock
- :hammer_and_wrench: Added link to the D3 demo bl.ock

## v1.0.9

_Jun 28, 2016_
- :pencil: Starting to add some jsDoc

## v1.0.8

_Jun 24, 2016_
- :hammer_and_wrench: fixed directory
- :bug: Removed debug code

## v1.0.7

_Jun 24, 2016_
- :bug: Fixed logic error
- :bug: Fixed string literal error

## v1.0.6

_Jun 23, 2016_
- :hammer_and_wrench: Improved auto delete feature - works on IE
- :hammer_and_wrench: Added some tooltip text

## v1.0.5

_Jun 23, 2016_
- :bug: fixed error in json file
- :hammer_and_wrench: deleted duplicate link

## v1.0.4

_Jun 22, 2016_
- :hammer_and_wrench: Added tiger image file for index.html
- :hammer_and_wrench: Added d3 demo

## v1.0.3

_Jun 22, 2016_
- :boom: Added auto delete feature
- :hammer_and_wrench: created license.md

## v1.0.2

_Jun 20, 2016_
- :hammer_and_wrench: Just neatened things up a bit
- :bug: fixed issue with Opera getComputedStyle() inconsistency

## v1.0.1

_Jun 20, 2016_
- :bug: updated default border radius
- :bug: fixed js source

## v1.0.0

_Jun 19, 2016_
- :hammer_and_wrench: initial commit


text:
# cppnow2017
Repository for my C++Now 2017 talks.

## Implementing variant visitation using lambdas

> The addition of `std::variant` to the upcoming C++17 standard will introduce a "type-safe sum type" to the Standard Library.
> Variants model a "choice between types" - they essentially are type-safe "tagged unions".
>
> The interface they expose, however, is often more cumbersome to use than it needs to be: defining exhaustive visitors requires the user to create a class with several `operator()` overloads, or to create a chain of > `if constexpr(...)` calls. Both solutions are not very elegant.
>
> After a brief overview of `std::variant` and its usefulness, this talk will focus on the implementation of a "lambda-based in-place visitation" approach, where the user can visit a variant by simply providing a set > of lambdas on the spot. This will require implementing a way of overloading arbitrary function objects.
>
> Recursive variant types will then be covered and the "lambda-based" visitation techniques will be applied to them. This will require implementing the "Y combinator" higher-order function to achieve > zero-runtime-overhead lambda recursion.
>
> This talk is intended for developers familiar with C++11 and C++14 core language features (lambdas, variadic templates, `auto`, etc...). Prior knowledge of `std::variant` or sum types is not required.

* ~YouTube Video~ *(not yet available)*

* [`sched.org` link](https://cppnow2017.sched.com/event/f513597672d99e15edc1cd89f7b7b761)

## You must type it three times

Lightning talk about the fact that code has to be manually copy-pasted three times to achieve `noexcept`-friendliness and SFINAE-friendliness. E.g.

```cpp
template <typename F, typename... Ts>
auto log_and_call(F&& f, Ts&&... xs)
    noexcept(noexcept(
        std::forward<F>(f)(std::forward<Ts>(xs)...)
    ))
-> decltype(
    std::forward<F>(f)(std::forward<Ts>(xs)...)
)
{
    log << "calling `f`\n";
    return std::forward<F>(f)(std::forward<Ts>(xs)...);
}
```

* ~YouTube Video~ *(not yet available)*