Recent activity
Subscribe to this feed
Frank replied on May 16, 2008 22:50 to the problem "Urban Terrain" in Analytical Graphics, Inc.:
Lets start by examining a fixed point:
To use buildings as analytical constraints, you need to represent them in STK as either terrain data (used in creating Azimuth Elevation mask constraints) or as 3-D models (used to create Body masks which are very similar to AzEl masks and can be used as line of sight constraints as well)
Lets look at the terrain solution first:
You need to get the building height information into a supported terrain format. DEM's are one way, there are others listed in the docs. Typically the source of this data is either LIDAR, or dimensional blueprints (vector data) converted to a raster Lat/Lon/Alt data set.
I should caution that typically these are very dense data files, which tends to make them rather large, and somewhat of a memory hog if not managed properly. Remember that this is height data for buildings instead of natural terrain, and flat surfaces like rooftops and building sides cause more unusual issues than you would expect.
Load in the terrain data into the scenario, assign a facility/target object to use terrain for it's altitude, and then save the scenario. Close the scenario.
Hand edit the *.f (or *.t) file in a text editor to change the NumAzRaysInMask value from 360 to something much larger. This number represents the number of terrain data samples performed in 360 degrees. Normally this number defaults to the equivalent of 1 degree separation between samples. To increase the detail of the AzEl mask, increase this number. To figure out the equivalent angular resolution, divide it by 360 and you're left with the number of degrees between each ray used to create the masking file.
Save the file. Re-load the scenario, and then tell the facility to use terrain to calculate the AzEl mask. This may take a while depending on the number of points it has to sample.
Save the scenario. This saves off the .aem file for the facility in question so it doesn't need to recalculate the data.
Turn on the use of AzEl masks as a constraint for the facility. You can then expect the ACCESS tool to do it's thing, which may take some time depending on how detailed an AzEl mask file was used.
As a side note: I recommend removing the terrain data from the scenario as it's likely a memory hog due to the number of points needed to represent the detail of buildings. If everything is static, you won't need it again unless you re-position the facility. Even if other things are moving around, like aircraft, satellites, etc... the analysis from the fixed point doesn't change the masking effects of the building. It's whole world of what's visible and what's not, due to buildings, is represented in the *.aem file.
next post: we'll look at using 3-D models of buildings as a source of analytic line of sight obstruction, and later, address the RF questions w/ TIREM
Frank replied on May 16, 2008 21:46 to the problem "Urban Terrain" in Analytical Graphics, Inc.:
Frank reported a problem in Analytical Graphics, Inc. on May 16, 2008 21:42:
Urban TerrainI need an education in how to use buildings as constraints. My assumption is that you can either create custom terrain files, or create/load 3D models and use them create masking files. I'm interested in line of sight constraints, but I'm doing RF stuff too, so I think I may eventually figure out that that's what I want. Is that TIREM?
nothingtosay replied on May 10, 2008 16:57 to the problem "The facebook app appears broken" in Twitter:
It hasn't worked for me since October last year, and none of the method people has suggested worked for me (ie. re-adding the app, re-enter the information, adjusting the settings, etc.).
What I find it very vexing is the fact that the application page on facebook has been long ignored by the developers at the same time last year when the application was first broken. It's one matter that they couldn't figure out what's wrong with it, it's another matter to ignore their user base completely. I would have appreciated (and more willing to give more time to the developers) if they would have at least informed us that they have been listening and still trying to work out the problem. However, that hasn't happen and I am fed-up on this kind of treatment thus far.
brewninja marked one of Frank's replies in Twitter as useful. Frank replied to the problem "The facebook app appears broken".
A comment on the problem "The facebook app appears broken" in Twitter:
You're right, I've done the same now. – rhino75, on May 07, 2008 15:21
jrichardn replied on May 07, 2008 15:21 to the problem "The facebook app appears broken" in Twitter:
For the last several days, clicking on the Twitter app in Facebook yields a page headed thus:
RFacebook environment information
This shows you at a glance the information that RFacebook has populated for you.
More information at rfacebook.rubyforge.org. Please report RFacebook bugs here.
Until yesterday, updates through the Web or IM were relayed to Facebook quickly. It now appears to be spotty at best.
WildCeltcRose replied on May 07, 2008 14:59 to the problem "The facebook app appears broken" in Twitter:
MrAndrew replied on May 07, 2008 14:58 to the problem "The facebook app appears broken" in Twitter:
Tribee replied on May 07, 2008 14:45 to the problem "The facebook app appears broken" in Twitter:
rhino75 replied on May 07, 2008 14:41 to the problem "The facebook app appears broken" in Twitter:
mjsmith1223 replied on May 07, 2008 12:40 to the problem "The facebook app appears broken" in Twitter:
antoineclarke replied on May 06, 2008 19:10 to the problem "The facebook app appears broken" in Twitter:
It wasn't worked for a couple of days and no news, which is annoying. It means I have no idea if anyone realizes there is a problem or not. Which is a poor start. In case it helps I've cut and pasted what comes up on the screen:
RFacebook environment information
This shows you at a glance the information that RFacebook has populated for you.
More information at rfacebook.rubyforge.org. Please report RFacebook bugs here.
FacebookController
fbsession OK session is ready to make API calls
fbparams OK
user 707581015
added 1
session_key ea0125e38d8f99751ebaa20c-707581015
in_canvas 1
profile_update_time 1209911954
expires 0
time 1210100564.4997
friends 919463,15619812,500260243,501630843,502365728,502630468,503617740,503764783,506334065,507855489,508007578,508778842,509968833,511623888,513079215,513160025,515566418,518865472,532116723,534042462,541209618,542258355,542444306,542604255,542648695,543071514,543285962,568260209,570102292,581765008,587158387,589513627,592187517,599810711,604363101,609736573,610009443,616436624,617022052,618591313,618975257,625233499,641550408,641599992,642862722,645525277,646000818,651782192,656830656,657116133,658411438,661602782,666753741,666993707,669782914,682785404,683770526,689916254,693315503,694572750,695718235,696290624,699333222,700568382,703545005,711111050,711536155,714094886,717791129,722478159,731415017,734365906,739930680,749815198,759705726,770019244,789060310,812199908,816634927,842810091,1049966484,1082118466,1105792863,1470240149
api_key 7cc3dc042ec019b913300d1e7559aad9
request_method GET
locale en_US
position_fix 1
in_facebook_canvas? OK yes
in_facebook_frame? OK no
facebook_api_key OK XXXXXXXXXXXXXXXXXXaad9
facebook_api_secret OK XXXXXXXXXXXXXXXXXXc6f4
undefined method `is_https?' for #
*
attribute_methods.rb:200 in method_missing_without_original
/vendor/rails/activerecord/lib/active_record/attribute_methods.rb:200:in `method_missing_without_original'
*
acts_as_modified.rb:212 in method_missing
/vendor/plugins/acts_as_modified/lib/acts_as_modified.rb:212:in `method_missing'
*
application_helper.rb:59 in profile_image_path_for_user
/app/helpers/application_helper.rb:59:in `profile_image_path_for_user'
*
user.rb:1203 in set_facebook_profile_box
/app/models/user.rb:1203:in `set_facebook_profile_box'
*
facebook_controller.rb:13 in index
/app/controllers/facebook_controller.rb:13:in `index'
*
base.rb:1158 in send
/vendor/rails/actionpack/lib/action_controller/base.rb:1158:in `send'
*
base.rb:1158 in perform_action_without_filters
/vendor/rails/actionpack/lib/action_controller/base.rb:1158:in `perform_action_without_filters'
*
filters.rb:697 in call_filters
/vendor/rails/actionpack/lib/action_controller/filters.rb:697:in `call_filters'
*
filters.rb:725 in run_before_filters
/vendor/rails/actionpack/lib/action_controller/filters.rb:725:in `run_before_filters'
*
benchmark.rb:293 in measure
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
*
filters.rb:483 in call
/vendor/rails/actionpack/lib/action_controller/filters.rb:483:in `call'
*
filters.rb:483 in call
/vendor/rails/actionpack/lib/action_controller/filters.rb:483:in `call'
*
filters.rb:722 in run_before_filters
/vendor/rails/actionpack/lib/action_controller/filters.rb:722:in `run_before_filters'
*
filters.rb:695 in call_filters
/vendor/rails/actionpack/lib/action_controller/filters.rb:695:in `call_filters'
*
filters.rb:689 in perform_action_without_benchmark
/vendor/rails/actionpack/lib/action_controller/filters.rb:689:in `perform_action_without_benchmark'
*
benchmarking.rb:68 in perform_action_without_rescue
/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
*
benchmark.rb:293 in measure
/usr/lib/ruby/1.8/benchmark.rb:293:in `measure'
*
benchmarking.rb:68 in perform_action_without_rescue
/vendor/rails/actionpack/lib/action_controller/benchmarking.rb:68:in `perform_action_without_rescue'
*
rescue.rb:199 in perform_action_without_caching
/vendor/rails/actionpack/lib/action_controller/rescue.rb:199:in `perform_action_without_caching'
*
caching.rb:678 in perform_action_without_apache_combined
/vendor/rails/actionpack/lib/action_controller/caching.rb:678:in `perform_action_without_apache_combined'
*
query_cache.rb:33 in cache
/vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/query_cache.rb:33:in `cache'
*
query_cache.rb:8 in cache
/vendor/rails/activerecord/lib/active_record/query_cache.rb:8:in `cache'
*
caching.rb:677 in perform_action_without_apache_combined
/vendor/rails/actionpack/lib/action_controller/caching.rb:677:in `perform_action_without_apache_combined'
*
response_management_additions.rb:86 in perform_action
/lib/response_management_additions.rb:86:in `perform_action'
*
base.rb:524 in send
/vendor/rails/actionpack/lib/action_controller/base.rb:524:in `send'
*
base.rb:524 in process_without_filters
/vendor/rails/actionpack/lib/action_controller/base.rb:524:in `process_without_filters'
*
filters.rb:685 in process_without_session_management_support
/vendor/rails/actionpack/lib/action_controller/filters.rb:685:in `process_without_session_management_support'
*
session_management.rb:123 in process
/vendor/rails/actionpack/lib/action_controller/session_management.rb:123:in `process'
*
base.rb:388 in process
/vendor/rails/actionpack/lib/action_controller/base.rb:388:in `process'
*
dispatcher.rb:171 in handle_request
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:171:in `handle_request'
*
dispatcher.rb:115 in dispatch
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:115:in `dispatch'
*
dispatcher.rb:126 in dispatch_cgi
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:126:in `dispatch_cgi'
*
dispatcher.rb:9 in dispatch
/vendor/rails/actionpack/lib/action_controller/dispatcher.rb:9:in `dispatch'
*
rails.rb:76 in process
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel/rails.rb:76:in `process'
*
rails.rb:74 in synchronize
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel/rails.rb:74:in `synchronize'
*
rails.rb:74 in process
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel/rails.rb:74:in `process'
*
mongrel.rb:159 in process_client
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:159:in `process_client'
*
mongrel.rb:158 in each
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:158:in `each'
*
mongrel.rb:158 in process_client
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:158:in `process_client'
*
mongrel.rb:285 in run
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:285:in `run'
*
mongrel.rb:285 in initialize
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:285:in `initialize'
*
mongrel.rb:285 in new
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:285:in `new'
*
mongrel.rb:285 in run
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:285:in `run'
*
mongrel.rb:268 in initialize
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:268:in `initialize'
*
mongrel.rb:268 in new
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:268:in `new'
*
mongrel.rb:268 in run
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel.rb:268:in `run'
*
configurator.rb:282 in run
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel/configurator.rb:282:in `run'
*
configurator.rb:281 in each
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel/configurator.rb:281:in `each'
*
configurator.rb:281 in run
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel/configurator.rb:281:in `run'
*
mongrel_rails:128 in run
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/mongrel_rails:128:in `run'
*
command.rb:212 in run
/usr/lib64/ruby/gems/1.8/gems/mongrel-1.1.3/bin/../lib/mongrel/command.rb:212:in `run'
*
mongrel_rails:19 in load
/usr/bin/mongrel_rails:19:in `load
roxierockstar replied on May 03, 2008 11:55 to the problem "The facebook app appears broken" in Twitter:
Frank replied on April 24, 2008 23:08 to the problem "The facebook app appears broken" in Twitter:
scooterissima replied on April 24, 2008 03:08 to the problem "The facebook app appears broken" in Twitter:
Pawel Szymczykowski replied on April 05, 2008 05:41 to the problem "The facebook app appears broken" in Twitter:
mjsmith1223 replied on April 03, 2008 18:32 to the problem "The facebook app appears broken" in Twitter:
ali replied on April 03, 2008 18:24 to the problem "The facebook app appears broken" in Twitter:
| next » « previous |
Loading Profile...








