Cdap by fscottfoti · Pull Request #11 · ActivitySim/activitysim

fscottfoti · 2015-01-07T22:02:20Z

This PR - which I won't be merging yet - contains the CDAP for number of persons in the households == 1

To the good: I had to dig out the definitions of some variables from the code and ended up finding everything I needed. Started a data dictionary on the wiki here: https://github.com/synthicity/activitysim/wiki/Data-Dictionary

Not as good: the multiple member households have some tricky logic in how they choose their CDAP. I got a good explanation from David Ory and will dig into multi-member households next.

e-lo · 2015-01-09T17:39:49Z

At some point it might be good to (since this is an example) write out exactly what is going on in the comments...in travel modeler ( not programmer shorthand ) terms.

I.e. cdap took me a few minutes to figure out what it was. I had to look at the roadmap and then I was like AHA...why didn't you say so! ( or maybe this is bc we just have the less sophisticated DAPs instead of CDAPs)

If it took me 5 min to figure out...my guess that somebody less familiar ( i.e. an intern!) will take longer.

This isnt a high priority for now, but let's keep it mind when we use shorthand and acronyms.

fscottfoti · 2015-02-10T00:03:13Z

Just a quick reminder, for anyone following this repo - this is what I will be working on this week. I believe I have the CDAP (coordinate daily activity pattern) running for 1 person households and will now be proceeding to 2 person households. If you guys would prefer that I be working on something else (e.g. if you don't need the C of CDAP), feel free to let me know.

Elizabeth, your comment about adding comments is important. I suggest we do a commenting and testing iteration after getting enough of a prototype going that we all think that the current approach is good. I don't to to do much polish on code that's still subject to significant revisions...

Workplace size coeffs

And all the alternatives, model, and all the new columns that are required to support it. Only about halfway through at this point but hopefully gets a bit faster going forward. Also added proper newlines to the csv file so they look ok outside of excel. Also started keeping a todo list in markdown to keep track of anything that will need revisiting before the model is fully usable.

still need to polish one or two things before opening a PR though, but pretty close

…ges to the code

for full time worker only at this point

only running for the full time worker person type at this time

…neration 140 lines or so to go!

there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

I didn't realize all the segments in the non mandatory model had the same spec - this made things much easier (i.e. I didn't have to definite 250 variables for every segment). Anyway this is now running and brings up a few questions which I will add to the readme.md.

a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

not working yet as far as model specifications and such

need to ask a few questions about the time windowing

no new functionality here - just splitting up the one large file into 8-10 smaller files. Now have a models directory and one file per model, as well as a tables directory and one file per table. Remember this is only a convention, so mixing in other aspects of the simulation framework where appropriate is expected.

sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

Nonmandatory tour schedule

File reorg

Explicitly testing situations when there are no interactions.

[ci-skip]

It's nice to have the specs not mixed up with alternative names.

So they can be used for evaluating variables with DataFrame.eval.

The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

These are rules that express things like "retired people can't do mandatory tours".

jiffyclub · 2015-03-09T19:41:54Z

Closing this since the PR isn't targeting the master branch.

remove deprecated method from trip scheduling

Updated Model Component Documentation

latest updates from other PRs

* School escorting estimation updates Most changes are needed to avoid crash if estimation run actually had no school escorting in the input data * blacken * updating to work with Pydantic and State object * adding missed columns necessary for no school escorting * blacken * handling zero escorting cases * removing duplicate code

fscottfoti · 2015-01-07T22:02:20Z

This PR - which I won't be merging yet - contains the CDAP for number of persons in the households == 1

To the good: I had to dig out the definitions of some variables from the code and ended up finding everything I needed. Started a data dictionary on the wiki here: https://github.com/synthicity/activitysim/wiki/Data-Dictionary

Not as good: the multiple member households have some tricky logic in how they choose their CDAP. I got a good explanation from David Ory and will dig into multi-member households next.

e-lo · 2015-01-09T17:39:49Z

At some point it might be good to (since this is an example) write out exactly what is going on in the comments...in travel modeler ( not programmer shorthand ) terms.

I.e. cdap took me a few minutes to figure out what it was. I had to look at the roadmap and then I was like AHA...why didn't you say so! ( or maybe this is bc we just have the less sophisticated DAPs instead of CDAPs)

If it took me 5 min to figure out...my guess that somebody less familiar ( i.e. an intern!) will take longer.

This isnt a high priority for now, but let's keep it mind when we use shorthand and acronyms.

fscottfoti · 2015-02-10T00:03:13Z

Just a quick reminder, for anyone following this repo - this is what I will be working on this week. I believe I have the CDAP (coordinate daily activity pattern) running for 1 person households and will now be proceeding to 2 person households. If you guys would prefer that I be working on something else (e.g. if you don't need the C of CDAP), feel free to let me know.

Elizabeth, your comment about adding comments is important. I suggest we do a commenting and testing iteration after getting enough of a prototype going that we all think that the current approach is good. I don't to to do much polish on code that's still subject to significant revisions...

Workplace size coeffs

And all the alternatives, model, and all the new columns that are required to support it. Only about halfway through at this point but hopefully gets a bit faster going forward. Also added proper newlines to the csv file so they look ok outside of excel. Also started keeping a todo list in markdown to keep track of anything that will need revisiting before the model is fully usable.

still need to polish one or two things before opening a PR though, but pretty close

…ges to the code

for full time worker only at this point

only running for the full time worker person type at this time

…neration 140 lines or so to go!

there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

I didn't realize all the segments in the non mandatory model had the same spec - this made things much easier (i.e. I didn't have to definite 250 variables for every segment). Anyway this is now running and brings up a few questions which I will add to the readme.md.

a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

not working yet as far as model specifications and such

need to ask a few questions about the time windowing

no new functionality here - just splitting up the one large file into 8-10 smaller files. Now have a models directory and one file per model, as well as a tables directory and one file per table. Remember this is only a convention, so mixing in other aspects of the simulation framework where appropriate is expected.

sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

Nonmandatory tour schedule

File reorg

Explicitly testing situations when there are no interactions.

[ci-skip]

It's nice to have the specs not mixed up with alternative names.

So they can be used for evaluating variables with DataFrame.eval.

The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

These are rules that express things like "retired people can't do mandatory tours".

jiffyclub · 2015-03-09T19:41:54Z

Closing this since the PR isn't targeting the master branch.

remove deprecated method from trip scheduling

Updated Model Component Documentation

latest updates from other PRs

* School escorting estimation updates Most changes are needed to avoid crash if estimation run actually had no school escorting in the input data * blacken * updating to work with Pydantic and State object * adding missed columns necessary for no school escorting * blacken * handling zero escorting cases * removing duplicate code

fscottfoti · 2015-01-07T22:02:20Z

This PR - which I won't be merging yet - contains the CDAP for number of persons in the households == 1

To the good: I had to dig out the definitions of some variables from the code and ended up finding everything I needed. Started a data dictionary on the wiki here: https://github.com/synthicity/activitysim/wiki/Data-Dictionary

Not as good: the multiple member households have some tricky logic in how they choose their CDAP. I got a good explanation from David Ory and will dig into multi-member households next.

e-lo · 2015-01-09T17:39:49Z

At some point it might be good to (since this is an example) write out exactly what is going on in the comments...in travel modeler ( not programmer shorthand ) terms.

