Menu
▾
▴
transims-developers — developer list
You can subscribe to this list here.
| 2007 |
Jan
|
Feb
|
Mar
(6) |
Apr
|
May
(2) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Clark H. <cha...@vo...> - 2020-06-22 18:29:46
|
Good afternoon, We wanted to follow up with you to make sure you received our last email. We are experiencing some difficulty parsing and contextualizing some of the data exported from TRANSIMS for the 2020 SMC Data Challenge. Please see the quoted text below for more information. Any clarification on these apparent outliers in our data would be greatly appreciated. On 6/18/2020 7:35 PM, Clark Hathaway wrote: > > Hello Sponsors, > > > We are a team taking on Challenge 4 of the 2020 SMC Data Challenge, > and we would like clarification regarding possible discrepancies we > noticed in the traffic simulation snapshot dataset. > > > Specifically, many of the records in this dataset seem to have > position data that is inconsistent with both the provided road network > and with the actual geography of the Chicago area. We’ve identified > three main problems: > > * > > Over half of the records apparently have link offsets (distances > travelled) that are greater than the actual lengths of their > associated links. > > * > > On top of that, many records have UTM coordinates that lie inside > of buildings, on train tracks, in rivers, or are even in Lake > Michigan. > > * > > Even when the link offset within a record is valid, it often does > not match the UTM position in the record: computing the absolute > UTM position of the vehicle from the link and offset information > results in positions that can be hundreds or thousands of meters > away from the stored UTM position. > > > One specific example of the first problem can be seen in row 55 of > file Snapshot_2000000.csv, describing vehicle 34970 at time 7:24. It > is listed as travelling down link 1210 with an offset of 202.5 meters; > however, link 1210 should only be 14.6 meters long, based on the > coordinates provided in the road network dataset. > > After taking a random sample of roughly 5% of the dataset (1.2 million > records), we found that almost 685 thousand records (or about 55% of > the sample) have this problem. > > > An example of the second and third problems can be seen in row 105,310 > of file Snapshot_4000000.csv, which describes vehicle 34271 at time > 9:00. This record contains a valid link and an offset that is > consistent with the computed length of that link; however, the given > UTM coordinates for this vehicle (16N 447301 4635366) place it in the > middle of the Chicago River. > > We tried computing a new position for the vehicle based on the link > and offset information provided in the record, by using the offset to > interpolate between the endpoints of the associated link. However, the > position as calculated by this method is 1086 meters away from the > position stored in the record. > > > Furthermore, we’d like to ask if parked cars are simulated by > TRANSIMS, and if that might cause simulated vehicles to appear to be > inside of buildings. > > > Thank you for your time. > > > Sincerely, > > Sebastian Mobo and Clark Hathaway > Sincerely, Sebastian Mobo and Clark Hathaway |
|
From: Clark H. <cha...@vo...> - 2020-06-18 23:59:03
|
Hello Sponsors,
We are a team taking on Challenge 4 of the 2020 SMC Data Challenge, and
we would like clarification regarding possible discrepancies we noticed
in the traffic simulation snapshot dataset.
Specifically, many of the records in this dataset seem to have position
data that is inconsistent with both the provided road network and with
the actual geography of the Chicago area. We’ve identified three main
problems:
*
Over half of the records apparently have link offsets (distances
travelled) that are greater than the actual lengths of their
associated links.
*
On top of that, many records have UTM coordinates that lie inside of
buildings, on train tracks, in rivers, or are even in Lake Michigan.
*
Even when the link offset within a record is valid, it often does
not match the UTM position in the record: computing the absolute UTM
position of the vehicle from the link and offset information results
in positions that can be hundreds or thousands of meters away from
the stored UTM position.
One specific example of the first problem can be seen in row 55 of file
Snapshot_2000000.csv, describing vehicle 34970 at time 7:24. It is
listed as travelling down link 1210 with an offset of 202.5 meters;
however, link 1210 should only be 14.6 meters long, based on the
coordinates provided in the road network dataset.
After taking a random sample of roughly 5% of the dataset (1.2 million
records), we found that almost 685 thousand records (or about 55% of the
sample) have this problem.
An example of the second and third problems can be seen in row 105,310
of file Snapshot_4000000.csv, which describes vehicle 34271 at time
9:00. This record contains a valid link and an offset that is consistent
with the computed length of that link; however, the given UTM
coordinates for this vehicle (16N 447301 4635366) place it in the middle
of the Chicago River.
We tried computing a new position for the vehicle based on the link and
offset information provided in the record, by using the offset to
interpolate between the endpoints of the associated link. However, the
position as calculated by this method is 1086 meters away from the
position stored in the record.
Furthermore, we’d like to ask if parked cars are simulated by TRANSIMS,
and if that might cause simulated vehicles to appear to be inside of
buildings.
Thank you for your time.
Sincerely,
Sebastian Mobo and Clark Hathaway
|
|
From: Brian G. <bri...@gm...> - 2007-11-28 14:51:00
|
This is a test to see if the list is working. Please do not reply. |
|
From: <Bri...@do...> - 2007-07-27 12:23:03
|
=20 =20 ________________________________ From: Roden, David [mailto:dav...@dm...]=20 Sent: Friday, July 27, 2007 7:46 AM To: Ley, Hubert; Toonen, Brian R. Cc: Karonis, Nicholas T.; Park, Young Soo; Gardner, Brian <FHWA> Subject: Version 4.1 Router =20 I have completed the first round of updates to the 4.1 Router to utilize the Plan_Data class designed for 5.0. I have tested it and (except for the generalized cost field which isn't used for anything) it reproduces the highway and transit plans in the 3.x/4.0 format generated by the 4.0 Router. If a conference call is desirable to go over this or discuss what you have learned / decided this week, I am available any time today. The next step from my perspective is to split the Plan_Build method into a separate class using the Static_Service interface. I might have time to take a first cut at that over the weekend if that would be helpful. dbr =20 David B. Roden, P.E. Senior Consulting Manager AECOM Consult, An affiliate of DMJM Harris 3101 Wilson Boulevard, 4th Floor Arlington, VA. 22201 E dav...@dm... T 703.682.5079 F 703.682.5001 =20 =20 |
|
From: Le, P. <pa...@no...> - 2007-05-29 15:10:18
|
To All Transims Developers,=20 =20 The Subversion repository has been restructured successfully. All works can be resumed normally. Thank you for your patient. =20 Regards, =20 Paul H. Le Noblis Wireless Communication and Mobile Computing 703-610-2397 ________________________________ From: Le, Paul=20 Sent: Tuesday, May 22, 2007 1:43 PM To: 'tra...@li...' Cc: Vasudevan, Meenakshy Subject: Repository Restructure Notice =20 To All Transims Developers, =20 Per FHWA request, the Subversion repository will be restructured this Friday 5/25/07. Please commit all your changes by noon on Friday. Thank you! =20 =20 Regards, =20 Paul H. Le Noblis Wireless Communication and Mobile Computing 703-610-2397 =20 |
|
From: Le, P. <pa...@no...> - 2007-05-22 17:43:10
|
To All Transims Developers, =20 Per FHWA request, the Subversion repository will be restructured this Friday 5/25/07. Please commit all your changes by noon on Friday. Thank you! =20 =20 Regards, =20 Paul H. Le Noblis Wireless Communication and Mobile Computing 703-610-2397 =20 |
|
From: Le, P. <pa...@no...> - 2007-03-27 17:19:15
|
HI=20Dave, If=20you=20have=20not=20made=20any=20changes=20to=20your=20working=20copie= s=20since=20Saturday, then=20I=20would=20suggest=20to=20use=20the=20command=20SNV->import=20to=20= import=20a=20new working=20copy=20onto=20your=20computer.=20Then,=20copy=20any=20files=20th= at=20you=20may=20have changes=20from=20your=20old=20local=20working=20copy=20into=20the=20new=20= working=20copy directory.=20=20 If=20your=20old=20files=20are=20deleted=20from=20the=20updates=20on=20the=20= lower=20level folders,=20then=20you=20can=20use=20the=20command=20SVN->Revert=20to=20try= =20bring=20them back. Another=20option=20is=20using=20the=20Switch=20command=20that=20Brian=20su= ggested. Regards, =20 Paul=20H.=20Le Noblis Wireless=20Communication=20and=20Mobile=20Computing 703-610-2397 -----Original=20Message----- From:=20B...@do...=20[mailto:Bri...@do...]=20 Sent:=20Tuesday,=20March=2027,=202007=2012:03=20PM To:=20d...@dm...;=20Le,=20Paul Cc:=20t...@li... Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured Sounds=20like=20the=20root=20of=20your=20repository=20is=20set=20as=20 https://transims.svn.sourceforge.net/svnroot/transims/trunk which=20doesn't=20exist=20any=20longer. FYI:=20I=20had=20been=20updating=20the=20entire=20repository=20to=20my=20l= ocal=20copy.=20It's inefficient=20but=20it=20worked=20for=20my=20purposes.=20I=20haven't=20mas= tered=20the appropriate=20use=20of=20the=20"switch"=20command=20yet,=20so=20I'll=20lea= ve=20that=20for=20Paul to=20explain.=20Whenever=20I=20try=20it,=20I=20end=20up=20with=20folder=20= and=20file=20name conflicts. Use=20"switch"=20to=20change=20the=20SVN=20URL.=20You=20may=20want=20to=20= start=20with=20a=20clean folder,=20if=20possible=20as=20switch=20won't=20delete=20or=20overwrite=20= a=20local=20folder. In=20file=20explorer,=20rclick=20the=20root=20folder=20of=20your=20local=20= copy,=20select tortoiseSVN,=20select=20switch.=20You=20will=20get=20a=20dialogue=20at=20t= his=20point, prompting=20for=20a=20URL To=20copy=20just=20the=20current=20version/trunk=20you=20had=20previously,= =20use=20the=20url: https://transims.svn.sourceforge.net/svnroot/transims/main_path/trunk -----Original=20Message----- From:=20Roden,=20David=20[mailto:dav...@dm...]=20 Sent:=20Tuesday,=20March=2027,=202007=2011:27=20AM To:=20Gardner,=20Brian=20<FHWA>;=20p...@no... Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured I=20don't=20believe=20so. dbr David=20B.=20Roden,=20P.E. Senior=20Consulting=20Manager AECOM=20Consult,=20An=20affiliate=20of=20DMJM=20Harris 3101=20Wilson=20Boulevard,=204th=20Floor Arlington,=20VA.=20=2022201 E=20d...@dm... T=20703.682.5079=20=20F=20703.682.5001 =20 -----Original=20Message----- From:=20B...@do...=20[mailto:Bri...@do...]=20 Sent:=20Tuesday,=20March=2027,=202007=2011:25=20AM To:=20Roden,=20David;=20p...@no... Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured Before=20the=20restructuring,=20could=20you=20see=20a=20/test=20folder=20i= n=20the=20root folder=20of=20you=20local=20repository? -----Original=20Message----- From:=20Roden,=20David=20[mailto:dav...@dm...]=20 Sent:=20Tuesday,=20March=2027,=202007=2011:16=20AM To:=20Gardner,=20Brian=20<FHWA>;=20p...@no... Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured It=20is=20or=20"was".=20=20It=20looks=20like=20the=20lower=20level=20updat= es=20wiped=20out=20the "case=20studies"=20and=20"doc"=20directories=20I=20use=20to=20have=20under= =20the "SourceForge"=20directory.=20=20Now=20all=20I=20have=20is=20".svn"=20and=20= "src" dbr David=20B.=20Roden,=20P.E. Senior=20Consulting=20Manager AECOM=20Consult,=20An=20affiliate=20of=20DMJM=20Harris 3101=20Wilson=20Boulevard,=204th=20Floor Arlington,=20VA.=20=2022201 E=20d...@dm... T=20703.682.5079=20=20F=20703.682.5001 =20 -----Original=20Message----- From:=20B...@do...=20[mailto:Bri...@do...]=20 Sent:=20Tuesday,=20March=2027,=202007=2011:12=20AM To:=20Roden,=20David;=20p...@no... Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured /trunk=20was=20one=20of=20the=20top=20folders=20in=20the=20old=20repositor= y=20structure.=20 Is=20the=20reported=20URL=20path=20associated=20with=20the=20highest=20fol= der=20within=20your local=20copy=20of=20the=20repository? -----Original=20Message----- From:=20Roden,=20David=20[mailto:dav...@dm...]=20 Sent:=20Tuesday,=20March=2027,=202007=2011:06=20AM To:=20Gardner,=20Brian=20<FHWA>;=20p...@no... Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured My=20URL=20path=20has=20/trunk=20after=20the=20one=20you=20listed=20below,= =20but=20it=20does=20not let=20me=20change=20the=20path.=20=20Any=20idea=20how=20I=20change=20the=20= path? dbr David=20B.=20Roden,=20P.E. Senior=20Consulting=20Manager AECOM=20Consult,=20An=20affiliate=20of=20DMJM=20Harris 3101=20Wilson=20Boulevard,=204th=20Floor Arlington,=20VA.=20=2022201 E=20d...@dm... T=20703.682.5079=20=20F=20703.682.5001 =20 -----Original=20Message----- From:=20B...@do...=20[mailto:Bri...@do...]=20 Sent:=20Tuesday,=20March=2027,=202007=2010:55=20AM To:=20Roden,=20David;=20p...@no... Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured You=20might=20want=20to=20verify=20the=20repository=20URL. I=20have=20my=20local=20copy=20stored=20as=20C:\TRANSIMS\SourceForge The=20properties=20of=20my=20local=20copy=20folder=20(in=20file=20explorer= :=20rclick, properties,=20Subversion=20tab)=20lists=20the=20repository=20url=20as https://transims.svn.sourceforge.net/svnroot/transims As=20for=20changing=20the=20locally=20stored=20UID's,=20you=20may=20want=20= to=20wait=20to=20try this=20until=20you've=20figured=20out=20the=20connection=20problem: As=20far=20as=20I=20can=20tell,=20tortoiseSVN=20encrypts=20the=20password=20= string=20found=20in the=20local=20application=20data=20directory.=20The=20only=20way=20I've=20= found=20to=20change the=20UID=20is=20to=20clear=20all=20of=20them=20(since=20you're=20only=20u= sing=20one=20it shouldn't=20be=20a=20big=20deal).=20In=20file=20explorer:=20rclick=20on=20= any=20folder,=20select TortoiseSVN=20in=20the=20context=20menu,=20select=20settings.=20In=20the=20= settings dialogue:=20select=20saved=20data=20from=20the=20list=20on=20the=20left=20= side,=20and=20click the=20Clear=20button=20to=20the=20right=20of=20Authentication=20data.=20Yo= u=20can=20do=20updates without=20authentication,=20but=20you'll=20need=20to=20enter=20the=20usern= ame/pwd=20pair you=20want=20to=20use=20before=20you=20can=20make=20commits. -----Original=20Message----- From:=20Roden,=20David=20[mailto:dav...@dm...]=20 Sent:=20Tuesday,=20March=2027,=202007=2010:26=20AM To:=20Gardner,=20Brian=20<FHWA>;=20p...@no... Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured I=20don't=20know=20how=20to=20change=20my=20user=20ID.=20=20I=20assume=20i= t=20is=20still=20aecom,=20but I=20haven't=20found=20any=20form=20/=20interface=20that=20tells=20me=20tha= t.=20=20 The=20update=20error=20message=20is: Error=09REPORT=20request=20failed=20on=20'/svnroot/transims/!svn/vcc/defau= lt' Error=09Target=20path=20does=20not=20exist dbr David=20B.=20Roden,=20P.E. Senior=20Consulting=20Manager AECOM=20Consult,=20An=20affiliate=20of=20DMJM=20Harris 3101=20Wilson=20Boulevard,=204th=20Floor Arlington,=20VA.=20=2022201 E=20d...@dm... T=20703.682.5079=20=20F=20703.682.5001 =20 -----Original=20Message----- From:=20B...@do...=20[mailto:Bri...@do...]=20 Sent:=20Tuesday,=20March=2027,=202007=2010:12=20AM To:=20Roden,=20David;=20p...@no... Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured I=20just=20tried=20an=20update=20and=20it=20seems=20to=20be=20working.=20T= he=20aecom=20UID=20is still=20active=20on=20the=20project. -----Original=20Message----- From:=20Roden,=20David=20[mailto:dav...@dm...]=20 Sent:=20Tuesday,=20March=2027,=202007=2010:06=20AM To:=20Le,=20Paul Cc:=20Gardner,=20Brian=20<FHWA> Subject:=20RE:=20[transims-developers]=20Subversion=20repository=20has=20b= een restructured My=20svn=20update=20failed=20to=20find=20the=20connection.=20=20Any=20sugg= estions=20about=20what I=20need=20to=20change=20to=20get=20reconnected? dbr David=20B.=20Roden,=20P.E. Senior=20Consulting=20Manager AECOM=20Consult,=20An=20affiliate=20of=20DMJM=20Harris 3101=20Wilson=20Boulevard,=204th=20Floor Arlington,=20VA.=20=2022201 E=20d...@dm... T=20703.682.5079=20=20F=20703.682.5001 =20 -----Original=20Message----- From:=20t...@li... [mailto:tra...@li...]=20On=20Behalf=20= Of Le,=20Paul Sent:=20Monday,=20March=2026,=202007=201:10=20PM To:=20t...@li... Subject:=20[transims-developers]=20Subversion=20repository=20has=20been restructured To=20All=20Developer/Subversion=20users, =20 The=20Subversion=20repository=20has=20been=20restructured=20over=20the=20w= eekend.=20=20All your=20current=20development=20will=20continue=20under=20the=20new=20top=20= level=20folder called=20"main-path".=20=20Please=20update=20your=20local=20working=20copi= es=20using=20the command=20svn.>update,=20before=20making=20any=20new=20changes,=20and=20be= fore committing=20any=20new=20changes=20to=20the=20repository.=20=20 =20 It=20is=20normally=20good=20practice=20to=20run=20the=20command=20svn->upd= ate=20to=20get=20all the=20latest=20updates=20from=20the=20repository=20server=20before=20makin= g=20any=20new changes=20or=20committing=20any=20new=20changes. =20 =20 =20 =20 =20 Regards, =20 Paul=20H.=20Le Noblis Wireless=20Communication=20and=20Mobile=20Computing 703-610-2397 ______________________________________________________________________ We=20recently=20changed=20our=20name=20from=20Mitretek=20Systems=20to=20No= blis=20-=20www.noblis.org. ______________________________________________________________________ |
|
From: <Bri...@do...> - 2007-03-27 16:03:45
|
Sounds like the root of your repository is set as=20 https://transims.svn.sourceforge.net/svnroot/transims/trunk which doesn't exist any longer. FYI: I had been updating the entire repository to my local copy. It's inefficient but it worked for my purposes. I haven't mastered the appropriate use of the "switch" command yet, so I'll leave that for Paul to explain. Whenever I try it, I end up with folder and file name conflicts. Use "switch" to change the SVN URL. You may want to start with a clean folder, if possible as switch won't delete or overwrite a local folder. In file explorer, rclick the root folder of your local copy, select tortoiseSVN, select switch. You will get a dialogue at this point, prompting for a URL To copy just the current version/trunk you had previously, use the url: https://transims.svn.sourceforge.net/svnroot/transims/main_path/trunk -----Original Message----- From: Roden, David [mailto:dav...@dm...]=20 Sent: Tuesday, March 27, 2007 11:27 AM To: Gardner, Brian <FHWA>; pa...@no... Subject: RE: [transims-developers] Subversion repository has been restructured I don't believe so. dbr David B. Roden, P.E. Senior Consulting Manager AECOM Consult, An affiliate of DMJM Harris 3101 Wilson Boulevard, 4th Floor Arlington, VA. 22201 E dav...@dm... T 703.682.5079 F 703.682.5001 =20 -----Original Message----- From: Bri...@do... [mailto:Bri...@do...]=20 Sent: Tuesday, March 27, 2007 11:25 AM To: Roden, David; pa...@no... Subject: RE: [transims-developers] Subversion repository has been restructured Before the restructuring, could you see a /test folder in the root folder of you local repository? -----Original Message----- From: Roden, David [mailto:dav...@dm...]=20 Sent: Tuesday, March 27, 2007 11:16 AM To: Gardner, Brian <FHWA>; pa...@no... Subject: RE: [transims-developers] Subversion repository has been restructured It is or "was". It looks like the lower level updates wiped out the "case studies" and "doc" directories I use to have under the "SourceForge" directory. Now all I have is ".svn" and "src" dbr David B. Roden, P.E. Senior Consulting Manager AECOM Consult, An affiliate of DMJM Harris 3101 Wilson Boulevard, 4th Floor Arlington, VA. 22201 E dav...@dm... T 703.682.5079 F 703.682.5001 =20 -----Original Message----- From: Bri...@do... [mailto:Bri...@do...]=20 Sent: Tuesday, March 27, 2007 11:12 AM To: Roden, David; pa...@no... Subject: RE: [transims-developers] Subversion repository has been restructured /trunk was one of the top folders in the old repository structure.=20 Is the reported URL path associated with the highest folder within your local copy of the repository? -----Original Message----- From: Roden, David [mailto:dav...@dm...]=20 Sent: Tuesday, March 27, 2007 11:06 AM To: Gardner, Brian <FHWA>; pa...@no... Subject: RE: [transims-developers] Subversion repository has been restructured My URL path has /trunk after the one you listed below, but it does not let me change the path. Any idea how I change the path? dbr David B. Roden, P.E. Senior Consulting Manager AECOM Consult, An affiliate of DMJM Harris 3101 Wilson Boulevard, 4th Floor Arlington, VA. 22201 E dav...@dm... T 703.682.5079 F 703.682.5001 =20 -----Original Message----- From: Bri...@do... [mailto:Bri...@do...]=20 Sent: Tuesday, March 27, 2007 10:55 AM To: Roden, David; pa...@no... Subject: RE: [transims-developers] Subversion repository has been restructured You might want to verify the repository URL. I have my local copy stored as C:\TRANSIMS\SourceForge The properties of my local copy folder (in file explorer: rclick, properties, Subversion tab) lists the repository url as https://transims.svn.sourceforge.net/svnroot/transims As for changing the locally stored UID's, you may want to wait to try this until you've figured out the connection problem: As far as I can tell, tortoiseSVN encrypts the password string found in the local application data directory. The only way I've found to change the UID is to clear all of them (since you're only using one it shouldn't be a big deal). In file explorer: rclick on any folder, select TortoiseSVN in the context menu, select settings. In the settings dialogue: select saved data from the list on the left side, and click the Clear button to the right of Authentication data. You can do updates without authentication, but you'll need to enter the username/pwd pair you want to use before you can make commits. -----Original Message----- From: Roden, David [mailto:dav...@dm...]=20 Sent: Tuesday, March 27, 2007 10:26 AM To: Gardner, Brian <FHWA>; pa...@no... Subject: RE: [transims-developers] Subversion repository has been restructured I don't know how to change my user ID. I assume it is still aecom, but I haven't found any form / interface that tells me that. =20 The update error message is: Error REPORT request failed on '/svnroot/transims/!svn/vcc/default' Error Target path does not exist dbr David B. Roden, P.E. Senior Consulting Manager AECOM Consult, An affiliate of DMJM Harris 3101 Wilson Boulevard, 4th Floor Arlington, VA. 22201 E dav...@dm... T 703.682.5079 F 703.682.5001 =20 -----Original Message----- From: Bri...@do... [mailto:Bri...@do...]=20 Sent: Tuesday, March 27, 2007 10:12 AM To: Roden, David; pa...@no... Subject: RE: [transims-developers] Subversion repository has been restructured I just tried an update and it seems to be working. The aecom UID is still active on the project. -----Original Message----- From: Roden, David [mailto:dav...@dm...]=20 Sent: Tuesday, March 27, 2007 10:06 AM To: Le, Paul Cc: Gardner, Brian <FHWA> Subject: RE: [transims-developers] Subversion repository has been restructured My svn update failed to find the connection. Any suggestions about what I need to change to get reconnected? dbr David B. Roden, P.E. Senior Consulting Manager AECOM Consult, An affiliate of DMJM Harris 3101 Wilson Boulevard, 4th Floor Arlington, VA. 22201 E dav...@dm... T 703.682.5079 F 703.682.5001 =20 -----Original Message----- From: tra...@li... [mailto:tra...@li...] On Behalf Of Le, Paul Sent: Monday, March 26, 2007 1:10 PM To: tra...@li... Subject: [transims-developers] Subversion repository has been restructured To All Developer/Subversion users, =20 The Subversion repository has been restructured over the weekend. All your current development will continue under the new top level folder called "main-path". Please update your local working copies using the command svn.>update, before making any new changes, and before committing any new changes to the repository. =20 =20 It is normally good practice to run the command svn->update to get all the latest updates from the repository server before making any new changes or committing any new changes. =20 =20 =20 =20 =20 Regards, =20 Paul H. Le Noblis Wireless Communication and Mobile Computing 703-610-2397 |
|
From: Le, P. <pa...@no...> - 2007-03-26 17:09:57
|
To=20All=20Developer/Subversion=20users, =20 The=20Subversion=20repository=20has=20been=20restructured=20over=20the=20w= eekend.=20=20All your=20current=20development=20will=20continue=20under=20the=20new=20top=20= level=20folder called=20"main-path".=20=20Please=20update=20your=20local=20working=20copi= es=20using=20the command=20svn.>update,=20before=20making=20any=20new=20changes,=20and=20be= fore committing=20any=20new=20changes=20to=20the=20repository.=20=20 =20 It=20is=20normally=20good=20practice=20to=20run=20the=20command=20svn->upd= ate=20to=20get=20all the=20latest=20updates=20from=20the=20repository=20server=20before=20makin= g=20any=20new changes=20or=20committing=20any=20new=20changes. =20 =20 =20 =20 =20 Regards, =20 Paul=20H.=20Le Noblis Wireless=20Communication=20and=20Mobile=20Computing 703-610-2397 =20 ______________________________________________________________________ We=20recently=20changed=20our=20name=20from=20Mitretek=20Systems=20to=20No= blis=20-=20www.noblis.org. ______________________________________________________________________ |
|
From: Le, P. <pa...@no...> - 2007-03-19 14:23:33
|
Per=20the=20request=20from=20Brian,=20on=20Friday=203/23,=20I=20will=20res= tructure=20the Subversion=20repository=20to=20include=202=20main=20development=20areas:=20= =20main-path, and=20research-path.=20=20The=20main-path=20folder=20holds=20the=20main=20= development=20path that=20is=20closely=20managed=20by=20FHWA,=20and=20frequently=20used=20by=20= the=20community. The=20developers=20will=20continue=20to=20use=20the=20main-path=20folder=20= as=20before.=20=20The research-path=20folder=20holds=20the=20research=20oriented=20development=20= path=20that moves=20in=20tangent=20with=20the=20main=20development=20path=20to=20reach= =20a=20revolutionary target.=20=20The=20research-path=20folder=20will=20be=20used=20in=20the=20= near=20future.=20=20Both the=20main-path=20and=20the=20research-path=20folders=20have=20the=20same=20= file=20structure consisting=20of=203=20subfolders:=20trunk,=20branches,=20and=20tags. =20 Please=20make=20sure=20that=20all=20outstanding=20files=20are=20check-in/c= ommitted before=20the=20restructure=20task=20on=20Friday=203/23=20to=20avoid=20comp= lex=20merges. Thank=20you! =20 =20 =20 Regards, =20 Paul=20H.=20Le Noblis Wireless=20Communication=20and=20Mobile=20Computing 703-610-2397 =20 ______________________________________________________________________ We=20recently=20changed=20our=20name=20from=20Mitretek=20Systems=20to=20No= blis=20-=20www.noblis.org. ______________________________________________________________________ |
|
From: Brian G. <bri...@gm...> - 2007-03-17 16:40:12
|
I've set up a discussion list "transims-developers" to provide a mechanism to discuss development issues. Unlike "transims-commits" this list is/will be configured to allow all members to post. On 3/16/07, Le, Paul <pa...@no...> wrote: > > Per the request from Brian, on Friday 3/23, I will restructure the > Subversion repository to include 2 main development areas: main-path, and > research-path. The main-path folder holds the main development path that is > closely managed by FHWA, and frequently used by the community. The > developers will continue to use the main-path folder as before. The > research-path folder holds the research oriented development path that moves > in tangent with the main development path to reach a revolutionary target. > The research-path folder will be used in the near future. Both the > main-path and the research-path folders have the same file structure > consisting of 3 subfolders: trunk, branches, and tags. > > > > Please make sure that all outstanding files are check-in/committed before > the restructure task on Friday 3/23 to avoid complex merges. Thank you! > > > > Regards, > > > > Paul H. Le > > Noblis > > Wireless Communication and Mobile Computing > > 703-610-2397 > > > > ______________________________________________________________________ > We recently changed our name from Mitretek Systems to Noblis - > www.noblis.org. > ______________________________________________________________________ > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys-and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Transims-developers mailing list > Tra...@li... > https://lists.sourceforge.net/lists/listinfo/transims-developers > > |
|
From: Le, P. <pa...@no...> - 2007-03-16 14:41:03
|
Per=20the=20request=20from=20Brian,=20on=20Friday=203/23,=20I=20will=20res= tructure=20the Subversion=20repository=20to=20include=202=20main=20development=20areas:=20= =20main-path, and=20research-path.=20=20The=20main-path=20folder=20holds=20the=20main=20= development=20path that=20is=20closely=20managed=20by=20FHWA,=20and=20frequently=20used=20by=20= the=20community. The=20developers=20will=20continue=20to=20use=20the=20main-path=20folder=20= as=20before.=20=20The research-path=20folder=20holds=20the=20research=20oriented=20development=20= path=20that moves=20in=20tangent=20with=20the=20main=20development=20path=20to=20reach= =20a=20revolutionary target.=20=20The=20research-path=20folder=20will=20be=20used=20in=20the=20= near=20future.=20=20Both the=20main-path=20and=20the=20research-path=20folders=20have=20the=20same=20= file=20structure consisting=20of=203=20subfolders:=20trunk,=20branches,=20and=20tags. =20 Please=20make=20sure=20that=20all=20outstanding=20files=20are=20check-in/c= ommitted before=20the=20restructure=20task=20on=20Friday=203/23=20to=20avoid=20comp= lex=20merges. Thank=20you! =20 Regards, =20 Paul=20H.=20Le Noblis Wireless=20Communication=20and=20Mobile=20Computing 703-610-2397 =20 ______________________________________________________________________ We=20recently=20changed=20our=20name=20from=20Mitretek=20Systems=20to=20No= blis=20-=20www.noblis.org. ______________________________________________________________________ |
