profile
viewpoint
Jackie Kazil jackiekazil Washington, DC

jackiekazil/data-wrangling 462

Code repository for Data Wrangling with Python (O'Reilly)

aepton/python-data-wrangling 12

Resources for teaching Python for Data Wrangling at NICAR 2016.

fdosani/better-interviews 9

An Open source framework for conducting technical interviews

jackiekazil/dc-neighborhoods 3

Looking into DC neighorhood data

jackiekazil/dotfiles 3

Personal dotfile settings files

jackiekazil/cloud-custodian 1

Rules engine for cloud security, cost optimization, and governance, DSL in yaml for policies to query, filter, and take actions on resources

jackiekazil/django 1

The Web framework for perfectionists with deadlines.

jackiekazil/django-dilla 1

Ubercool DB spammer for Django

issue commentprojectmesa/mesa

How to visualize time in x axis instead of steps?

If you consider a step as a unit of time, then I think this is solved. Yes? No?

JaslinRikkaz123

comment created time in 2 days

issue closedprojectmesa/mesa

Disappearing Agent/Grid in Visualization

Hello. I am working on a simple evacuation model on a basic multi-grid. The problem I am encountering occurs whenever I run the visualization. When I first open it in browser, the agents and the grid itself does not appear. I then press "reset". Sometimes things go back to normal, other times, only the agents appear or all continue to be hidden. Even with the times where the grid/agents do appear, they re-disappear within certain steps. What is going on here? What in my code is causing this issue?

I apologize in advance if this post lacks the necessary information. I did not know whether this is an easy-to-pin-down problem or not. Thanks.

closed time in 4 days

arata-tarata

issue commentprojectmesa/mesa

Disappearing Agent/Grid in Visualization

Since there has been no reply this. I am going to close it. Please reopen when sharing your code or error.

arata-tarata

comment created time in 4 days

issue commentprojectmesa/mesa

SingleGrid position_agent very slow for large grids

@rht I like your proposal.

timjdavey

comment created time in 4 days

issue closedprojectmesa/mesa

How to model the agents' steps by a continuous time,like each hour?

What's the problem this feature will solve? <!-- A clear and concise description of what the problem is. --> Hi, maybe there is a way I didn't find out to realize that each agent will advance its step by an hour with a different time schedule. For example, my agent is the pupil; some pupils will go to school from 8:00 to 9:00, and while some will start their commuting from 9:00 to 10:00. The whole day may be divided into 24 hours, and agents will have an individual schedule to arrange their daily activities. How to represent the 24 hours in MESA? Describe the solution you'd like <!-- A clear and concise description of what you want to happen. --> I have a very naive solution, which is using the self.time to take modulo of 24 in the step function of agent class, but it seems very redundant. Is there any other way to do that? Additional context <!-- Add any other context, links, etc. about the feature here. --> In addition, in the visualization module, how to show the time or date in the axis rather than step? Best regards Sijin

closed time in 4 days

seeingwu

issue commentprojectmesa/mesa

How to model the agents' steps by a continuous time,like each hour?

I am not sure there is any action that needs to be taken at this time. I am going to close this issue for now.

seeingwu

comment created time in 4 days

push eventprojectmesa/mesa

Ewout ter Hoeven

commit sha 9ffb499b434410cc901948a615ca465c63ab07c3

CI: Maintenance: Update to Python 3.10, split of lint jobs - Update main build jobs to Python 3.10 - Split of lint steps in separate jobs

view details

Ewout ter Hoeven

commit sha 146f5a8b839ce811eee1ecfb2e5f4bac169842f8

CI: Also lint Jupyter notebooks with black Install black[jupyter] for lint job

view details

Ewout ter Hoeven

commit sha ae53d21eebe7452c5128f1987fbea2d31b883e85

CI: Don't install all dev dependencies on lint jobs Speeds up both lint jobs by about 25 seconds

view details

Jackie Kazil

commit sha ab3cec5b788104d2dad6f27434f1fadfb8a7452f

Merge pull request #1074 from EwoutH/ci-maintenance CI: Maintenance: Update to Python 3.10, split of lint jobs

view details

push time in 4 days

PR merged projectmesa/mesa

CI: Maintenance: Update to Python 3.10, split of lint jobs
  • Update main build jobs to Python 3.10
  • Split of lint steps in separate jobs, so that the other jobs passes if the lint jobs fails
  • Install black[jupyter] to also lint Jupyter notebooks with black

The new build matrix now looks like this: Screenshot_671

+40 -24

6 comments

1 changed file

EwoutH

pr closed time in 4 days

pull request commentprojectmesa/mesa

CI: Maintenance: Update to Python 3.10, split of lint jobs

LGTM

EwoutH

comment created time in 4 days

issue commentprojectmesa/mesa

Use rebase-and-merge instead of merge

@rht I am confused by settings in your comments. You are suggesting setting it as the default then also encouraging folks during the the PR Rebase -- on the command line? Or call all this be set in the settings and am I missing it?

rht

comment created time in 4 days

pull request commentprojectmesa/mesa

Format Python and Jupyter Notebook files with Black

Good catch. I am cool with either of these. Is this something you plan on picking up? Can you create a ticket?

EwoutH

comment created time in 4 days

push eventjackiekazil/dotfiles

jackiekazil

commit sha ad70b7d0bbf5ae5f8ded1b98d8674be9cdf2357d

Updating gitconfig

view details

push time in 8 days

push eventjackiekazil/dotfiles

jackiekazil

commit sha eaa1970aac349b2447417351a1aba5d1ec996a27

Updating dotfiles.

view details

push time in 8 days

issue commentOpen-Source-Software-Neighborhood-Watch/HQ

Helloooo world!

Hello

jspeed-meyers

comment created time in 10 days

Pull request review commentprojectmesa/mesa

CI: Maintenance: Update to Python 3.10, split of lint jobs

 jobs:         key: ${{ runner.os }}-pip-${{ matrix.python-version }}-${{ hashFiles('Pipfile.lock') }}       if: matrix.python-version == 'pypy3'     - name: Install dependencies-      run: |-        python -m pip install --upgrade pip-        pip install .[dev]-    - name: Lint with flake8-      run: |-        # Use settings from mesas .flake8 file-        flake8 . --count --show-source --statistics-    - name: Lint with black-      if: matrix.python-version == '3.8'-      run: |-        pip install black-        black --check --exclude=mesa/cookiecutter-mesa/* .+      run: pip install .[dev]     - name: Test with pytest-      run: |-        pytest --cov=mesa tests/ --cov-report=xml+      run: pytest --cov=mesa tests/ --cov-report=xml     - name: Codecov       uses: codecov/codecov-action@v1.0.15++  lint-flake:+    runs-on: ubuntu-latest+    steps:+    - uses: actions/checkout@v2+    - name: Set up Python 3.10+      uses: actions/setup-python@v2+      with:+        python-version: "3.10"+    - name: Install dependencies+      run: pip install .[dev]+    - name: Lint with flake8+      # Use settings from mesas .flake8 file+      run: flake8 . --count --show-source --statistics++  lint-black:+    runs-on: ubuntu-latest+    steps:+    - uses: actions/checkout@v2+    - name: Set up Python 3.10+      uses: actions/setup-python@v2+      with:+        python-version: "3.10"+    - name: Install dependencies+      run: pip install .[dev]

Fair point. @EwoutH can you adjust?

EwoutH

comment created time in 10 days

PullRequestReviewEvent

Pull request review commentprojectmesa/mesa

CI: Maintenance: Update to Python 3.10, split of lint jobs

 jobs:         key: ${{ runner.os }}-pip-${{ matrix.python-version }}-${{ hashFiles('Pipfile.lock') }}       if: matrix.python-version == 'pypy3'     - name: Install dependencies-      run: |-        python -m pip install --upgrade pip-        pip install .[dev]-    - name: Lint with flake8-      run: |-        # Use settings from mesas .flake8 file-        flake8 . --count --show-source --statistics-    - name: Lint with black-      if: matrix.python-version == '3.8'-      run: |-        pip install black-        black --check --exclude=mesa/cookiecutter-mesa/* .+      run: pip install .[dev]     - name: Test with pytest-      run: |-        pytest --cov=mesa tests/ --cov-report=xml+      run: pytest --cov=mesa tests/ --cov-report=xml     - name: Codecov       uses: codecov/codecov-action@v1.0.15++  lint-flake:+    runs-on: ubuntu-latest+    steps:+    - uses: actions/checkout@v2+    - name: Set up Python 3.10+      uses: actions/setup-python@v2+      with:+        python-version: "3.10"+    - name: Install dependencies+      run: pip install .[dev]

This line installs it. The one below runs it. So I think this is necessary.

EwoutH

comment created time in 11 days

PullRequestReviewEvent

Pull request review commentprojectmesa/mesa

CI: Maintenance: Update to Python 3.10, split of lint jobs

 jobs:         key: ${{ runner.os }}-pip-${{ matrix.python-version }}-${{ hashFiles('Pipfile.lock') }}       if: matrix.python-version == 'pypy3'     - name: Install dependencies-      run: |-        python -m pip install --upgrade pip-        pip install .[dev]-    - name: Lint with flake8-      run: |-        # Use settings from mesas .flake8 file-        flake8 . --count --show-source --statistics-    - name: Lint with black-      if: matrix.python-version == '3.8'-      run: |-        pip install black-        black --check --exclude=mesa/cookiecutter-mesa/* .+      run: pip install .[dev]     - name: Test with pytest-      run: |-        pytest --cov=mesa tests/ --cov-report=xml+      run: pytest --cov=mesa tests/ --cov-report=xml     - name: Codecov       uses: codecov/codecov-action@v1.0.15++  lint-flake:+    runs-on: ubuntu-latest+    steps:+    - uses: actions/checkout@v2+    - name: Set up Python 3.10+      uses: actions/setup-python@v2+      with:+        python-version: "3.10"+    - name: Install dependencies+      run: pip install .[dev]+    - name: Lint with flake8+      # Use settings from mesas .flake8 file+      run: flake8 . --count --show-source --statistics++  lint-black:+    runs-on: ubuntu-latest+    steps:+    - uses: actions/checkout@v2+    - name: Set up Python 3.10+      uses: actions/setup-python@v2+      with:+        python-version: "3.10"+    - name: Install dependencies+      run: pip install .[dev]

Good catch. Is there a reason why we wouldn't just add the black[juypter] to dev setup? And get rid of the second line?

EwoutH

comment created time in 11 days

PullRequestReviewEvent

pull request commentprojectmesa/mesa

Update Pipfile to use Python 3.9

I merged the github action which updates the piplock. can you just submit the python update and I will merge that?

EwoutH

comment created time in 13 days

delete branch projectmesa/mesa

delete branch : update-pipfile

delete time in 13 days

push eventprojectmesa/mesa

jackiekazil

commit sha 38e5a281139959f168623bd4cad645caba965a91

[Bot] Update Pipfile.lock dependencies

view details

Jackie Kazil

commit sha 932350d5b098c7d2224c4b8ecd8cb9c462ecbebc

Merge pull request #1080 from projectmesa/update-pipfile Update Pipfile.lock (dependencies)

view details

push time in 13 days

PR merged projectmesa/mesa

Update Pipfile.lock (dependencies)

Automated changes by create-pull-request GitHub action

+260 -180

0 comment

1 changed file

github-actions[bot]

pr closed time in 13 days

push eventprojectmesa/mesa

Ewout ter Hoeven

commit sha 6db54a5f21dd0ff65d8956d9f0d77ee8277861d3

CI: Add workflow to update Pipfile.lock every month Adds a workflow that generates a up to date lockfile based on the current Pipfile. The workflow runs every 1st day of each month, and if either this configuration or the Pipfile itself is modified. A run will open a PR with the updated pipfile.lock, and if a PR is already open it will update that PR.

view details

Ewout ter Hoeven

commit sha c90fe1a38b14b72894cf2821411c9c299c01dd6f

CI: Specify Python version in update-pipfile workflow Since the Python version is currently fixed in the Pipfile (with [requires] python_version = "3.7") this workflow should use that same Python version.

view details

Ewout ter Hoeven

commit sha 59a9325a6136f87261cdd93d0c55334c768e03a0

CI: Ensure latest pip installs, use create-pull-request@v3

view details

Ewout ter Hoeven

commit sha df6a2dfde02a3793c6a65437059c11447daaa215

CI: Base update pipfile on default branch (main)

view details

Jackie Kazil

commit sha 1a71834e9cdbe474e63782ba866253e115965f10

Merge pull request #1018 from EwoutH/patch-3 CI: Add workflow to update Pipfile.lock every month

view details

push time in 13 days

PR merged projectmesa/mesa

CI: Add workflow to update Pipfile.lock every month

Adds a workflow that generates a up to date lockfile based on the current Pipfile. The workflow runs every 1st day of each month, and if either this configuration or the Pipfile itself is modified. A run will open a PR with the updated pipfile.lock, and if a PR is already open it will update that PR.

By running and opening/updating a PR each month it's ensured the pipfile.lock stays up to date and updated frequently at convenient times, while reproducible builds are still ensured.

The schedule can be adjusted to fit development, of course.

+31 -0

5 comments

1 changed file

EwoutH

pr closed time in 13 days

pull request commentprojectmesa/mesa

CI: Add workflow to update Pipfile.lock every month

LGTM

EwoutH

comment created time in 13 days

push eventprojectmesa/mesa

Ewout ter Hoeven

commit sha 3b978a94a93f7020c3ea0d999fe9d919aaedeaa9

Format Python files with Black

view details

Ewout ter Hoeven

commit sha 33701dbccb4df6c1b5e352321eb2d6543b3685b7

Format Jupyter Notebooks with Black

view details

Jackie Kazil

commit sha 455e1719ffa3b3ea283a771fdf2fd3b0febe3e7c

Merge pull request #1078 from EwoutH/black Format Python and Jupyter Notebook files with Black

view details

push time in 14 days

PR merged projectmesa/mesa

Format Python and Jupyter Notebook files with Black

Formats the Python files and Jupyter Notebooks with Black (version 21.10b0).

Closes #1073.

+173 -125

2 comments

10 changed files

EwoutH

pr closed time in 14 days

issue closedprojectmesa/mesa

Needs black clean up

See build fail on #1072

closed time in 14 days

jackiekazil
more