I.e. cdap took me a few minutes to figure out what it was. I had to look at the roadmap and then I was like AHA...why didn't you say so! ( or maybe this is bc we just have the less sophisticated DAPs instead of CDAPs)

If it took me 5 min to figure out...my guess that somebody less familiar ( i.e. an intern!) will take longer.

This isnt a high priority for now, but let's keep it mind when we use shorthand and acronyms.

fscottfoti · 2015-02-10T00:03:13Z

Just a quick reminder, for anyone following this repo - this is what I will be working on this week. I believe I have the CDAP (coordinate daily activity pattern) running for 1 person households and will now be proceeding to 2 person households. If you guys would prefer that I be working on something else (e.g. if you don't need the C of CDAP), feel free to let me know.

Elizabeth, your comment about adding comments is important. I suggest we do a commenting and testing iteration after getting enough of a prototype going that we all think that the current approach is good. I don't to to do much polish on code that's still subject to significant revisions...

Workplace size coeffs

And all the alternatives, model, and all the new columns that are required to support it. Only about halfway through at this point but hopefully gets a bit faster going forward. Also added proper newlines to the csv file so they look ok outside of excel. Also started keeping a todo list in markdown to keep track of anything that will need revisiting before the model is fully usable.

still need to polish one or two things before opening a PR though, but pretty close

…ges to the code

for full time worker only at this point

only running for the full time worker person type at this time

…neration 140 lines or so to go!

there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

I didn't realize all the segments in the non mandatory model had the same spec - this made things much easier (i.e. I didn't have to definite 250 variables for every segment). Anyway this is now running and brings up a few questions which I will add to the readme.md.

a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

not working yet as far as model specifications and such

need to ask a few questions about the time windowing

no new functionality here - just splitting up the one large file into 8-10 smaller files. Now have a models directory and one file per model, as well as a tables directory and one file per table. Remember this is only a convention, so mixing in other aspects of the simulation framework where appropriate is expected.

sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

Nonmandatory tour schedule

File reorg

Explicitly testing situations when there are no interactions.

[ci-skip]

It's nice to have the specs not mixed up with alternative names.

So they can be used for evaluating variables with DataFrame.eval.

The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

These are rules that express things like "retired people can't do mandatory tours".

jiffyclub · 2015-03-09T19:41:54Z

Closing this since the PR isn't targeting the master branch.

remove deprecated method from trip scheduling

Updated Model Component Documentation

latest updates from other PRs

* School escorting estimation updates Most changes are needed to avoid crash if estimation run actually had no school escorting in the input data * blacken * updating to work with Pydantic and State object * adding missed columns necessary for no school escorting * blacken * handling zero escorting cases * removing duplicate code

fscottfoti · 2015-01-07T22:02:20Z

This PR - which I won't be merging yet - contains the CDAP for number of persons in the households == 1

To the good: I had to dig out the definitions of some variables from the code and ended up finding everything I needed. Started a data dictionary on the wiki here: https://github.com/synthicity/activitysim/wiki/Data-Dictionary

Not as good: the multiple member households have some tricky logic in how they choose their CDAP. I got a good explanation from David Ory and will dig into multi-member households next.

e-lo · 2015-01-09T17:39:49Z

At some point it might be good to (since this is an example) write out exactly what is going on in the comments...in travel modeler ( not programmer shorthand ) terms.

I.e. cdap took me a few minutes to figure out what it was. I had to look at the roadmap and then I was like AHA...why didn't you say so! ( or maybe this is bc we just have the less sophisticated DAPs instead of CDAPs)

If it took me 5 min to figure out...my guess that somebody less familiar ( i.e. an intern!) will take longer.

This isnt a high priority for now, but let's keep it mind when we use shorthand and acronyms.

fscottfoti · 2015-02-10T00:03:13Z

Just a quick reminder, for anyone following this repo - this is what I will be working on this week. I believe I have the CDAP (coordinate daily activity pattern) running for 1 person households and will now be proceeding to 2 person households. If you guys would prefer that I be working on something else (e.g. if you don't need the C of CDAP), feel free to let me know.

Elizabeth, your comment about adding comments is important. I suggest we do a commenting and testing iteration after getting enough of a prototype going that we all think that the current approach is good. I don't to to do much polish on code that's still subject to significant revisions...

Workplace size coeffs

And all the alternatives, model, and all the new columns that are required to support it. Only about halfway through at this point but hopefully gets a bit faster going forward. Also added proper newlines to the csv file so they look ok outside of excel. Also started keeping a todo list in markdown to keep track of anything that will need revisiting before the model is fully usable.

still need to polish one or two things before opening a PR though, but pretty close

…ges to the code

for full time worker only at this point

only running for the full time worker person type at this time

…neration 140 lines or so to go!

there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

I didn't realize all the segments in the non mandatory model had the same spec - this made things much easier (i.e. I didn't have to definite 250 variables for every segment). Anyway this is now running and brings up a few questions which I will add to the readme.md.

a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

not working yet as far as model specifications and such

need to ask a few questions about the time windowing

no new functionality here - just splitting up the one large file into 8-10 smaller files. Now have a models directory and one file per model, as well as a tables directory and one file per table. Remember this is only a convention, so mixing in other aspects of the simulation framework where appropriate is expected.

sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

Nonmandatory tour schedule

File reorg

Explicitly testing situations when there are no interactions.

[ci-skip]

It's nice to have the specs not mixed up with alternative names.

So they can be used for evaluating variables with DataFrame.eval.

The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

These are rules that express things like "retired people can't do mandatory tours".

jiffyclub · 2015-03-09T19:41:54Z

Closing this since the PR isn't targeting the master branch.

remove deprecated method from trip scheduling

Updated Model Component Documentation

latest updates from other PRs

* School escorting estimation updates Most changes are needed to avoid crash if estimation run actually had no school escorting in the input data * blacken * updating to work with Pydantic and State object * adding missed columns necessary for no school escorting * blacken * handling zero escorting cases * removing duplicate code

fscottfoti · 2015-01-07T22:02:20Z

This PR - which I won't be merging yet - contains the CDAP for number of persons in the households == 1

To the good: I had to dig out the definitions of some variables from the code and ended up finding everything I needed. Started a data dictionary on the wiki here: https://github.com/synthicity/activitysim/wiki/Data-Dictionary

Not as good: the multiple member households have some tricky logic in how they choose their CDAP. I got a good explanation from David Ory and will dig into multi-member households next.

e-lo · 2015-01-09T17:39:49Z

At some point it might be good to (since this is an example) write out exactly what is going on in the comments...in travel modeler ( not programmer shorthand ) terms.

I.e. cdap took me a few minutes to figure out what it was. I had to look at the roadmap and then I was like AHA...why didn't you say so! ( or maybe this is bc we just have the less sophisticated DAPs instead of CDAPs)

If it took me 5 min to figure out...my guess that somebody less familiar ( i.e. an intern!) will take longer.

This isnt a high priority for now, but let's keep it mind when we use shorthand and acronyms.

fscottfoti · 2015-02-10T00:03:13Z

