enums - Quantifier elimination for enumeration types in Z3 -


i'm experimenting quantifier elimination tactic formulas of enumerated types. i'd know if there ways of increasing performance adjusting solver somehow. after brief glance on source code concluded there seem different strategies quantifier elimination (e.g. qe_lite.cpp), not exposed parameters of qe tactic. in case formulas have simple propositional structure, quantified variables don't occur in formula, procedure can called several thousands of times. guess, questions following:

  1. does z3 have sort of caching quantifier elimination (application mode?), allow process bunch of similar or identical formulas faster?
  2. can guide z3 use different approaches quantifier elimination on finite domain formulas, can see 1 works better me?
  3. it interesting know approach used in z3 eliminate quantifiers formulas on finite domain types. performed substitution + simplification, or more elaborate techniques used?

thank you.

  1. "qe-lite" separate tactic "qe".
  2. there no similarity detection of formulas. identical formulas hash-consed (represented uniquely) , quantifier elimination traverses once.
  3. you can try either "qe" or "qe-lite". "qe-lite" light-weight. eliminates equalities. meant crude (faster, incomplete) routine eliminating quantified variables when opportune.
  4. the facilities finite domains simple: z3 performs bit-vector , booleans all-sat find values can used. enumeration types given algebraic data-types, z3 case split (followed satisfiability check prune). values finite domain are

Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more