Just a quick reminder, for anyone following this repo - this is what I will be working on this week. I believe I have the CDAP (coordinate daily activity pattern) running for 1 person households and will now be proceeding to 2 person households. If you guys would prefer that I be working on something else (e.g. if you don't need the C of CDAP), feel free to let me know.

Elizabeth, your comment about adding comments is important. I suggest we do a commenting and testing iteration after getting enough of a prototype going that we all think that the current approach is good. I don't to to do much polish on code that's still subject to significant revisions...

Workplace size coeffs

And all the alternatives, model, and all the new columns that are required to support it. Only about halfway through at this point but hopefully gets a bit faster going forward. Also added proper newlines to the csv file so they look ok outside of excel. Also started keeping a todo list in markdown to keep track of anything that will need revisiting before the model is fully usable.

still need to polish one or two things before opening a PR though, but pretty close

…ges to the code

for full time worker only at this point

only running for the full time worker person type at this time

…neration 140 lines or so to go!

there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

I didn't realize all the segments in the non mandatory model had the same spec - this made things much easier (i.e. I didn't have to definite 250 variables for every segment). Anyway this is now running and brings up a few questions which I will add to the readme.md.

a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

not working yet as far as model specifications and such

need to ask a few questions about the time windowing

no new functionality here - just splitting up the one large file into 8-10 smaller files. Now have a models directory and one file per model, as well as a tables directory and one file per table. Remember this is only a convention, so mixing in other aspects of the simulation framework where appropriate is expected.

sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

Nonmandatory tour schedule

File reorg

Explicitly testing situations when there are no interactions.

[ci-skip]

It's nice to have the specs not mixed up with alternative names.

So they can be used for evaluating variables with DataFrame.eval.

The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

These are rules that express things like "retired people can't do mandatory tours".

jiffyclub · 2015-03-09T19:41:54Z

Closing this since the PR isn't targeting the master branch.

remove deprecated method from trip scheduling

Updated Model Component Documentation

latest updates from other PRs

* School escorting estimation updates Most changes are needed to avoid crash if estimation run actually had no school escorting in the input data * blacken * updating to work with Pydantic and State object * adding missed columns necessary for no school escorting * blacken * handling zero escorting cases * removing duplicate code

fscottfoti · 2015-01-07T22:02:20Z

This PR - which I won't be merging yet - contains the CDAP for number of persons in the households == 1

To the good: I had to dig out the definitions of some variables from the code and ended up finding everything I needed. Started a data dictionary on the wiki here: https://github.com/synthicity/activitysim/wiki/Data-Dictionary

Not as good: the multiple member households have some tricky logic in how they choose their CDAP. I got a good explanation from David Ory and will dig into multi-member households next.

e-lo · 2015-01-09T17:39:49Z

At some point it might be good to (since this is an example) write out exactly what is going on in the comments...in travel modeler ( not programmer shorthand ) terms.

I.e. cdap took me a few minutes to figure out what it was. I had to look at the roadmap and then I was like AHA...why didn't you say so! ( or maybe this is bc we just have the less sophisticated DAPs instead of CDAPs)

If it took me 5 min to figure out...my guess that somebody less familiar ( i.e. an intern!) will take longer.

This isnt a high priority for now, but let's keep it mind when we use shorthand and acronyms.

fscottfoti · 2015-02-10T00:03:13Z

Just a quick reminder, for anyone following this repo - this is what I will be working on this week. I believe I have the CDAP (coordinate daily activity pattern) running for 1 person households and will now be proceeding to 2 person households. If you guys would prefer that I be working on something else (e.g. if you don't need the C of CDAP), feel free to let me know.

Elizabeth, your comment about adding comments is important. I suggest we do a commenting and testing iteration after getting enough of a prototype going that we all think that the current approach is good. I don't to to do much polish on code that's still subject to significant revisions...

Workplace size coeffs

And all the alternatives, model, and all the new columns that are required to support it. Only about halfway through at this point but hopefully gets a bit faster going forward. Also added proper newlines to the csv file so they look ok outside of excel. Also started keeping a todo list in markdown to keep track of anything that will need revisiting before the model is fully usable.

still need to polish one or two things before opening a PR though, but pretty close

…ges to the code

for full time worker only at this point

only running for the full time worker person type at this time

…neration 140 lines or so to go!

there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

I didn't realize all the segments in the non mandatory model had the same spec - this made things much easier (i.e. I didn't have to definite 250 variables for every segment). Anyway this is now running and brings up a few questions which I will add to the readme.md.

a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

not working yet as far as model specifications and such

need to ask a few questions about the time windowing

no new functionality here - just splitting up the one large file into 8-10 smaller files. Now have a models directory and one file per model, as well as a tables directory and one file per table. Remember this is only a convention, so mixing in other aspects of the simulation framework where appropriate is expected.

sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

Nonmandatory tour schedule

File reorg

Explicitly testing situations when there are no interactions.

[ci-skip]

It's nice to have the specs not mixed up with alternative names.

So they can be used for evaluating variables with DataFrame.eval.

The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

These are rules that express things like "retired people can't do mandatory tours".

jiffyclub · 2015-03-09T19:41:54Z

Closing this since the PR isn't targeting the master branch.

remove deprecated method from trip scheduling

Updated Model Component Documentation

latest updates from other PRs

* School escorting estimation updates Most changes are needed to avoid crash if estimation run actually had no school escorting in the input data * blacken * updating to work with Pydantic and State object * adding missed columns necessary for no school escorting * blacken * handling zero escorting cases * removing duplicate code

fscottfoti · 2015-01-07T22:02:20Z

This PR - which I won't be merging yet - contains the CDAP for number of persons in the households == 1

To the good: I had to dig out the definitions of some variables from the code and ended up finding everything I needed. Started a data dictionary on the wiki here: https://github.com/synthicity/activitysim/wiki/Data-Dictionary

Not as good: the multiple member households have some tricky logic in how they choose their CDAP. I got a good explanation from David Ory and will dig into multi-member households next.

e-lo · 2015-01-09T17:39:49Z

At some point it might be good to (since this is an example) write out exactly what is going on in the comments...in travel modeler ( not programmer shorthand ) terms.

I.e. cdap took me a few minutes to figure out what it was. I had to look at the roadmap and then I was like AHA...why didn't you say so! ( or maybe this is bc we just have the less sophisticated DAPs instead of CDAPs)

If it took me 5 min to figure out...my guess that somebody less familiar ( i.e. an intern!) will take longer.

This isnt a high priority for now, but let's keep it mind when we use shorthand and acronyms.

fscottfoti · 2015-02-10T00:03:13Z

Just a quick reminder, for anyone following this repo - this is what I will be working on this week. I believe I have the CDAP (coordinate daily activity pattern) running for 1 person households and will now be proceeding to 2 person households. If you guys would prefer that I be working on something else (e.g. if you don't need the C of CDAP), feel free to let me know.

Elizabeth, your comment about adding comments is important. I suggest we do a commenting and testing iteration after getting enough of a prototype going that we all think that the current approach is good. I don't to to do much polish on code that's still subject to significant revisions...

Workplace size coeffs

And all the alternatives, model, and all the new columns that are required to support it. Only about halfway through at this point but hopefully gets a bit faster going forward. Also added proper newlines to the csv file so they look ok outside of excel. Also started keeping a todo list in markdown to keep track of anything that will need revisiting before the model is fully usable.

still need to polish one or two things before opening a PR though, but pretty close

…ges to the code

for full time worker only at this point

only running for the full time worker person type at this time

…neration 140 lines or so to go!

there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

I didn't realize all the segments in the non mandatory model had the same spec - this made things much easier (i.e. I didn't have to definite 250 variables for every segment). Anyway this is now running and brings up a few questions which I will add to the readme.md.

a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

not working yet as far as model specifications and such

need to ask a few questions about the time windowing

no new functionality here - just splitting up the one large file into 8-10 smaller files. Now have a models directory and one file per model, as well as a tables directory and one file per table. Remember this is only a convention, so mixing in other aspects of the simulation framework where appropriate is expected.

sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

Nonmandatory tour schedule

File reorg

Explicitly testing situations when there are no interactions.

[ci-skip]

It's nice to have the specs not mixed up with alternative names.

So they can be used for evaluating variables with DataFrame.eval.

The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

These are rules that express things like "retired people can't do mandatory tours".

jiffyclub · 2015-03-09T19:41:54Z

Closing this since the PR isn't targeting the master branch.

remove deprecated method from trip scheduling

Updated Model Component Documentation

latest updates from other PRs

* School escorting estimation updates Most changes are needed to avoid crash if estimation run actually had no school escorting in the input data * blacken * updating to work with Pydantic and State object * adding missed columns necessary for no school escorting * blacken * handling zero escorting cases * removing duplicate code

fscottfoti · 2015-01-07T22:02:20Z

This PR - which I won't be merging yet - contains the CDAP for number of persons in the households == 1

To the good: I had to dig out the definitions of some variables from the code and ended up finding everything I needed. Started a data dictionary on the wiki here: https://github.com/synthicity/activitysim/wiki/Data-Dictionary

Not as good: the multiple member households have some tricky logic in how they choose their CDAP. I got a good explanation from David Ory and will dig into multi-member households next.

e-lo · 2015-01-09T17:39:49Z

At some point it might be good to (since this is an example) write out exactly what is going on in the comments...in travel modeler ( not programmer shorthand ) terms.

I.e. cdap took me a few minutes to figure out what it was. I had to look at the roadmap and then I was like AHA...why didn't you say so! ( or maybe this is bc we just have the less sophisticated DAPs instead of CDAPs)

If it took me 5 min to figure out...my guess that somebody less familiar ( i.e. an intern!) will take longer.

This isnt a high priority for now, but let's keep it mind when we use shorthand and acronyms.

fscottfoti · 2015-02-10T00:03:13Z

Just a quick reminder, for anyone following this repo - this is what I will be working on this week. I believe I have the CDAP (coordinate daily activity pattern) running for 1 person households and will now be proceeding to 2 person households. If you guys would prefer that I be working on something else (e.g. if you don't need the C of CDAP), feel free to let me know.

Elizabeth, your comment about adding comments is important. I suggest we do a commenting and testing iteration after getting enough of a prototype going that we all think that the current approach is good. I don't to to do much polish on code that's still subject to significant revisions...

Workplace size coeffs

And all the alternatives, model, and all the new columns that are required to support it. Only about halfway through at this point but hopefully gets a bit faster going forward. Also added proper newlines to the csv file so they look ok outside of excel. Also started keeping a todo list in markdown to keep track of anything that will need revisiting before the model is fully usable.

still need to polish one or two things before opening a PR though, but pretty close

…ges to the code

for full time worker only at this point

only running for the full time worker person type at this time

…neration 140 lines or so to go!

there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

I didn't realize all the segments in the non mandatory model had the same spec - this made things much easier (i.e. I didn't have to definite 250 variables for every segment). Anyway this is now running and brings up a few questions which I will add to the readme.md.

a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

not working yet as far as model specifications and such

need to ask a few questions about the time windowing

no new functionality here - just splitting up the one large file into 8-10 smaller files. Now have a models directory and one file per model, as well as a tables directory and one file per table. Remember this is only a convention, so mixing in other aspects of the simulation framework where appropriate is expected.

sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

Nonmandatory tour schedule

File reorg

Explicitly testing situations when there are no interactions.

[ci-skip]

It's nice to have the specs not mixed up with alternative names.

So they can be used for evaluating variables with DataFrame.eval.

The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

These are rules that express things like "retired people can't do mandatory tours".

jiffyclub · 2015-03-09T19:41:54Z

Closing this since the PR isn't targeting the master branch.

remove deprecated method from trip scheduling

Updated Model Component Documentation

latest updates from other PRs

* School escorting estimation updates Most changes are needed to avoid crash if estimation run actually had no school escorting in the input data * blacken * updating to work with Pydantic and State object * adding missed columns necessary for no school escorting * blacken * handling zero escorting cases * removing duplicate code

jiffyclub force-pushed the cdap branch from c39cb6b to 0706c82Compare February 19, 2015 23:11

Merge pull request#18from synthicity/workplace-size-coeffs
411ee42
Workplace size coeffs

jiffyclub force-pushed the cdap branch 3 times, most recently from 0fdbcaf to ab5914aCompare February 23, 2015 23:48

fscottfoti added 23 commits February 23, 2015 17:40

finished up the rest of the rows of the mandatory tour generation model
ddf4b16
still need to polish one or two things before opening a PR though, but pretty close

comments, a few extra items on the todo list, and a few cosmetic chan…
8a311d9
…ges to the code

pep8 fixes
12f4eeb

adding csv formatted non mandatory tour config
59d8484
for full time worker only at this point

add the alternatives too
a8fd8ca

making the basic model for non mandatory tours
d2fac8f
only running for the full time worker person type at this time

the first 60 rows or so of the full time worker non mandatory tour ge…
19e4fa2
…neration 140 lines or so to go!

got to row 114
fb365d7

all but about 10 rows in non mandatory tours...
a6c32a9

spec is now complete
324c88f
there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

adding a few notes to the readme
0cabf8f

basic destination model working
524deba
a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

a couple of small bugs and a couple of comments
767a9a2

adding small coment to TODO list
df7fa25

basic pipeline of tour departure and duration model
53bf27c
not working yet as far as model specifications and such

have about half of the mandatory scheduling model implemented
bb43936
need to ask a few questions about the time windowing

filling in basic skeleton of non-mandatory tour scheduling
522f35d

experimental reorg splitting up large file into several smaller files
d83e62e

cleanup!
88e6f82
sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

pep8
78af0a8

fscottfotiand others added 23 commits March 9, 2015 10:52

Merge pull request#28from synthicity/nonmandatory-tour-schedule
cfb2c4e
Nonmandatory tour schedule

Merge pull request#29from synthicity/file-reorg
63fff26
File reorg

Test data for CDAP routines
7cdccc2

Test for make_interactions function
732df84

function for two- and three-person household interactions
e9e59ea

extra make_interactions tests
25950dc
Explicitly testing situations when there are no interactions.

Update read_model_spec docstring
b6f0f04
[ci-skip]

read specs as dataframes
fcee534
It's nice to have the specs not mixed up with alternative names.

function for evaluating variables from specs
871e227

thinking about how to calculate individual cdap utilities.
8cc6ecc

make interactions as dataframes, not series
45a477c
So they can be used for evaluating variables with DataFrame.eval.

function for applying "final rules" to individual cdap utilities
99b2aaf

update "final rules" alternative name to match specs
6514739

allow commented lines with # in spec CSV files
6487ea8

function and tests for calculating individual cdap utilities
f21ffcc

rethinking some of the test data
5bdff62

Remove final rules from individual utilities calc
fd00422
The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

update individual utilities result
aebfb96

function for combining individual utilities into household utilities
faf650c

move household utils to a test fixture
afd3c5b

function that applies "final rules" to household alternatives
bade4fe
These are rules that express things like "retired people can't do mandatory tours".

interim commit with all_people test
85c9881

adding example cdap configs back
b3faf56

jiffyclub force-pushed the cdap branch from 7090031 to b3faf56Compare March 9, 2015 19:40

jiffyclub closed this Mar 9, 2015

bstabler pushed a commit that referenced this pull request Oct 20, 2021
Merge pull request#11from SANDAG/develop
9c9498e
remove deprecated method from trip scheduling

jpn-- pushed a commit that referenced this pull request Feb 1, 2024
Merge pull request#11from camsys/cfg-documentation-navjs
200d73d
Updated Model Component Documentation

jpn-- pushed a commit that referenced this pull request Feb 13, 2024
Merge pull request#11from camsys/data-type-op-pd-cat
db03dae
latest updates from other PRs

jiffyclub force-pushed the cdap branch from c39cb6b to 0706c82Compare February 19, 2015 23:11

Merge pull request#18from synthicity/workplace-size-coeffs
411ee42
Workplace size coeffs

jiffyclub force-pushed the cdap branch 3 times, most recently from 0fdbcaf to ab5914aCompare February 23, 2015 23:48

fscottfoti added 23 commits February 23, 2015 17:40

finished up the rest of the rows of the mandatory tour generation model
ddf4b16
still need to polish one or two things before opening a PR though, but pretty close

comments, a few extra items on the todo list, and a few cosmetic chan…
8a311d9
…ges to the code

pep8 fixes
12f4eeb

adding csv formatted non mandatory tour config
59d8484
for full time worker only at this point

add the alternatives too
a8fd8ca

making the basic model for non mandatory tours
d2fac8f
only running for the full time worker person type at this time

the first 60 rows or so of the full time worker non mandatory tour ge…
19e4fa2
…neration 140 lines or so to go!

got to row 114
fb365d7

all but about 10 rows in non mandatory tours...
a6c32a9

spec is now complete
324c88f
there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

adding a few notes to the readme
0cabf8f

basic destination model working
524deba
a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

a couple of small bugs and a couple of comments
767a9a2

adding small coment to TODO list
df7fa25

basic pipeline of tour departure and duration model
53bf27c
not working yet as far as model specifications and such

have about half of the mandatory scheduling model implemented
bb43936
need to ask a few questions about the time windowing

filling in basic skeleton of non-mandatory tour scheduling
522f35d

experimental reorg splitting up large file into several smaller files
d83e62e

cleanup!
88e6f82
sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

pep8
78af0a8

fscottfotiand others added 23 commits March 9, 2015 10:52

Merge pull request#28from synthicity/nonmandatory-tour-schedule
cfb2c4e
Nonmandatory tour schedule

Merge pull request#29from synthicity/file-reorg
63fff26
File reorg

Test data for CDAP routines
7cdccc2

Test for make_interactions function
732df84

function for two- and three-person household interactions
e9e59ea

extra make_interactions tests
25950dc
Explicitly testing situations when there are no interactions.

Update read_model_spec docstring
b6f0f04
[ci-skip]

read specs as dataframes
fcee534
It's nice to have the specs not mixed up with alternative names.

function for evaluating variables from specs
871e227

thinking about how to calculate individual cdap utilities.
8cc6ecc

make interactions as dataframes, not series
45a477c
So they can be used for evaluating variables with DataFrame.eval.

function for applying "final rules" to individual cdap utilities
99b2aaf

update "final rules" alternative name to match specs
6514739

allow commented lines with # in spec CSV files
6487ea8

function and tests for calculating individual cdap utilities
f21ffcc

rethinking some of the test data
5bdff62

Remove final rules from individual utilities calc
fd00422
The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

update individual utilities result
aebfb96

function for combining individual utilities into household utilities
faf650c

move household utils to a test fixture
afd3c5b

function that applies "final rules" to household alternatives
bade4fe
These are rules that express things like "retired people can't do mandatory tours".

interim commit with all_people test
85c9881

adding example cdap configs back
b3faf56

jiffyclub force-pushed the cdap branch from 7090031 to b3faf56Compare March 9, 2015 19:40

jiffyclub closed this Mar 9, 2015

bstabler pushed a commit that referenced this pull request Oct 20, 2021
Merge pull request#11from SANDAG/develop
9c9498e
remove deprecated method from trip scheduling

jpn-- pushed a commit that referenced this pull request Feb 1, 2024
Merge pull request#11from camsys/cfg-documentation-navjs
200d73d
Updated Model Component Documentation

jpn-- pushed a commit that referenced this pull request Feb 13, 2024
Merge pull request#11from camsys/data-type-op-pd-cat
db03dae
latest updates from other PRs

jiffyclub force-pushed the cdap branch from c39cb6b to 0706c82Compare February 19, 2015 23:11

Merge pull request#18from synthicity/workplace-size-coeffs
411ee42
Workplace size coeffs

jiffyclub force-pushed the cdap branch 3 times, most recently from 0fdbcaf to ab5914aCompare February 23, 2015 23:48

fscottfoti added 23 commits February 23, 2015 17:40

finished up the rest of the rows of the mandatory tour generation model
ddf4b16
still need to polish one or two things before opening a PR though, but pretty close

comments, a few extra items on the todo list, and a few cosmetic chan…
8a311d9
…ges to the code

pep8 fixes
12f4eeb

adding csv formatted non mandatory tour config
59d8484
for full time worker only at this point

add the alternatives too
a8fd8ca

making the basic model for non mandatory tours
d2fac8f
only running for the full time worker person type at this time

the first 60 rows or so of the full time worker non mandatory tour ge…
19e4fa2
…neration 140 lines or so to go!

got to row 114
fb365d7

all but about 10 rows in non mandatory tours...
a6c32a9

spec is now complete
324c88f
there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

adding a few notes to the readme
0cabf8f

basic destination model working
524deba
a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

a couple of small bugs and a couple of comments
767a9a2

adding small coment to TODO list
df7fa25

basic pipeline of tour departure and duration model
53bf27c
not working yet as far as model specifications and such

have about half of the mandatory scheduling model implemented
bb43936
need to ask a few questions about the time windowing

filling in basic skeleton of non-mandatory tour scheduling
522f35d

experimental reorg splitting up large file into several smaller files
d83e62e

cleanup!
88e6f82
sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

pep8
78af0a8

fscottfotiand others added 23 commits March 9, 2015 10:52

Merge pull request#28from synthicity/nonmandatory-tour-schedule
cfb2c4e
Nonmandatory tour schedule

Merge pull request#29from synthicity/file-reorg
63fff26
File reorg

Test data for CDAP routines
7cdccc2

Test for make_interactions function
732df84

function for two- and three-person household interactions
e9e59ea

extra make_interactions tests
25950dc
Explicitly testing situations when there are no interactions.

Update read_model_spec docstring
b6f0f04
[ci-skip]

read specs as dataframes
fcee534
It's nice to have the specs not mixed up with alternative names.

function for evaluating variables from specs
871e227

thinking about how to calculate individual cdap utilities.
8cc6ecc

make interactions as dataframes, not series
45a477c
So they can be used for evaluating variables with DataFrame.eval.

function for applying "final rules" to individual cdap utilities
99b2aaf

update "final rules" alternative name to match specs
6514739

allow commented lines with # in spec CSV files
6487ea8

function and tests for calculating individual cdap utilities
f21ffcc

rethinking some of the test data
5bdff62

Remove final rules from individual utilities calc
fd00422
The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

update individual utilities result
aebfb96

function for combining individual utilities into household utilities
faf650c

move household utils to a test fixture
afd3c5b

function that applies "final rules" to household alternatives
bade4fe
These are rules that express things like "retired people can't do mandatory tours".

interim commit with all_people test
85c9881

adding example cdap configs back
b3faf56

jiffyclub force-pushed the cdap branch from 7090031 to b3faf56Compare March 9, 2015 19:40

jiffyclub closed this Mar 9, 2015

bstabler pushed a commit that referenced this pull request Oct 20, 2021
Merge pull request#11from SANDAG/develop
9c9498e
remove deprecated method from trip scheduling

jpn-- pushed a commit that referenced this pull request Feb 1, 2024
Merge pull request#11from camsys/cfg-documentation-navjs
200d73d
Updated Model Component Documentation

jpn-- pushed a commit that referenced this pull request Feb 13, 2024
Merge pull request#11from camsys/data-type-op-pd-cat
db03dae
latest updates from other PRs

jiffyclub force-pushed the cdap branch from c39cb6b to 0706c82Compare February 19, 2015 23:11

Merge pull request#18from synthicity/workplace-size-coeffs
411ee42
Workplace size coeffs

jiffyclub force-pushed the cdap branch 3 times, most recently from 0fdbcaf to ab5914aCompare February 23, 2015 23:48

fscottfoti added 23 commits February 23, 2015 17:40

finished up the rest of the rows of the mandatory tour generation model
ddf4b16
still need to polish one or two things before opening a PR though, but pretty close

comments, a few extra items on the todo list, and a few cosmetic chan…
8a311d9
…ges to the code

pep8 fixes
12f4eeb

adding csv formatted non mandatory tour config
59d8484
for full time worker only at this point

add the alternatives too
a8fd8ca

making the basic model for non mandatory tours
d2fac8f
only running for the full time worker person type at this time

the first 60 rows or so of the full time worker non mandatory tour ge…
19e4fa2
…neration 140 lines or so to go!

got to row 114
fb365d7

all but about 10 rows in non mandatory tours...
a6c32a9

spec is now complete
324c88f
there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

adding a few notes to the readme
0cabf8f

basic destination model working
524deba
a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

a couple of small bugs and a couple of comments
767a9a2

adding small coment to TODO list
df7fa25

basic pipeline of tour departure and duration model
53bf27c
not working yet as far as model specifications and such

have about half of the mandatory scheduling model implemented
bb43936
need to ask a few questions about the time windowing

filling in basic skeleton of non-mandatory tour scheduling
522f35d

experimental reorg splitting up large file into several smaller files
d83e62e

cleanup!
88e6f82
sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

pep8
78af0a8

fscottfotiand others added 23 commits March 9, 2015 10:52

Merge pull request#28from synthicity/nonmandatory-tour-schedule
cfb2c4e
Nonmandatory tour schedule

Merge pull request#29from synthicity/file-reorg
63fff26
File reorg

Test data for CDAP routines
7cdccc2

Test for make_interactions function
732df84

function for two- and three-person household interactions
e9e59ea

extra make_interactions tests
25950dc
Explicitly testing situations when there are no interactions.

Update read_model_spec docstring
b6f0f04
[ci-skip]

read specs as dataframes
fcee534
It's nice to have the specs not mixed up with alternative names.

function for evaluating variables from specs
871e227

thinking about how to calculate individual cdap utilities.
8cc6ecc

make interactions as dataframes, not series
45a477c
So they can be used for evaluating variables with DataFrame.eval.

function for applying "final rules" to individual cdap utilities
99b2aaf

update "final rules" alternative name to match specs
6514739

allow commented lines with # in spec CSV files
6487ea8

function and tests for calculating individual cdap utilities
f21ffcc

rethinking some of the test data
5bdff62

Remove final rules from individual utilities calc
fd00422
The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

update individual utilities result
aebfb96

function for combining individual utilities into household utilities
faf650c

move household utils to a test fixture
afd3c5b

function that applies "final rules" to household alternatives
bade4fe
These are rules that express things like "retired people can't do mandatory tours".

interim commit with all_people test
85c9881

adding example cdap configs back
b3faf56

jiffyclub force-pushed the cdap branch from 7090031 to b3faf56Compare March 9, 2015 19:40

jiffyclub closed this Mar 9, 2015

bstabler pushed a commit that referenced this pull request Oct 20, 2021
Merge pull request#11from SANDAG/develop
9c9498e
remove deprecated method from trip scheduling

jpn-- pushed a commit that referenced this pull request Feb 1, 2024
Merge pull request#11from camsys/cfg-documentation-navjs
200d73d
Updated Model Component Documentation

jpn-- pushed a commit that referenced this pull request Feb 13, 2024
Merge pull request#11from camsys/data-type-op-pd-cat
db03dae
latest updates from other PRs

jiffyclub force-pushed the cdap branch from c39cb6b to 0706c82Compare February 19, 2015 23:11

Merge pull request#18from synthicity/workplace-size-coeffs
411ee42
Workplace size coeffs

jiffyclub force-pushed the cdap branch 3 times, most recently from 0fdbcaf to ab5914aCompare February 23, 2015 23:48

fscottfoti added 23 commits February 23, 2015 17:40

finished up the rest of the rows of the mandatory tour generation model
ddf4b16
still need to polish one or two things before opening a PR though, but pretty close

comments, a few extra items on the todo list, and a few cosmetic chan…
8a311d9
…ges to the code

pep8 fixes
12f4eeb

adding csv formatted non mandatory tour config
59d8484
for full time worker only at this point

add the alternatives too
a8fd8ca

making the basic model for non mandatory tours
d2fac8f
only running for the full time worker person type at this time

the first 60 rows or so of the full time worker non mandatory tour ge…
19e4fa2
…neration 140 lines or so to go!

got to row 114
fb365d7

all but about 10 rows in non mandatory tours...
a6c32a9

spec is now complete
324c88f
there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

adding a few notes to the readme
0cabf8f

basic destination model working
524deba
a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

a couple of small bugs and a couple of comments
767a9a2

adding small coment to TODO list
df7fa25

basic pipeline of tour departure and duration model
53bf27c
not working yet as far as model specifications and such

have about half of the mandatory scheduling model implemented
bb43936
need to ask a few questions about the time windowing

filling in basic skeleton of non-mandatory tour scheduling
522f35d

experimental reorg splitting up large file into several smaller files
d83e62e

cleanup!
88e6f82
sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

pep8
78af0a8

fscottfotiand others added 23 commits March 9, 2015 10:52

Merge pull request#28from synthicity/nonmandatory-tour-schedule
cfb2c4e
Nonmandatory tour schedule

Merge pull request#29from synthicity/file-reorg
63fff26
File reorg

Test data for CDAP routines
7cdccc2

Test for make_interactions function
732df84

function for two- and three-person household interactions
e9e59ea

extra make_interactions tests
25950dc
Explicitly testing situations when there are no interactions.

Update read_model_spec docstring
b6f0f04
[ci-skip]

read specs as dataframes
fcee534
It's nice to have the specs not mixed up with alternative names.

function for evaluating variables from specs
871e227

thinking about how to calculate individual cdap utilities.
8cc6ecc

make interactions as dataframes, not series
45a477c
So they can be used for evaluating variables with DataFrame.eval.

function for applying "final rules" to individual cdap utilities
99b2aaf

update "final rules" alternative name to match specs
6514739

allow commented lines with # in spec CSV files
6487ea8

function and tests for calculating individual cdap utilities
f21ffcc

rethinking some of the test data
5bdff62

Remove final rules from individual utilities calc
fd00422
The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

update individual utilities result
aebfb96

function for combining individual utilities into household utilities
faf650c

move household utils to a test fixture
afd3c5b

function that applies "final rules" to household alternatives
bade4fe
These are rules that express things like "retired people can't do mandatory tours".

interim commit with all_people test
85c9881

adding example cdap configs back
b3faf56

jiffyclub force-pushed the cdap branch from 7090031 to b3faf56Compare March 9, 2015 19:40

jiffyclub closed this Mar 9, 2015

bstabler pushed a commit that referenced this pull request Oct 20, 2021
Merge pull request#11from SANDAG/develop
9c9498e
remove deprecated method from trip scheduling

jpn-- pushed a commit that referenced this pull request Feb 1, 2024
Merge pull request#11from camsys/cfg-documentation-navjs
200d73d
Updated Model Component Documentation

jpn-- pushed a commit that referenced this pull request Feb 13, 2024
Merge pull request#11from camsys/data-type-op-pd-cat
db03dae
latest updates from other PRs

jiffyclub force-pushed the cdap branch from c39cb6b to 0706c82Compare February 19, 2015 23:11

Merge pull request#18from synthicity/workplace-size-coeffs
411ee42
Workplace size coeffs

jiffyclub force-pushed the cdap branch 3 times, most recently from 0fdbcaf to ab5914aCompare February 23, 2015 23:48

fscottfoti added 23 commits February 23, 2015 17:40

finished up the rest of the rows of the mandatory tour generation model
ddf4b16
still need to polish one or two things before opening a PR though, but pretty close

comments, a few extra items on the todo list, and a few cosmetic chan…
8a311d9
…ges to the code

pep8 fixes
12f4eeb

adding csv formatted non mandatory tour config
59d8484
for full time worker only at this point

add the alternatives too
a8fd8ca

making the basic model for non mandatory tours
d2fac8f
only running for the full time worker person type at this time

the first 60 rows or so of the full time worker non mandatory tour ge…
19e4fa2
…neration 140 lines or so to go!

got to row 114
fb365d7

all but about 10 rows in non mandatory tours...
a6c32a9

spec is now complete
324c88f
there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

adding a few notes to the readme
0cabf8f

basic destination model working
524deba
a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

a couple of small bugs and a couple of comments
767a9a2

adding small coment to TODO list
df7fa25

basic pipeline of tour departure and duration model
53bf27c
not working yet as far as model specifications and such

have about half of the mandatory scheduling model implemented
bb43936
need to ask a few questions about the time windowing

filling in basic skeleton of non-mandatory tour scheduling
522f35d

experimental reorg splitting up large file into several smaller files
d83e62e

cleanup!
88e6f82
sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

pep8
78af0a8

fscottfotiand others added 23 commits March 9, 2015 10:52

Merge pull request#28from synthicity/nonmandatory-tour-schedule
cfb2c4e
Nonmandatory tour schedule

Merge pull request#29from synthicity/file-reorg
63fff26
File reorg

Test data for CDAP routines
7cdccc2

Test for make_interactions function
732df84

function for two- and three-person household interactions
e9e59ea

extra make_interactions tests
25950dc
Explicitly testing situations when there are no interactions.

Update read_model_spec docstring
b6f0f04
[ci-skip]

read specs as dataframes
fcee534
It's nice to have the specs not mixed up with alternative names.

function for evaluating variables from specs
871e227

thinking about how to calculate individual cdap utilities.
8cc6ecc

make interactions as dataframes, not series
45a477c
So they can be used for evaluating variables with DataFrame.eval.

function for applying "final rules" to individual cdap utilities
99b2aaf

update "final rules" alternative name to match specs
6514739

allow commented lines with # in spec CSV files
6487ea8

function and tests for calculating individual cdap utilities
f21ffcc

rethinking some of the test data
5bdff62

Remove final rules from individual utilities calc
fd00422
The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

update individual utilities result
aebfb96

function for combining individual utilities into household utilities
faf650c

move household utils to a test fixture
afd3c5b

function that applies "final rules" to household alternatives
bade4fe
These are rules that express things like "retired people can't do mandatory tours".

interim commit with all_people test
85c9881

adding example cdap configs back
b3faf56

jiffyclub force-pushed the cdap branch from 7090031 to b3faf56Compare March 9, 2015 19:40

jiffyclub closed this Mar 9, 2015

bstabler pushed a commit that referenced this pull request Oct 20, 2021
Merge pull request#11from SANDAG/develop
9c9498e
remove deprecated method from trip scheduling

jpn-- pushed a commit that referenced this pull request Feb 1, 2024
Merge pull request#11from camsys/cfg-documentation-navjs
200d73d
Updated Model Component Documentation

jpn-- pushed a commit that referenced this pull request Feb 13, 2024
Merge pull request#11from camsys/data-type-op-pd-cat
db03dae
latest updates from other PRs

jiffyclub force-pushed the cdap branch from c39cb6b to 0706c82Compare February 19, 2015 23:11

Merge pull request#18from synthicity/workplace-size-coeffs
411ee42
Workplace size coeffs

jiffyclub force-pushed the cdap branch 3 times, most recently from 0fdbcaf to ab5914aCompare February 23, 2015 23:48

fscottfoti added 23 commits February 23, 2015 17:40

finished up the rest of the rows of the mandatory tour generation model
ddf4b16
still need to polish one or two things before opening a PR though, but pretty close

comments, a few extra items on the todo list, and a few cosmetic chan…
8a311d9
…ges to the code

pep8 fixes
12f4eeb

adding csv formatted non mandatory tour config
59d8484
for full time worker only at this point

add the alternatives too
a8fd8ca

making the basic model for non mandatory tours
d2fac8f
only running for the full time worker person type at this time

the first 60 rows or so of the full time worker non mandatory tour ge…
19e4fa2
…neration 140 lines or so to go!

got to row 114
fb365d7

all but about 10 rows in non mandatory tours...
a6c32a9

spec is now complete
324c88f
there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

adding a few notes to the readme
0cabf8f

basic destination model working
524deba
a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

a couple of small bugs and a couple of comments
767a9a2

adding small coment to TODO list
df7fa25

basic pipeline of tour departure and duration model
53bf27c
not working yet as far as model specifications and such

have about half of the mandatory scheduling model implemented
bb43936
need to ask a few questions about the time windowing

filling in basic skeleton of non-mandatory tour scheduling
522f35d

experimental reorg splitting up large file into several smaller files
d83e62e

cleanup!
88e6f82
sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

pep8
78af0a8

fscottfotiand others added 23 commits March 9, 2015 10:52

Merge pull request#28from synthicity/nonmandatory-tour-schedule
cfb2c4e
Nonmandatory tour schedule

Merge pull request#29from synthicity/file-reorg
63fff26
File reorg

Test data for CDAP routines
7cdccc2

Test for make_interactions function
732df84

function for two- and three-person household interactions
e9e59ea

extra make_interactions tests
25950dc
Explicitly testing situations when there are no interactions.

Update read_model_spec docstring
b6f0f04
[ci-skip]

read specs as dataframes
fcee534
It's nice to have the specs not mixed up with alternative names.

function for evaluating variables from specs
871e227

thinking about how to calculate individual cdap utilities.
8cc6ecc

make interactions as dataframes, not series
45a477c
So they can be used for evaluating variables with DataFrame.eval.

function for applying "final rules" to individual cdap utilities
99b2aaf

update "final rules" alternative name to match specs
6514739

allow commented lines with # in spec CSV files
6487ea8

function and tests for calculating individual cdap utilities
f21ffcc

rethinking some of the test data
5bdff62

Remove final rules from individual utilities calc
fd00422
The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

update individual utilities result
aebfb96

function for combining individual utilities into household utilities
faf650c

move household utils to a test fixture
afd3c5b

function that applies "final rules" to household alternatives
bade4fe
These are rules that express things like "retired people can't do mandatory tours".

interim commit with all_people test
85c9881

adding example cdap configs back
b3faf56

jiffyclub force-pushed the cdap branch from 7090031 to b3faf56Compare March 9, 2015 19:40

jiffyclub closed this Mar 9, 2015

bstabler pushed a commit that referenced this pull request Oct 20, 2021
Merge pull request#11from SANDAG/develop
9c9498e
remove deprecated method from trip scheduling

jpn-- pushed a commit that referenced this pull request Feb 1, 2024
Merge pull request#11from camsys/cfg-documentation-navjs
200d73d
Updated Model Component Documentation

jpn-- pushed a commit that referenced this pull request Feb 13, 2024
Merge pull request#11from camsys/data-type-op-pd-cat
db03dae
latest updates from other PRs

jiffyclub force-pushed the cdap branch from c39cb6b to 0706c82Compare February 19, 2015 23:11

Merge pull request#18from synthicity/workplace-size-coeffs
411ee42
Workplace size coeffs

jiffyclub force-pushed the cdap branch 3 times, most recently from 0fdbcaf to ab5914aCompare February 23, 2015 23:48

fscottfoti added 23 commits February 23, 2015 17:40

finished up the rest of the rows of the mandatory tour generation model
ddf4b16
still need to polish one or two things before opening a PR though, but pretty close

comments, a few extra items on the todo list, and a few cosmetic chan…
8a311d9
…ges to the code

pep8 fixes
12f4eeb

adding csv formatted non mandatory tour config
59d8484
for full time worker only at this point

add the alternatives too
a8fd8ca

making the basic model for non mandatory tours
d2fac8f
only running for the full time worker person type at this time

the first 60 rows or so of the full time worker non mandatory tour ge…
19e4fa2
…neration 140 lines or so to go!

got to row 114
fb365d7

all but about 10 rows in non mandatory tours...
a6c32a9

spec is now complete
324c88f
there are a couple of issues - the window residual and the presence of X type not including chooser other than that this is looking pretty good

adding a few notes to the readme
0cabf8f

basic destination model working
524deba
a few caveats 1) this has no mode choice logsums 2) it uses fully random sampling 3) it's missing size terms 4) the escort trip type is not split into with and without child ... but basic workflow is completely there - every tour now has a destination

a couple of small bugs and a couple of comments
767a9a2

adding small coment to TODO list
df7fa25

basic pipeline of tour departure and duration model
53bf27c
not working yet as far as model specifications and such

have about half of the mandatory scheduling model implemented
bb43936
need to ask a few questions about the time windowing

filling in basic skeleton of non-mandatory tour scheduling
522f35d

experimental reorg splitting up large file into several smaller files
d83e62e

cleanup!
88e6f82
sharing some merges between models also sharing the vectorized tour choice between mandatory and non_mandatory scheduling (should move to activitysim)

pep8
78af0a8

fscottfotiand others added 23 commits March 9, 2015 10:52

Merge pull request#28from synthicity/nonmandatory-tour-schedule
cfb2c4e
Nonmandatory tour schedule

Merge pull request#29from synthicity/file-reorg
63fff26
File reorg

Test data for CDAP routines
7cdccc2

Test for make_interactions function
732df84

function for two- and three-person household interactions
e9e59ea

extra make_interactions tests
25950dc
Explicitly testing situations when there are no interactions.

Update read_model_spec docstring
b6f0f04
[ci-skip]

read specs as dataframes
fcee534
It's nice to have the specs not mixed up with alternative names.

function for evaluating variables from specs
871e227

thinking about how to calculate individual cdap utilities.
8cc6ecc

make interactions as dataframes, not series
45a477c
So they can be used for evaluating variables with DataFrame.eval.

function for applying "final rules" to individual cdap utilities
99b2aaf

update "final rules" alternative name to match specs
6514739

allow commented lines with # in spec CSV files
6487ea8

function and tests for calculating individual cdap utilities
f21ffcc

rethinking some of the test data
5bdff62

Remove final rules from individual utilities calc
fd00422
The final rules really need to be applied after utilities have been calculated for an entire household so that a household can't choose a certain alternative at all.

update individual utilities result
aebfb96

function for combining individual utilities into household utilities
faf650c

move household utils to a test fixture
afd3c5b

function that applies "final rules" to household alternatives
bade4fe
These are rules that express things like "retired people can't do mandatory tours".

interim commit with all_people test
85c9881

adding example cdap configs back
b3faf56

jiffyclub force-pushed the cdap branch from 7090031 to b3faf56Compare March 9, 2015 19:40

jiffyclub closed this Mar 9, 2015

bstabler pushed a commit that referenced this pull request Oct 20, 2021
Merge pull request#11from SANDAG/develop
9c9498e
remove deprecated method from trip scheduling

jpn-- pushed a commit that referenced this pull request Feb 1, 2024
Merge pull request#11from camsys/cfg-documentation-navjs
200d73d
Updated Model Component Documentation

jpn-- pushed a commit that referenced this pull request Feb 13, 2024
Merge pull request#11from camsys/data-type-op-pd-cat
db03dae
latest updates from other PRs

Uh oh!

Conversation

fscottfoti commented Jan 7, 2015

Uh oh!

e-lo commented Jan 9, 2015

Uh oh!

fscottfoti commented Feb 10, 2015

Uh oh!

jiffyclub commented Mar 9, 2015

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

fscottfoti commented Jan 7, 2015

Uh oh!

e-lo commented Jan 9, 2015

Uh oh!

fscottfoti commented Feb 10, 2015

Uh oh!

jiffyclub commented Mar 9, 2015

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

fscottfoti commented Jan 7, 2015

Uh oh!

e-lo commented Jan 9, 2015

Uh oh!

fscottfoti commented Feb 10, 2015

Uh oh!

jiffyclub commented Mar 9, 2015

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

fscottfoti commented Jan 7, 2015

Uh oh!

e-lo commented Jan 9, 2015

Uh oh!

fscottfoti commented Feb 10, 2015

Uh oh!

jiffyclub commented Mar 9, 2015

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

fscottfoti commented Jan 7, 2015

Uh oh!

e-lo commented Jan 9, 2015

Uh oh!

fscottfoti commented Feb 10, 2015

Uh oh!