All Files (100.0% covered at 1.66 hits/line)
57 files in total.
492 relevant lines.
492 lines covered and
0 lines missed
- 1
class ApplicationController < ActionController::Base
# Prevent CSRF attacks by raising an exception.
# For APIs, you may want to use :null_session instead.
- 1
protect_from_forgery with: :null_session
# Devise auth prereqs
- 1
before_filter :configure_permitted_parameters, if: :devise_controller?
- 1
def configure_permitted_parameters
- 4
devise_parameter_sanitizer.for(:sign_up) { |u| u.permit(:username, :email, :password, :password_confirmation) }
end
- 1
def after_sign_in_path_for(resource)
- 1
user_path(resource)
end
- 1
def verify_current_user user
- 29
if current_user && !current_user.eql?(user)
- 1
flash[:alert] = 'You are not authorized to perform this action'
- 1
redirect_to root_path
end
end
end
- 1
class CategoriesController < ApplicationController
- 1
def index
- 1
@categories = Category.all
end
- 1
def show
- 1
@category = Category.find(params[:id])
end
end
- 1
class ChallengesController < ApplicationController
- 1
before_action :authenticate_user!
- 1
before_action :find_user, except: [:index]
- 1
before_action :verify_user, except: [:index, :show]
- 1
before_action :find_challenge, except: [:index, :new, :create]
- 1
def index
- 8
@users = User.all
- 8
if params[:user_id]
- 8
find_user
end
end
- 1
def new
- 2
@challenge = Challenge.new
- 2
respond_to do |format|
- 2
format.html
- 2
format.js
end
end
- 1
def create
- 2
@challenge = @user.challenges.new(challenge_params)
- 2
if @challenge.save
- 1
respond_to do |format|
- 1
format.html { redirect_to user_challenges_path(@user) }
- 1
format.js
end
else
- 1
render :new
end
end
- 1
def edit
end
- 1
def update
- 2
if @challenge.update(challenge_params)
- 1
respond_to do |format|
- 1
format.html { redirect_to user_challenges_path(@user) }
- 1
format.js
end
else
- 1
render :edit
end
end
- 1
def destroy
- 1
@challenge.destroy
- 1
redirect_to user_challenges_path(@user)
end
- 1
private
- 1
def find_user
- 29
@user = User.find(params[:user_id])
end
- 1
def verify_user
- 10
verify_current_user(@user)
end
- 1
def find_challenge
- 16
@challenge = Challenge.find(params[:id])
end
- 1
def challenge_params
- 4
params.require(:challenge).permit(:name, :description, :category_ids => [])
end
end
- 1
class HomeController < ApplicationController
end
- 1
class SubscriptionsController < ApplicationController
- 1
before_action :find_subscriber
- 1
before_action :verify_subscriber
- 1
before_action :find_subscription, except: [:index, :new, :create]
- 1
def create
- 1
@subscription = @subscriber.subscriptions.new(subscription_params)
- 1
@subscription.save
- 1
@user = User.find(subscription_params[:author_id])
- 1
respond_to :js
end
- 1
def destroy
- 1
@user =<EMAIL_ADDRESS>- 1
@subscription.destroy
- 1
respond_to :js
end
- 1
private
- 1
def find_subscriber
- 2
@subscriber = User.find(params[:user_id])
end
- 1
def verify_subscriber
- 2
verify_current_user(@subscriber)
end
- 1
def find_subscription
- 1
@subscription = Subscription.find(params[:id])
end
- 1
def subscription_params
- 2
params.require(:subscription).permit(:author_id)
end
end
- 1
class UpdatesController < ApplicationController
- 1
before_action :find_challenge_and_user, except: [:show]
- 1
before_action :find_update, except: [:index, :new, :create]
- 1
def new
- 3
@update = Update.new
- 3
respond_to do |format|
- 3
format.html
- 3
format.js
end
end
- 1
def create
- 2
@update = @challenge.updates.new(update_params)
- 2
if @update.save
- 1
respond_to do |format|
- 1
format.html { redirect_to user_challenge_path(@user, @challenge) }
- 1
format.js
end
else
- 1
render :new
end
end
- 1
def show
- 3
respond_to do |format|
- 3
format.html
- 3
format.js
end
end
- 1
private
- 1
def find_challenge_and_user
- 5
@challenge = Challenge.find(params[:challenge_id])
- 5
@user = @challenge.user
- 5
verify_current_user(@user)
end
- 1
def find_update
- 3
@update = Update.find(params[:id])
end
- 1
def update_params
- 2
params.require(:update).permit(:title, :body, :picture)
end
end
- 1
class UsersController < ApplicationController
- 1
before_action :authenticate_user!
- 1
before_action :find_user, except: [:new, :create, :index]
- 1
def index
- 1
@users = User.all
end
- 1
def edit
- 3
respond_to do |format|
- 3
format.html
- 3
format.js
end
end
- 1
def update
- 3
if @user.update(user_params)
- 2
redirect_to user_path(@user)
else
- 1
render :edit
end
end
- 1
private
- 1
def find_user
- 12
@user = User.find(params[:id])
- 12
verify_current_user(@user)
end
- 1
def user_params
- 3
params.require(:user).permit(:username, :avatar)
end
end
- 1
module ApplicationHelper
end
- 1
module CategoriesHelper
end
- 1
module SubscriptionsHelper
end
- 1
module UpdatesHelper
end
- 1
class Category < ActiveRecord::Base
- 1
has_and_belongs_to_many :challenges
- 1
validates :name, presence: true
- 1
validates_uniqueness_of :name
end
- 1
class Challenge < ActiveRecord::Base
- 1
belongs_to :user
- 1
has_many :updates, dependent: :destroy
- 1
has_and_belongs_to_many :categories
- 1
validates :name, presence: true
end
- 1
class Subscription < ActiveRecord::Base
- 1
belongs_to :user
- 1
validates :author_id, presence: true
- 1
validates_uniqueness_of :author_id
end
- 1
class Update < ActiveRecord::Base
- 1
belongs_to :challenge
- 1
validates :title, presence: true
- 1
validates :body, presence: true
- 1
mount_uploader :picture, AvatarUploader
end
- 1
class User < ActiveRecord::Base
# Include default devise modules. Others available are:
# :confirmable, :lockable, :timeoutable and :omniauthable
- 1
devise :database_authenticatable, :registerable,
:recoverable, :rememberable, :trackable, :validatable
- 1
mount_uploader :avatar, AvatarUploader
- 1
validates :username, presence: true
- 1
has_many :challenges, dependent: :destroy
- 1
has_many :subscriptions, dependent: :destroy
end
# encoding: utf-8
- 1
class AvatarUploader < CarrierWave::Uploader::Base
# Include RMagick or MiniMagick support:
# include CarrierWave::RMagick
# include CarrierWave::MiniMagick
# Choose what kind of storage to use for this uploader:
- 1
storage :fog
# storage :file
# Override the directory where uploaded files will be stored.
# This is a sensible default for uploaders that are meant to be mounted:
- 1
def store_dir
- 3
"uploads/#{model.class.to_s.underscore}/#{mounted_as}/#{model.id}"
end
# Provide a default URL as a default if there hasn't been a file uploaded:
# def default_url
# # For Rails 3.1+ asset pipeline compatibility:
# # ActionController::Base.helpers.asset_path("fallback/" + [version_name, "default.png"].compact.join('_'))
#
# "/images/fallback/" + [version_name, "default.png"].compact.join('_')
# end
# Process files as they are uploaded:
# process :scale => [200, 300]
#
# def scale(width, height)
# # do something
# end
# Create different versions of your uploaded files:
# version :thumb do
# process :resize_to_fit => [50, 50]
# end
# Add a white list of extensions which are allowed to be uploaded.
# For images you might use something like this:
# def extension_white_list
# %w(jpg jpeg gif png)
# end
# Override the filename of the uploaded files:
# Avoid using model.id or version_name here, see uploader/store.rb for details.
# def filename
# "something.jpg" if original_filename
# end
end
- 1
require File.expand_path('../boot', __FILE__)
- 1
require "rails"
# Pick the frameworks you want:
- 1
require "active_model/railtie"
- 1
require "active_job/railtie"
- 1
require "active_record/railtie"
- 1
require "action_controller/railtie"
- 1
require "action_mailer/railtie"
- 1
require "action_view/railtie"
- 1
require "sprockets/railtie"
# require "rails/test_unit/railtie"
# Require the gems listed in Gemfile, including any gems
# you've limited to :test, :development, or :production.
- 1
Bundler.require(*Rails.groups)
- 1
module Lunarleap
- 1
class Application < Rails::Application
# Settings in config/environments/* take precedence over those specified here.
# Application configuration should go into files in config/initializers
# -- all .rb files in that directory are automatically loaded.
# Set Time.zone default to the specified zone and make Active Record auto-convert to this zone.
# Run "rake -D time" for a list of tasks for finding time zone names. Default is UTC.
# config.time_zone = 'Central Time (US & Canada)'
# The default locale is :en and all translations from config/locales/*.rb,yml are auto loaded.
# config.i18n.load_path += Dir[Rails.root.join('my', 'locales', '*.{rb,yml}').to_s]
# config.i18n.default_locale = :de
# Do not swallow errors in after_commit/after_rollback callbacks.
- 1
config.active_record.raise_in_transactional_callbacks = true
- 1
config.action_view.embed_authenticity_token_in_remote_forms = true
end
end
- 1
ENV['BUNDLE_GEMFILE'] ||= File.expand_path('../../Gemfile', __FILE__)
- 1
require 'bundler/setup' # Set up gems listed in the Gemfile.
# Load the Rails application.
- 1
require File.expand_path('../application', __FILE__)
# Initialize the Rails application.
- 1
Rails.application.initialize!
- 1
Rails.application.configure do
# Settings specified here will take precedence over those in config/application.rb.
# The test environment is used exclusively to run your application's
# test suite. You never need to work with it otherwise. Remember that
# your test database is "scratch space" for the test suite and is wiped
# and recreated between test runs. Don't rely on the data there!
- 1
config.cache_classes = true
# Do not eager load code on boot. This avoids loading your whole application
# just for the purpose of running a single test. If you are using a tool that
# preloads Rails for running tests, you may have to set it to true.
- 1
config.eager_load = false
# Configure static file server for tests with Cache-Control for performance.
- 1
config.serve_static_files = true
- 1
config.static_cache_control = 'public, max-age=3600'
# Show full error reports and disable caching.
- 1
config.consider_all_requests_local = true
- 1
config.action_controller.perform_caching = false
# Raise exceptions instead of rendering exception templates.
- 1
config.action_dispatch.show_exceptions = false
# Disable request forgery protection in test environment.
- 1
config.action_controller.allow_forgery_protection = false
# Tell Action Mailer not to deliver emails to the real world.
# The :test delivery method accumulates sent emails in the
# ActionMailer::Base.deliveries array.
- 1
config.action_mailer.delivery_method = :test
# Randomize the order test cases are executed.
- 1
config.active_support.test_order = :random
# Print deprecation notices to the stderr.
- 1
config.active_support.deprecation = :stderr
# Raises error for missing translations
# config.action_view.raise_on_missing_translations = true
end
# Be sure to restart your server when you modify this file.
# Version of your assets, change this if you want to expire all your assets.
- 1
Rails.application.config.assets.version = '1.0'
# Add additional assets to the asset load path
# Rails.application.config.assets.paths << Emoji.images_path
# Precompile additional assets.
# application.js, application.css, and all non-JS/CSS in app/assets folder are already added.
# Rails.application.config.assets.precompile += %w( search.js )
# Be sure to restart your server when you modify this file.
# You can add backtrace silencers for libraries that you're using but don't wish to see in your backtraces.
# Rails.backtrace_cleaner.add_silencer { |line| line =~ /my_noisy_library/ }
# You can also remove all the silencers if you're trying to debug a problem that might stem from framework code.
# Rails.backtrace_cleaner.remove_silencers!
- 1
CarrierWave.configure do |config|
- 1
config.fog_credentials = {
provider: 'AWS',
aws_access_key_id: ENV['AWS_ACCESS_KEY_ID'],
aws_secret_access_key: ENV['AWS_SECRET_ACCESS_KEY'],
region: ENV['S3_REGION']
}
- 1
config.fog_directory = 'lunarleap'
- 1
config.fog_public = false
- 1
config.fog_attributes = { 'Cache-Control' => "max-age=#{365.day.to_i}" }
end
# Be sure to restart your server when you modify this file.
- 1
Rails.application.config.action_dispatch.cookies_serializer = :json
# Use this hook to configure devise mailer, warden hooks and so forth.
# Many of these configuration options can be set straight in your model.
- 1
Devise.setup do |config|
# The secret key used by Devise. Devise uses this key to generate
# random tokens. Changing this key will render invalid all existing
# confirmation, reset password and unlock tokens in the database.
# Devise will use the `secret_key_base` on Rails 4+ applications as its `secret_key`
# by default. You can change it below and use your own secret key.
# config.secret_key = '1b7d725ec579947740577dd66d9f4115926e2562a6694297b2556511feabffb9d28279db0a758dba6447430eaaddd6c1c9659e31e90f01753a2f8f913ae5f250'
# ==> Mailer Configuration
# Configure the e-mail address which will be shown in Devise::Mailer,
# note that it will be overwritten if you use your own mailer class
# with default "from" parameter.
- 1
config.mailer_sender =<EMAIL_ADDRESS># Configure the class responsible to send e-mails.
# config.mailer = 'Devise::Mailer'
# ==> ORM configuration
# Load and configure the ORM. Supports :active_record (default) and
# :mongoid (bson_ext recommended) by default. Other ORMs may be
# available as additional gems.
- 1
require 'devise/orm/active_record'
# ==> Configuration for any authentication mechanism
# Configure which keys are used when authenticating a user. The default is
# just :email. You can configure it to use [:username, :subdomain], so for
# authenticating a user, both parameters are required. Remember that those
# parameters are used only when authenticating and not when retrieving from
# session. If you need permissions, you should implement that in a before filter.
# You can also supply a hash where the value is a boolean determining whether
# or not authentication should be aborted when the value is not present.
# config.authentication_keys = [:email]
# Configure parameters from the request object used for authentication. Each entry
# given should be a request method and it will automatically be passed to the
# find_for_authentication method and considered in your model lookup. For instance,
# if you set :request_keys to [:subdomain], :subdomain will be used on authentication.
# The same considerations mentioned for authentication_keys also apply to request_keys.
# config.request_keys = []
# Configure which authentication keys should be case-insensitive.
# These keys will be downcased upon creating or modifying a user and when used
# to authenticate or find a user. Default is :email.
- 1
config.case_insensitive_keys = [:email]
# Configure which authentication keys should have whitespace stripped.
# These keys will have whitespace before and after removed upon creating or
# modifying a user and when used to authenticate or find a user. Default is :email.
- 1
config.strip_whitespace_keys = [:email]
# Tell if authentication through request.params is enabled. True by default.
# It can be set to an array that will enable params authentication only for the
# given strategies, for example, `config.params_authenticatable = [:database]` will
# enable it only for database (email + password) authentication.
# config.params_authenticatable = true
# Tell if authentication through HTTP Auth is enabled. False by default.
# It can be set to an array that will enable http authentication only for the
# given strategies, for example, `config.http_authenticatable = [:database]` will
# enable it only for database authentication. The supported strategies are:
# :database = Support basic authentication with authentication key + password
# config.http_authenticatable = false
# If 401 status code should be returned for AJAX requests. True by default.
# config.http_authenticatable_on_xhr = true
# The realm used in Http Basic Authentication. 'Application' by default.
# config.http_authentication_realm = 'Application'
# It will change confirmation, password recovery and other workflows
# to behave the same regardless if the e-mail provided was right or wrong.
# Does not affect registerable.
# config.paranoid = true
# By default Devise will store the user in session. You can skip storage for
# particular strategies by setting this option.
# Notice that if you are skipping storage for all authentication paths, you
# may want to disable generating routes to Devise's sessions controller by
# passing skip: :sessions to `devise_for` in your config/routes.rb
- 1
config.skip_session_storage = [:http_auth]
# By default, Devise cleans up the CSRF token on authentication to
# avoid CSRF token fixation attacks. This means that, when using AJAX
# requests for sign in and sign up, you need to get a new CSRF token
# from the server. You can disable this option at your own risk.
# config.clean_up_csrf_token_on_authentication = true
# ==> Configuration for :database_authenticatable
# For bcrypt, this is the cost for hashing the password and defaults to 10. If
# using other encryptors, it sets how many times you want the password re-encrypted.
#
# Limiting the stretches to just one in testing will increase the performance of
# your test suite dramatically. However, it is STRONGLY RECOMMENDED to not use
# a value less than 10 in other environments. Note that, for bcrypt (the default
# encryptor), the cost increases exponentially with the number of stretches (e.g.
# a value of 20 is already extremely slow: approx. 60 seconds for 1 calculation).
- 1
config.stretches = Rails.env.test? ? 1 : 10
# Setup a pepper to generate the encrypted password.
# config.pepper = '6e45b1067197c738596e73b2a02f857b01f660ea040e5e9c94e6aa1e0e2a48487332294315be19af6fe23968187c3580cc4deba252489c4e400d5e07fd303d58'
# ==> Configuration for :confirmable
# A period that the user is allowed to access the website even without
# confirming their account. For instance, if set to 2.days, the user will be
# able to access the website for two days without confirming their account,
# access will be blocked just in the third day. Default is 0.days, meaning
# the user cannot access the website without confirming their account.
# config.allow_unconfirmed_access_for = 2.days
# A period that the user is allowed to confirm their account before their
# token becomes invalid. For example, if set to 3.days, the user can confirm
# their account within 3 days after the mail was sent, but on the fourth day
# their account can't be confirmed with the token any more.
# Default is nil, meaning there is no restriction on how long a user can take
# before confirming their account.
# config.confirm_within = 3.days
# If true, requires any email changes to be confirmed (exactly the same way as
# initial account confirmation) to be applied. Requires additional unconfirmed_email
# db field (see migrations). Until confirmed, new email is stored in
# unconfirmed_email column, and copied to email column on successful confirmation.
- 1
config.reconfirmable = true
# Defines which key will be used when confirming an account
# config.confirmation_keys = [:email]
# ==> Configuration for :rememberable
# The time the user will be remembered without asking for credentials again.
# config.remember_for = 2.weeks
# Invalidates all the remember me tokens when the user signs out.
- 1
config.expire_all_remember_me_on_sign_out = true
# If true, extends the user's remember period when remembered via cookie.
# config.extend_remember_period = false
# Options to be passed to the created cookie. For instance, you can set
# secure: true in order to force SSL only cookies.
# config.rememberable_options = {}
# ==> Configuration for :validatable
# Range for password length.
- 1
config.password_length = 8..72
# Email regex used to validate email formats. It simply asserts that
# one (and only one) @ exists in the given string. This is mainly
# to give user feedback and not to assert the e-mail validity.
# config.email_regexp = /\A[^@]+@[^@]+\z/
# ==> Configuration for :timeoutable
# The time you want to timeout the user session without activity. After this
# time the user will be asked for credentials again. Default is 30 minutes.
# config.timeout_in = 30.minutes
# If true, expires auth token on session timeout.
# config.expire_auth_token_on_timeout = false
# ==> Configuration for :lockable
# Defines which strategy will be used to lock an account.
# :failed_attempts = Locks an account after a number of failed attempts to sign in.
# :none = No lock strategy. You should handle locking by yourself.
# config.lock_strategy = :failed_attempts
# Defines which key will be used when locking and unlocking an account
# config.unlock_keys = [:email]
# Defines which strategy will be used to unlock an account.
# :email = Sends an unlock link to the user email
# :time = Re-enables login after a certain amount of time (see :unlock_in below)
# :both = Enables both strategies
# :none = No unlock strategy. You should handle unlocking by yourself.
# config.unlock_strategy = :both
# Number of authentication tries before locking an account if lock_strategy
# is failed attempts.
# config.maximum_attempts = 20
# Time interval to unlock the account if :time is enabled as unlock_strategy.
# config.unlock_in = 1.hour
# Warn on the last attempt before the account is locked.
# config.last_attempt_warning = true
# ==> Configuration for :recoverable
#
# Defines which key will be used when recovering the password for an account
# config.reset_password_keys = [:email]
# Time interval you can reset your password with a reset password key.
# Don't put a too small interval or your users won't have the time to
# change their passwords.
- 1
config.reset_password_within = 6.hours
# When set to false, does not sign a user in automatically after their password is
# reset. Defaults to true, so a user is signed in automatically after a reset.
# config.sign_in_after_reset_password = true
# ==> Configuration for :encryptable
# Allow you to use another encryption algorithm besides bcrypt (default). You can use
# :sha1, :sha512 or encryptors from others authentication tools as :clearance_sha1,
# :authlogic_sha512 (then you should set stretches above to 20 for default behavior)
# and :restful_authentication_sha1 (then you should set stretches to 10, and copy
# REST_AUTH_SITE_KEY to pepper).
#
# Require the `devise-encryptable` gem when using anything other than bcrypt
# config.encryptor = :sha512
# ==> Scopes configuration
# Turn scoped views on. Before rendering "sessions/new", it will first check for
# "users/sessions/new". It's turned off by default because it's slower if you
# are using only default views.
# config.scoped_views = false
# Configure the default scope given to Warden. By default it's the first
# devise role declared in your routes (usually :user).
# config.default_scope = :user
# Set this configuration to false if you want /users/sign_out to sign out
# only the current scope. By default, Devise signs out all scopes.
# config.sign_out_all_scopes = true
# ==> Navigation configuration
# Lists the formats that should be treated as navigational. Formats like
# :html, should redirect to the sign in page when the user does not have
# access, but formats like :xml or :json, should return 401.
#
# If you have any extra navigational formats, like :iphone or :mobile, you
# should add them to the navigational formats lists.
#
# The "*/*" below is required to match Internet Explorer requests.
# config.navigational_formats = ['*/*', :html]
# The default HTTP method used to sign out a resource. Default is :delete.
- 1
config.sign_out_via = :delete
# ==> OmniAuth
# Add a new OmniAuth provider. Check the wiki for more information on setting
# up on your models and hooks.
# config.omniauth :github, 'APP_ID', 'APP_SECRET', scope: 'user,public_repo'
# ==> Warden configuration
# If you want to use other strategies, that are not supported by Devise, or
# change the failure app, you can configure them inside the config.warden block.
#
# config.warden do |manager|
# manager.intercept_401 = false
# manager.default_strategies(scope: :user).unshift :some_external_strategy
# end
# ==> Mountable engine configurations
# When using Devise inside an engine, let's call it `MyEngine`, and this engine
# is mountable, there are some extra configurations to be taken into account.
# The following options are available, assuming the engine is mounted as:
#
# mount MyEngine, at: '/my_engine'
#
# The router that invoked `devise_for`, in the example above, would be:
# config.router_name = :my_engine
#
# When using OmniAuth, Devise cannot automatically set OmniAuth path,
# so you need to do it manually. For the users scope, it would be:
# config.omniauth_path_prefix = '/my_engine/users/auth'
end
# Be sure to restart your server when you modify this file.
# Configure sensitive parameters which will be filtered from the log file.
- 1
Rails.application.config.filter_parameters += [:password]
# Be sure to restart your server when you modify this file.
# Add new inflection rules using the following format. Inflections
# are locale specific, and you may define rules for as many different
# locales as you wish. All of these examples are active by default:
# ActiveSupport::Inflector.inflections(:en) do |inflect|
# inflect.plural /^(ox)$/i, '\1en'
# inflect.singular /^(ox)en/i, '\1'
# inflect.irregular 'person', 'people'
# inflect.uncountable %w( fish sheep )
# end
# These inflection rules are supported but not enabled by default:
# ActiveSupport::Inflector.inflections(:en) do |inflect|
# inflect.acronym 'RESTful'
# end
# Be sure to restart your server when you modify this file.
# Add new mime types for use in respond_to blocks:
# Mime::Type.register "text/richtext", :rtf
# Be sure to restart your server when you modify this file.
- 1
Rails.application.config.session_store :cookie_store, key: '_lunarleap_session'
# Be sure to restart your server when you modify this file.
# This file contains settings for ActionController::ParamsWrapper which
# is enabled by default.
# Enable parameter wrapping for JSON. You can disable this by setting :format to an empty array.
- 1
ActiveSupport.on_load(:action_controller) do
- 1
wrap_parameters format: [:json] if respond_to?(:wrap_parameters)
end
# To enable root element in JSON for ActiveRecord objects.
# ActiveSupport.on_load(:active_record) do
# self.include_root_in_json = true
# end
- 1
Rails.application.routes.draw do
- 1
root 'home#index'
- 1
devise_for :users
- 1
resources :users do
- 1
resources :challenges
end
- 1
resources :challenges do
- 1
resources :updates
end
- 1
resources :users do
- 1
resources :subscriptions
end
- 1
resources :categories
end
- 1
require 'rails_helper'
- 1
RSpec.describe CategoriesController, type: :controller do
end
- 1
require 'rails_helper'
- 1
RSpec.describe ChallengesController, type: :controller do
end
- 1
require 'rails_helper'
- 1
RSpec.describe HomeController, type: :controller do
end
- 1
require 'rails_helper'
- 1
RSpec.describe SubscriptionsController, type: :controller do
end
- 1
require 'rails_helper'
- 1
RSpec.describe UpdatesController, type: :controller do
end
- 1
FactoryGirl.define do
- 1
factory :user do
- 1
username 'Telperion'
- 1
email<EMAIL_ADDRESS>- 1
password 'password'
end
- 1
factory :challenge do
- 1
name 'Push-up Challenge'
- 1
description 'Do 42 Push-ups every day'
end
- 1
factory :update do
- 1
title 'I did 43 actually!'
- 1
body 'I was feeling super motivated.'
end
- 1
factory :category do
- 1
name 'Fitness'
end
end
- 1
require 'rails_helper'
- 1
describe 'the visit categories process' do
- 1
before do
- 1
@category = FactoryGirl.create(:category)
- 1
@user = FactoryGirl.create(:user)
- 1
login_as(@user)
end
- 1
it 'can visit categories', js: true do
- 1
visit categories_path
- 1
click_on @category.name, match: :first
- 1
expect(page).to have_content @category.name
- 1
expect(page).to have_content 'no challenges'
end
end
- 1
require 'rails_helper'
- 1
describe 'the add a challenge process' do
- 1
before do
- 3
@user = FactoryGirl.create(:user)
- 3
@category = FactoryGirl.create(:category)
end
- 1
it 'cannot add a challenge if not logged in' do
- 1
visit root_path
- 1
click_link 'Challenges'
- 1
expect(page).to_not have_content 'New Challenge'
end
- 1
it 'can add a challenge', js: true do
- 1
login_as(@user)
- 1
visit user_challenges_path(@user)
- 1
expect(page).to have_content<EMAIL_ADDRESS>doesn\'t have any challenges, yet!"
- 1
click_on 'new-challenge-link'
- 1
fill_in 'Name', :with => 'Push-up Challenge'
- 1
fill_in 'Description', :with => 'Do 42 push-ups every day'
- 1
find("#challenge_category_ids_#{@category.id}").set(true)
- 1
find('input[type="submit"]').click
- 1
expect(page).to have_content 'Push-up Challenge'
- 1
expect(page).to have_content @category.name
end
- 1
it 'throws error if name is left blank', js: true do
- 1
login_as(@user)
- 1
visit user_challenges_path(@user)
- 1
click_on 'new-challenge-link'
- 1
find('input[type="submit"]').click
- 1
expect(page).to have_content 'errors'
end
end
- 1
require 'rails_helper'
- 1
describe 'the destroy a challenge process' do
- 1
before do
- 2
@challenge = FactoryGirl.create(:challenge)
- 2
@user = FactoryGirl.create(:user, challenges: [@challenge])
- 2
login_as(@user)
end
- 1
it 'can destroy a challenge', js: true do
- 1
visit user_challenge_path(@user, @challenge)
- 1
expect(page).to have_content @challenge.name
- 1
click_on 'delete-challenge-link'
- 1
expect(page).to_not have_content @challenge.name
end
- 1
it 'cannot attempt to destroy a challenge if not same user' do
- 1
login_as(FactoryGirl.create(:user, :username => 'Evildoer', :email => 'evil@doer.com'))
- 1
visit user_challenge_path(@user, @challenge)
- 1
expect(page).to_not have_css '#delete-challenge-link'
end
end
- 1
require 'rails_helper'
- 1
describe 'the edit a challenge process' do
- 1
before do
- 3
@challenge = FactoryGirl.create(:challenge)
- 3
@user = FactoryGirl.create(:user, challenges: [@challenge])
- 3
login_as(@user)
end
- 1
it 'cannot attempt to edit a challenge if not same user' do
- 1
login_as(FactoryGirl.create(:user, :username => 'Evildoer', :email => 'evil@doer.com'))
- 1
visit user_challenge_path(@user, @challenge)
- 1
expect(page).to_not have_css '#edit-challenge-link'
- 1
visit edit_user_challenge_path(@user, @challenge)
- 1
expect(page).to have_content 'not authorized'
end
- 1
it 'can edit a challenge', js: true do
- 1
visit user_challenge_path(@user, @challenge)
- 1
click_on 'edit-challenge-link'
- 1
fill_in 'Name', :with => '42 Jumping Jacks a Day!'
- 1
find('input[type="submit"]').click
- 1
expect(page).to have_content '42 Jumping Jacks a Day!'
end
- 1
it 'throws error if name is left blank', js: true do
- 1
visit user_challenge_path(@user, @challenge)
- 1
click_on 'edit-challenge-link'
- 1
fill_in 'Name', :with => ''
- 1
find('input[type="submit"]').click
- 1
expect(page).to have_content 'errors'
end
end
- 1
require 'rails_helper'
- 1
describe 'the view other users\' challenges process' do
- 1
before do
- 2
@update = FactoryGirl.create(:update)
- 2
@challenge = FactoryGirl.create(:challenge, updates: [@update])
- 2
@user = FactoryGirl.create(:user, challenges: [@challenge])
- 2
@viewer = FactoryGirl.create(:user, :username => 'Bosphorus', :email =><EMAIL_ADDRESS>- 2
login_as(@viewer)
end
- 1
it 'can view all users' do
- 1
visit users_path
- 1
click_on @user.username
- 1
expect(page).to have_content @challenge.name
end
- 1
it 'can view a user\'s challenge', js: true do
- 1
visit user_challenges_path(@user)
- 1
click_on @challenge.name
- 1
expect(page).to have_content @challenge.description
- 1
click_on @update.title
- 1
expect(page).to have_content @update.body
end
end
- 1
require 'rails_helper'
- 1
describe 'the follow a user process' do
- 1
before do
- 3
@challenge = FactoryGirl.create(:challenge)
- 3
@user = FactoryGirl.create(:user, challenges: [@challenge])
- 3
@follower = FactoryGirl.create(:user, :username => 'Bosphorus', :email =><EMAIL_ADDRESS>- 3
login_as(@follower)
end
- 1
it 'allows a user to follow another user', js: true do
- 1
visit user_challenges_path(@user)
- 1
find('#follow-button').click
- 1
expect(page).to have_content "Unfollow"
end
- 1
it 'allows a user to unfollow another user', js: true do
- 1
@subscription = @follower.subscriptions.new(:author_id => @user.id)
- 1
@subscription.save
- 1
visit user_challenges_path(@user)
- 1
click_link 'Unfollow'
- 1
expect(page).to have_content "Unfollow"
end
- 1
it 'cannot follow themselves' do
- 1
visit user_challenges_path(@follower)
- 1
expect(page).to_not have_content 'Follow'
end
end
- 1
require 'rails_helper'
- 1
describe 'the add an update to a challenge process' do
- 1
before do
- 3
@challenge = FactoryGirl.create(:challenge)
- 3
@user = FactoryGirl.create(:user, challenges: [@challenge])
- 3
login_as(@user)
end
- 1
it 'defaults title text to day of week and date', js: true do
- 1
visit user_challenge_path(@user, @challenge)
- 1
click_on 'new-update-link'
- 1
expect(page).to have_content DateTime.now.strftime("%A, %m/%d/%Y")
end
- 1
it 'can add an update to a challenge', js: true do
- 1
visit user_challenge_path(@user, @challenge)
- 1
click_on 'new-update-link'
- 1
fill_in 'Title', :with => 'I did 43 actually!'
- 1
fill_in 'Body', :with => 'I was feelin\' good.'
- 1
page.attach_file("Picture", 'spec/fixtures/images/avatar.jpeg')
- 1
find('#save-update-button').click
- 1
expect(page).to have_content 'I did 43 actually!'
end
- 1
it 'throws error if body is left blank', js: true do
- 1
visit user_challenge_path(@user, @challenge)
- 1
click_on 'new-update-link'
- 1
fill_in 'Body', :with => ''
- 1
find('#save-update-button').click
- 1
expect(page).to have_content 'errors'
end
end
- 1
require 'rails_helper'
- 1
describe 'the show an update process' do
- 1
before do
- 2
@update = FactoryGirl.create(:update)
- 2
@challenge = FactoryGirl.create(:challenge, updates: [@update])
- 2
@user = FactoryGirl.create(:user, challenges: [@challenge])
- 2
login_as(@user)
end
- 1
it 'can show an update', js: true do
- 1
visit user_challenge_path(@user, @challenge)
- 1
click_on @update.title
- 1
expect(page).to have_content @update.body
end
- 1
it 'can hide an update', js: true do
- 1
visit user_challenge_path(@user, @challenge)
- 1
click_on @update.title
- 1
find("#update-body-#{@update.id}").click
- 1
expect(page).to_not have_content @update.body
end
end
- 1
require 'rails_helper'
- 1
describe 'the user signup process' do
- 1
before do
- 2
@user = FactoryGirl.create(:user)
end
- 1
it 'can signup a user' do
- 1
visit new_user_registration_path
- 1
fill_in 'Username', :with => 'Steve'
- 1
fill_in 'Email', :with =><EMAIL_ADDRESS>- 1
fill_in 'Password', :with => 'password'
- 1
fill_in 'Password confirmation', :with => 'password'
- 1
find('input[type="submit"]').click
- 1
expect(page).to have_content 'Welcome! You have signed up successfully.'
end
- 1
it 'can view a user' do
- 1
login_as(@user)
- 1
visit user_path(@user)
- 1
expect(page).to have_content @user.username
end
end
- 1
require 'rails_helper'
- 1
describe 'the user update process' do
- 1
before do
- 3
@user = FactoryGirl.create(:user)
- 3
login_as(@user)
end
- 1
it 'can update a user', js: true do
- 1
visit user_path(@user)
- 1
click_link 'edit-user-link'
- 1
fill_in 'Username', :with => 'Steve'
- 1
find('input[type="submit"]').click
- 1
expect(page).to have_content 'Steve'
end
- 1
it 'throws error if username left blank' do
- 1
visit user_path(@user)
- 1
click_link 'edit-user-link'
- 1
fill_in 'Username', :with => ''
- 1
find('input[type="submit"]').click
- 1
expect(page).to have_content 'errors'
end
- 1
it 'can add an avatar' do
- 1
visit edit_user_path(@user)
- 1
page.attach_file("Avatar", 'spec/fixtures/images/avatar.jpeg')
- 1
find('input[type="submit"]').click
- 1
expect(page).to have_content @user.avatar
end
end
- 1
require 'rails_helper'
# Specs in this file have access to a helper object that includes
# the CategoriesHelper. For example:
#
# describe CategoriesHelper do
# describe "string concat" do
# it "concats two strings with spaces" do
# expect(helper.concat_strings("this","that")).to eq("this that")
# end
# end
# end
- 1
RSpec.describe CategoriesHelper, type: :helper do
end
- 1
require 'rails_helper'
# Specs in this file have access to a helper object that includes
# the SubscriptionsHelper. For example:
#
# describe SubscriptionsHelper do
# describe "string concat" do
# it "concats two strings with spaces" do
# expect(helper.concat_strings("this","that")).to eq("this that")
# end
# end
# end
- 1
RSpec.describe SubscriptionsHelper, type: :helper do
end
- 1
require 'rails_helper'
# Specs in this file have access to a helper object that includes
# the UpdatesHelper. For example:
#
# describe UpdatesHelper do
# describe "string concat" do
# it "concats two strings with spaces" do
# expect(helper.concat_strings("this","that")).to eq("this that")
# end
# end
# end
- 1
RSpec.describe UpdatesHelper, type: :helper do
end
- 1
require 'rails_helper'
- 1
RSpec.describe Category, type: :model do
- 2
it {should have_and_belong_to_many :challenges}
- 2
it {should validate_presence_of :name}
- 2
it {should validate_uniqueness_of :name}
end
- 1
require 'rails_helper'
- 1
RSpec.describe Challenge, type: :model do
- 2
it {should belong_to :user}
- 2
it {should have_many :updates}
- 2
it {should have_and_belong_to_many :categories}
- 2
it {should validate_presence_of :name}
end
- 1
require 'rails_helper'
- 1
RSpec.describe Subscription, type: :model do
- 2
it {should validate_presence_of :author_id}
- 2
it {should validate_uniqueness_of :author_id}
- 2
it {should belong_to :user}
end
- 1
require 'rails_helper'
- 1
RSpec.describe Update, type: :model do
- 2
it {should validate_presence_of :title}
- 2
it {should validate_presence_of :body}
- 2
it {should belong_to :challenge}
end
- 1
require 'rails_helper'
- 1
RSpec.describe User, type: :model do
- 2
it {should have_many :challenges}
- 2
it {should have_many :subscriptions}
- 2
it {should validate_presence_of :username}
end
- 1
ENV['RAILS_ENV'] ||= 'test'
- 1
require File.expand_path('../../config/environment', __FILE__)
# Prevent database truncation if the environment is production
- 1
abort("The Rails environment is running in production mode!") if Rails.env.production?
- 1
require 'spec_helper'
- 1
require 'rspec/rails'
- 1
require 'capybara/rails'
- 1
require 'capybara/poltergeist'
- 1
Capybara.javascript_driver = :poltergeist
- 1
include Warden::Test::Helpers
- 1
Warden.test_mode!
- 1
ActiveRecord::Migration.maintain_test_schema!
- 1
RSpec.configure do |config|
- 1
config.fixture_path = "#{::Rails.root}/spec/fixtures"
- 1
config.use_transactional_fixtures = false
# Bring in for AJAX tests:
- 1
config.before(:suite) do
- 1
DatabaseCleaner.strategy = :truncation
# Mock Fog calls
# Fog.mock!
# connection = Fog::Storage.new({
# :provider => 'AWS',
# :aws_access_key_id => 'bogus',
# :aws_secret_access_key => 'bogus'
# })
# connection.directories.create(:key => "lunarleap")
end
- 1
config.around(:each) do |example|
- 40
DatabaseCleaner.cleaning do
- 40
example.run
end
end
- 1
config.infer_spec_type_from_file_location!
end
- 1
Shoulda::Matchers.configure do |config|
- 1
config.integrate do |with|
- 1
with.test_framework :rspec
- 1
with.library :rails
end
end


microcephaly Zika dengue epidemic fever number cases virus {border-style ZIKV px;} #ffffff;} rate DENV Brazilian incidence Virus effect data previous time risk infection (). Dengue QGIS live region using Figure random years Brazil However, Information Map areas births high large px; {font-family Brazil. Foundation antibody epidemics estimated font-size presented (Fig. Data Fig. Health analysis anti-DENV double; immunity increased microregions neonates region, study window Congenital Development Fundação Geographic Geospatial Microcephaly Open Source Stamen System. Zika: antibodies associated available border-color border-width different included infections inhabitants interval level live-born microcephalic model plasma prior regions regions, solid; titres use week {font-style {font-weight (QGIS (grant (https://creativecommons.org/licenses/by/./) Commons Creative Design, Enhancement Infect. Infection Northeast OpenStreetMap, Pesquisa Project. Public. SA. babies bold cohort compared congenital considered courier; created cross-protection did ecological em; epidemic, epidemiological http://qgis.osgeo.org). increase infection. information lag larger main mice microregion, population possible present protect pt;} random-effects rates recent region. response standard tiles total version week,


An Everchanging Event Platform
Subscribe to get Events at Inbox
Subscribe to get Events at Inbox
Win the Cup with your Skill - Photography
Be Creative - Content Writing
Try to Crack the Problems! - Hackathons


About
California based software developer focusing on web technologies and development.
Web Developer & UI/UX Designer
I have been coding for close to 5 years as a mostly self taught web developer. I have always had a passion and desire to create and develop beautiful, interactive, and dynamic applications and websites. Right now my main stack of choice is javascript, node.js, and react.js but I am also proficient in C++ which I studied and worked with in college; but I am always open to and willing to learn new technologies and broaden my skills as a developer. I don't believe in constraining myself to one specific stack or language. I am always looking to challenge myself and what I already know.
Contact
Feel free to get in contact with me 😄
Location:
San Francisco Bay Area, California
Email:
danielausti@gmail.com


| time.mcmc {coda} | R Documentation |
These are methods for mcmc objects for the generic time series functions.
## S3 method for class 'mcmc' time(x, ...) ## S3 method for class 'mcmc' start(x, ...) ## S3 method for class 'mcmc' end(x, ...) ## S3 method for class 'mcmc' thin(x, ...)
x |
an |
... |
extra arguments for future methods |


Brock's Zubat
Was the third Pokémon acquired by Brock in the anime, and the first he caught within the series.


Some canned plots and functions designed for the mobilize project. Designed to be called remotely.
| Version: | 2.16-4 |
| Depends: | R (≥ 2.14), stats, methods, Ohmage |
| Imports: | ggplot2, wordcloud, reshape2 |
| Suggests: | XML, maps |
| Published: | 2014-09-12 |
| Author: | Jeroen Ooms |
| Maintainer: | Jeroen Ooms <jeroen.ooms at stat.ucla.edu> |
| License: | GPL-2 | GPL-3 [expanded from: GPL] |
| NeedsCompilation: | no |
| CRAN checks: | Mobilize results |
| Reference manual: | Mobilize.pdf |
| Package source: | Mobilize_2.16-4.tar.gz |
| Windows binaries: | r-devel: Mobilize_2.16-4.zip, r-release: Mobilize_2.16-4.zip, r-oldrel: Mobilize_2.16-4.zip |
| OS X binaries: | r-release: Mobilize_2.16-4.tgz, r-oldrel: Mobilize_2.16-4.tgz |
| Old sources: | Mobilize archive |
Please use the canonical form https://CRAN.R-project.org/package=Mobilize to link to this page.


|
VirtualSCADA
1.0
VirtualSCADA Senior Design Project
|
Public Member Functions | |
| __construct ($token) | |
| setToken ($token) | |
| getToken () | |
| setParent (Profile $parent) | |
| getParent () | |
| getParentToken () | |
| getIp () | |
| setIp ($ip) | |
| getMethod () | |
| setMethod ($method) | |
| getUrl () | |
| setUrl ($url) | |
| getTime () | |
| setTime ($time) | |
| getChildren () | |
| setChildren (array $children) | |
| addChild (Profile $child) | |
| getCollector ($name) | |
| getCollectors () | |
| setCollectors (array $collectors) | |
| addCollector (DataCollectorInterface $collector) | |
| hasCollector ($name) | |
| __sleep () | |
Definition at line 21 of file Profile.php.
| __construct | ( | $token | ) |
| __sleep | ( | ) |
Definition at line 271 of file Profile.php.
| addChild | ( | Profile | $child | ) |
Adds the child token.
Definition at line 202 of file Profile.php.
| addCollector | ( | DataCollectorInterface | $collector | ) |
Adds a Collector.
| DataCollectorInterface | $collector | A DataCollectorInterface instance |
Definition at line 254 of file Profile.php.
| getChildren | ( | ) |
Finds children profilers.
Definition at line 179 of file Profile.php.
| getCollector | ( | $name | ) |
Gets a Collector by name.
| string | $name | A collector name |
Definition at line 217 of file Profile.php.
| getCollectors | ( | ) |
Gets the Collectors associated with this profile.
Definition at line 231 of file Profile.php.
| getIp | ( | ) |
| getMethod | ( | ) |
Returns the request method.
Definition at line 130 of file Profile.php.
| getParent | ( | ) |
Returns the parent profile.
Definition at line 90 of file Profile.php.
| getParentToken | ( | ) |
Returns the parent token.
Definition at line 100 of file Profile.php.
| getTime | ( | ) |
| getToken | ( | ) |
| getUrl | ( | ) |
| hasCollector | ( | $name | ) |
Returns true if a Collector for the given name exists.
| string | $name | A collector name |
Definition at line 266 of file Profile.php.
| setChildren | ( | array | $children | ) |
Sets children profiler.
| Profile[] | $children An array of Profile |
Definition at line 189 of file Profile.php.
| setCollectors | ( | array | $collectors | ) |
Sets the Collectors associated with this profile.
| DataCollectorInterface[] | $collectors |
Definition at line 241 of file Profile.php.
| setIp | ( | $ip | ) |
| setMethod | ( | $method | ) |
Definition at line 135 of file Profile.php.
| setParent | ( | Profile | $parent | ) |
Sets the parent token.
Definition at line 80 of file Profile.php.
| setTime | ( | $time | ) |
Definition at line 169 of file Profile.php.
| setToken | ( | $token | ) |
| setUrl | ( | $url | ) |
Definition at line 150 of file Profile.php.


--- layout: post date: 2010-10-05 time: "09:00:00" authors: ["Greg Wilson"] title: Using Subversion from the Command Line tags: ["Content"] ---
Ainsley Lawson, one of the TAs for the Fall 2010 online course, has recorded an 8-minute episode showing how to use Subversion from the command line. We hope you find it useful.


Properties
The Properties window provides the opportunity to edit and view information about the project.
- Project Name: Displays the Name of the project. To change the name of the project go to File and select Save As. Use Save As to rename your project.
- Project Description: Enter a description for this project by typing in the Project Description text box. After saving the project, the description will appear in this location, and can be edited at any time.
- Project File: Displays the location that the project is stored. If the entire path name is not visable drag the window wider to reveal the entire name.
- Created By: Displays the user name of the person who created the project.
- Created Date: Displays the date and time when the project was first created.
- Project Notes: Enter notes for this project by clicking in the text box. After saving the project, the notes will appear in this location, and can be edited at any time.
- Monetary Unit: Displays the monetary units used in the project. The default units are in thousands of dollars, but can be changed by using the dropdown box to dollars, or millions of dollars.
- Unit System: Select the unit system for the project. The default is the English system but can be changed using the dropdown box to SI units.
- Surveyed Year: Displays the year the data was surveyed. This value can be changed by clicking in the text box.
- Updated Year: Displays the updated year. This value can be changed by clicking in the text box.
- Updated Price Index: Displays the updated price index.


If you're new to Mesos
See the getting started page for more information about downloading, building, and deploying Mesos.
If you'd like to get involved or you're looking for support
See our community page for more details.
Release Guide
This guide describes the process of doing an official release of Mesos.
Prerequisites
Ensure that you have a GPG key or generate a new one, e.g., using
gpg --gen-key
.Add your GPG public key to the Apache Mesos dist repository in the KEYS file.
Fetch the svn repository:
svn co https://dist.apache.org/repos/dist/release/mesos
Append your public key using one of methods described in KEYS, e.g.:
(gpg --list-sigs <your name> && gpg --armor --export <your name>) >> KEYS
.Push the commit:
svn ci
Submit your GPG public key to a keyserver, e.g., MIT PGP Public Key Server.
Add your GPG fingerprint (
gpg --fingerprint <your name>
) to your Apache account.Create a Maven settings file (
~/.m2/settings.xml
) for the Apache servers where you must copy your encrypted Apache password which you can get from runningmvn --encrypt-password
.NOTE: You may need to first generate a master password.
<settings> <servers> <server> <id>apache.snapshots.https</id> <username>APACHE USERNAME</username> <password>APACHE ENCRYPTED PASSWORD</password> </server> <server> <id>apache.releases.https</id> <username>APACHE USERNAME</username> <password>APACHE ENCRYPTED PASSWORD</password> </server> </servers> </settings>
Use
gpg-agent
to avoid typing your passphrase repeatedly.
Preparation
Go to Apache JIRA and make sure that the
CHANGELOG
for the release version is up to date.NOTE: You should move all Unresolved tickets marked with
Fix Version
orTarget Version
as the release version to the next release version.PROTIP: Use a JIRA dashboard (example) to track the progress of targeted issues as the release date approaches. This JIRA filter may be useful (
<X.Y.Z>
is the release version):project = MESOS AND "Target Version/s" = <X.Y.Z> AND (fixVersion != <X.Y.Z> OR fixVersion = EMPTY)
PROTIP: Use
bulk edit
option in JIRA to move the tickets and make sure to uncheck the option that emails everyone about the move to avoid spamming.Checkout the correct branch for the release. For regular releases this is the “master” branch. For patch releases this would be the corresponding release branch (e.g., 1.0.x).
Update and commit the
CHANGELOG
for the release.For regular releases:
Make sure all new API changes, deprecations, major features, and features graduating from experimental to stable are called out at the top of the
CHANGELOG
. This JIRA query may be helpful in identifying some of these (<X.Y.Z>
is the release version):project = MESOS AND "Target Version/s" = <X.Y.Z> AND type = Epic
Ensure that the “Unresolved Critical Issues” section is populated correctly. This JIRA query may be helpful:
project = Mesos AND type = bug AND status != Resolved AND priority IN (blocker, critical)
Prepare a full list of experimental features. The easiest way to do this is to take the list from the previous minor release, remove features that have been declared stable, and those, that declared experimental in the current release. Do not forget to mention features transitioning from experimental to stable in this release at the top of the
CHANGELOG
.
NOTE: You should use JIRA to generate the major portion of the
CHANGELOG
for you. Click on the release version in JIRA and click on theRelease Notes
. Make sure to configure the release notes in text format.NOTE: The JIRA Release Notes will list only tickets with
Fix Version
set to that version. You should check for any Resolved tickets that haveTarget Version
set but notFix Version
. Also check for any Unresolved orDuplicate
/Invalid
tickets that incorrectly set theFix Version
.For patch releases update the
CHANGELOG
on master branch and then cherry pick onto the release branch.Ensure version in
configure.ac
andCMakeLists.txt
is correctly set for the release.Run
make && support/generate-endpoint-help.py
and commit any resulting changes.Update and commit
docs/configuration.md
to reflect the current state of the master, agent, and configure flags. If this is a patch release, update it on master branch and then cherry pick onto the release branch.If this is a regular release, update and commit
docs/upgrades.md
with instructions about how to upgrade a live cluster from the previous release version to this release version.If this is a regular release, please ensure that user documentation has been added for any new features.
Make sure that for any updates of the API, specifically the scheduler API, the public mesos protobuf definitions are part of both,
include/mesos
as well asinclude/mesos/v1
.NOTE: This might actually demand code updates if any omissions were identified.
Tagging the Release Candidate
Ensure that you can build and pass all the tests.
$ sudo make -j<cores> distcheck
Run the benchmarks and compare with the previous release for any performance regressions:
$ make bench -j<cores> GTEST_FILTER="*BENCHMARK*"
First tag the required SHA locally.
$ git tag <X.Y.Z-rcR>
NOTE:
X.Y.Z
is based on semantic versioning scheme.R
is release candidate version that starts with 1.Tag the release externally and deploy the corresponding JAR to the Apache maven repository. It is recommended to use the
support/tag.sh
script to accomplish this.$ ./support/tag.sh X.Y.Z R
NOTE: This script assumes that you have the requisite permissions to deploy the JAR. For instructions on how to set it up, please refer to
src/java/MESOS-MAVEN-README
.NOTE: gnu-sed (Linux) requires
-i''
instead of the-i ''
(space-separated) that default OSX uses. You may need to modify your local copy oftag.sh
for it to complete successfully.If this is a regular release, create a new release branch (
. .x) from this tag. $ git checkout -b X.Y.x
Now, update master branch to the next minor version in
configure.ac
: changeAC_INIT([mesos], [X.Y.Z]))
, as well as inCMakeLists.txt
: changeset(MESOS_MAJOR_VERSION X)
,set(MESOS_MINOR_VERSION Y)
,set(MESOS_PATCH_VERSION Z)
and then commit.
Voting the Release Candidate
Once a release candidate is deemed worthy to be officially released you should call a vote on the
<EMAIL_ADDRESS>(and<EMAIL_ADDRESS>) mailing list.It is recommended to use the
support/vote.sh
script to vote the release candidate.$ ./support/vote.sh X.Y.Z R
The release script also spits out an email template that you could use to send the vote email.
NOTE: The
date -v+3d
command does not work on some platforms (e.g. Ubuntu), so you may need to fill in the vote end date manually. The vote should last for 3 business days instead of 3 calendar days anyway. Sometimes we allow a longer vote, to allow more time for integration testing.
Preparing a New Release Candidate
If the vote does not pass (any -1s or showstopper bugs), track the issues as new JIRAs for the release.
When all known issues are resolved, update the
CHANGELOG
with the newly fixed JIRAs.Once all patches are committed to master, cherry-pick them on to the corresponding release branch. This is the same process used for patch releases (e.g., 1.0.2) as well.
$ git checkout X.Y.x $ git cherry-pick abcdefgh...
Now go back up to the “Tagging the Release Candidate” section and repeat.
Releasing the Release Candidate
You should only release an official version if the vote passes with at least 3 +1 binding votes and no -1 votes. For more information, please refer to Apache release guidelines.
It is recommended to use
support/release.sh
script to release the candidate.$ ./support/release.sh X.Y.Z R
The release script also spits out an email template that you could use to notify the mailing lists about the result of the vote and the release.
NOTE: Make sure you fill the email template with the names of binding and non-binding voters.
Update the version in
configure.ac
andCMakeLists.txt
in the release branch to the next patch version.
Updating the Website
After a successful release, add the information associated with the release in
site/data/releases.yml
. It is used to generate the release information on the website.Update the Getting Started guide to use the latest release link.
Check out the website from svn.
$ svn co https://svn.apache.org/repos/asf/mesos/site mesos-site
See our website README for details on how to build the website. See the general Apache project website guide for details on how to publish the website.
Write a blog post announcing the new release and its features and major bug fixes. Include a link to the updated website.
This command may be helpful to gather the list of all contributors between two tags:
git log --pretty=format:%an <tagX>..<tagY> | sort | uniq | awk '{print}' ORS=', '
Mention the blog post in
site/data/releases.yml
.
Removing Old Releases from svn
Per the guidelines when to archive, we should only keep the latest release in each version under development.
Checkout the mesos distribution folder:
$ svn co https://dist.apache.org/repos/dist/release/mesos
Remove all minor versions that are no longer under development and commit the change.
Releasing the Version on JIRA
Find the released Mesos version here, and “release” it with the correct release date by clicking on “settings” → “Release”. Also, make sure to add the names of the release managers in “Description” section.
Updating External Tooling
Upload the mesos.interface package to PyPi.
Create/use a PyPi account with access to the mesos.interface submit form. You may need to ask a current package owner to add you as an owner/maintainer.
Setup your
~/.pypirc
with your PyPi username and password.After a successful Mesos
make
(any architecture), cd tobuild/src/python/interface
.Run
python setup.py register
to register this package.Run
python setup.py sdist bdist_egg upload
to upload the source distribution and egg for this package.
Update the Mesos Homebrew package.
Update the Homebrew formula for Mesos and test.
Submit a PR to the Homebrew repo.
Once accepted, verify that
brew install mesos
works.


The Hurricane Story:
Examining Spatiotemporal Pattern of Twitter Trajectory in 2017 Atlantic Hurricane Season
There is an increasing risk of tropical cyclones recent years causing a large amount of loss of assets. However, the fatalities are relatively low because of effective protective actions such as getting sheltered and evacuated. A more comprehensive understanding of the evacuation behaviors will benefit the management greatly.
Post-event survey is the traditional practice to collect the information of evacuation behaviors with limitation of high cost and low efficiency, while user-generated social media data provides great potentials to better understand and detect the spatiotemporal pattern of the evacuation behaviors during hurricane seasons.
Using the 2017 Atlantic Hurricane Season as a study case, we mainly focus on two hurricanes: 1) The NO.9 Hurricane - Harvey, which is tied with 2005's Hurricane Katrina as the costliest tropical cyclone on record, inflicting $125 billion in damage, primarily from catastrophic rainfall-triggered flooding in the Houston metropolitan area and Southeast Texas; 2) The NO.11 Hurricane - Irma, which is the strongest observed in the Atlantic in terms of maximum sustained winds since Wilma, and the strongest storm on record to exist in the open Atlantic region. The following map shows their moving tracks:
Based on Twitter data collected with keywords during 2017 Atlantic Hurricane Season, filtering out the unrelated tweets (e.g. entirely out of the U.S), non-humman users (e.g. public media and bots) as well as invalid trajectories (i.e. moving faster than plane), we generate the evacuation trajectories of valid twitter users and visualize the movement path. In the following interative map, the color of trajectories shows time range: The order of Red-Yellow-Blue indicates the date in August-September-October 2017.
After exploring the map, we can easily notice the two biggest clusters, which are the red trajectories around Houston area (showing people's evacuating routes during Hurricane Harvey in August 2017) and the yellow ones along with Florida (showing the evacuating routes during Hurricane Irma in September 2017).
To better understand the moving pattern, we will further compare where people are moving from, and where are people moving to. Inspired by the wind-rose graph in atmospheric science, we made these charts in which the moving angle/directoin are excatly the same, but the distances are cut down proportionally.
We make all these wind-rose charts by state, and allocate them at the centroid of each corresponding state. The first/left map shows the origin (beginning location) of each trajectory by state, and the second map shows the destination (ending location) of trajectory. Same as before, the color here shows the time range.
It is fun to play with the switch and compare the difference. As for the origins (left map), a large group of people were traveling from Texas towards northeast, west and even southeast; a lot of people were traveling from Florida to the north and north west, which clearly shows where people were moving towards, during Hurricane Harvey and Irma. As for the destinations (right map), California is obviously the most welcome target, and the northeast also accepted many evacuees.
Further spatiotemporal analytics and visualizations are expected to come soon!
Design & Cartography by Chenxiao (Atlas) Guo, December 2018


--- layout: post title: ScrumMaster/Office Manager wanted! date: 2010-03-01 00:00:00 categories: business software-development ---
We're recruiting, for a dual ScrumMaster/Office Manager role: someone to focus full-time on identifying and fixing issues, and on improving the efficiency of everyone here at FP.
The right person for the job will be smart, unintimidated by technology, calm under fire, and interested in learning. They might have experience in Scrum, but that's not essential as long as they have a clear enthusiasm and willingness to learn; we'll provide a lot of support during the early stages (we have certified staff in-house and have been running Scrum ourselves for more than 2 years), and training too.
The job description is short but broad:
ScrumMaster/Office Manager
Position reports to: Technical Director
Overview: Owns and organises the production process and office environment
Key Responsibilities:
- Facilitating daily standups for our two production teams
- Identifying and resolving impediments to progress of the teams
- Working with the Product Owners to create long-term release plans for the business
- Facilitating fortnightly sprint demos, retrospectives and planning sessions
- Administrative support to the management team
Scope:
- Predominately an internally facing role, with the exception of fortnightly demos and planning sessions
Training:
- Will be supported through Certified Scrum Master and Certified Scrum Practitioner qualifications
Email<EMAIL_ADDRESS>with a CV if you're interested.


English | Estonian
Current language: English
Open this page in multiple tabs or windows and if language is changed in one tab, the others should change too.


Dear {{ user.username }},
The following is your post:
Have fun with Microblog!
Sincerely,
The Microblog Team


Thanks to “Compilers” being the main keyword for this course, we also learned a great deal about Programming Language.
In a previous article I described what features can differentiate a programming language from the others. In particular:
- General Purpose vs Domain Specific Language.
- High vs Low Level Language.
- Interpreted vs Compiled Language.
- Procedural vs Functional vs Object Oriented Language.
- Typed vs Untyped Language.
- Statically vs Dynamically Typed Language.
- Static vs Dynamic Scope.
- Automatically Managed Memory (Garbage Collector) vs Manual Memory Management.
These are core features design of a language. The person (or the team) that works on that language development, and its compiler, has to make a choice for each of the above points, and even more.
As a result, there are a lot of Programming Languages out there. Each Language has its unique set of features, although, in all honesty, some languages are really similar.
A common question is what’s the fastest programming language?
First of all, the question asked in this form makes little sense. For a number of reasons:
- The quality of your code is more important than the efficiency of the language you use, for 99.9% of applications.
- Actual speed of execution strongly depends on the hardware, and not just on the programming language.
- Even on the same hardware, the current CPUs and RAM are such that in a tiny percentage of cases you will experience a performance difference due to the programming language.
- There are many things that you can’t know about how the Compiler modifies your code, to optimize the execution. I talked about them in a previous article.
In different words, much before thinking about the performance of the language you chose, and of its compiler, you should focus on different things, much more important:
- Write the highest-quality code you can.
- Use standard, well-known software pattern design. They improve readability and overall maintenance of the code, hence performance.
- Choose well tested, robust, external libraries and packages if you need any.
That said, the main question still stands, and it’s an interesting one from a theoretical point of view.
If we could implement the same algorithm, on the same hardware, with all other conditions being the same, in different Programming Languages, which would be the fastest?
To answer that, and in view of all other important points I mentioned, I want to discuss the top-3 features that impact the efficiency.
Assembled vs Compiled vs Interpreted
In fact, there’s little doubt. Assembled code is the fastest.
Speaking from a theoretical point of view, if you could always write your programs in Assembly code, and you could also always write the best Assembly code that’s possible, then yes, your Assembly code would always be the fastest.
That’s because Assembly code doesn’t need to pass through a Compiler. It’s directly assembled into CPU instructions. Blazing fast.
Needless to say, that’s quite a lot of hypotheses.
First of all, most modern programs would be painful to write in Assembly.
Secondly, very few programmers are trained to write efficient Assembly code. This is a direct consequence of the previous point. Therefore, it’s highly possible that a good code, say in C, compiled with a good Compiler becomes more efficient than a poorly written Assembly code.
In other words, if you are not an Assembly developer, then a good Compiler can written better Assembly code than you, even if it’s just a software!
If you don’t want to write Assembly code, then again, one can make an educated statement: Compiled code is the second fastest (among the three types we are discussing).
Briefly explained, the reason is that Compilers produce so-called “target code”, that’s basically machine code. On the other hand, Interpreters add one more layer between the execution environment for your program, and the Operating System, and that slows things down a bit.
Abstraction
Why is C that fast?
As a programming language, C doesn’t offer you anything special.
- There are no class and inheritance.
- There is no dynamic typing.
- Arrays boundaries are not checked (you don’t know the length of an array a-priori).
- There’s nothing cleaning up memory after you (you must do it manually).
In other words, C code is just a little bit more abstract than Assembly code. This allows a very good C developer to write highly efficient code.
On the other hand, C code is not really safe. Every time you perform an operation on the computer memory, for example using memcpy, it’s not even checked what was before in that memory locations, and if there’s any overlap. Trust the programmer is C’s spirit.
Other languages provide more abstraction and more security.
To start with, all OOP Languages allow us to define complex objects and new types, along with the operation that one can use on them.
Then, things like the Java Virtual Machine (or Python’s interpreter) make the program execution overall much safer. But, they do spend some time to perform security checks, during the execution itself.
It must be said that Just-In-Time compilers exist for many languages, and they give great performance improvements. But that’s an entirely different topic.
Tie with the Application
If you work on an application and could write for it a C program that takes 1 week to write and runs in 0.1 seconds, or a Python program that takes 1 day to write, and runs in 5 seconds, which option would you choose?
I guess it really depends on the actual application.
If the program is meant to run once a day, then maybe it doesn’t matter how fast it is.
But if you must run it 100.000+ times a day, on several machines, then the CPU-time on these machines would be very different if you sue C or if you use Python. And so would be the total power consumption of your computers, which means money. In this case, spending one week writing good C code can save you lots of money.
The point I am making here is that execution speed is often a relative concept. Other factors play an important role, such as how much speed do you really need, what’s the benefit of some speed improvement, as well as the trade-off between execution speed and development speed.
But so, Which Programming Language is the Fastest?!
I purposefully avoided to give a firm answer on this question in the previous part of this article, because I think this is not the correct design question to ask when building something.
That said, if you really can’t resist, just know that C is usually taken as reference point.
That means that performances of new languages are evaluated by comparing execution of standard algorithms with the runtime of the same algorithms implemented in C.
According to many sources (that you can google yourself) C, Rust, C++ and Fortran are always at the top of the many ratings for the fastest programming language.
As additional study, I warmly recommend to check you the link in the references to the page Bad Code Can Be Written In Any Language.
To conclude. Which programming language is fastest? Should we care? How could we know? (from The Benchmarks Game).
References
My article What are the differences between programming languages?.


Pharmacists as Trusted Providers
Description: Syrian refugees from the focus group discussed the importance of pharmacies as a healthcare service. Several participants discussed that pharmacists became trusted healthcare providers for refugees. They were perceived as a higher quality and lower cost option in certain circumstances.
Comments: - 'The participants stressed that there is no free health service center makes them feel safe. Instead, they prefer to go to a nearby or trusted pharmacist.'
- 'They always help family members and friends in any medical condition by taking them to this trusted pharmacist.'
- 'She took the child to a well-known pharmacist in the area where she lives who diagnosed the condition and gave her a different drug. The child’s health improved because of this new drug, which deepened the family’s trust in this pharmacist. The pharmacist was kind and sympathetic and showed compassion with the child’s condition.'
Full Data link


|
The Class Notes have sung at many different events in many different countries. We have toured the US extensively and have performed at weddings, colleges, and at major events such as the 1999 Christmas Tree Lighting at Rockefeller Center in New York City. Add a touch of class to your next event! PHONE<PHONE_NUMBER> Phil Torres General Manager WEB Email<EMAIL_ADDRESS>Url: http://www.theclassnotes.com The Class Notes Box 36 WSH Ithaca, NY 14853 |


Extracellular vesicles (EVs) released by living cells include exosomes and microvesicles (MVs), which contain various molecules from parental cells and are potential sources for disease diagnostic and therapeutic biomarkers. miRNA is the most well-studied molecule type in EVs because of its important functions and biomarker properties. Thus, we build the Extracellular Vesicles miRNA database (EVmiRNA) to collect comprehensive miRNA expression profiles in EVs.
In EVmiRNA database, we analyzed 462 smRNA sequencing datasets of EVs from 17 tissues/diseases. The miRNA expression profiles, miRNA regulated pathways, miRNA function, miRNA related drugs and publications are showed to support the miRNA biomarker discovery.


Learn
More about PACO
What is PACO good for?
Many types of mobile experiments!
Quantified Self
Ever wonder how happy you are? Whether your weight is trending up or down? Do you want one place to manage the data and reminder scheduling for all your mobile exercise trackers, weight trackers, baby's bowel movement trackers, fuel consumption trackers (is that the same as the previous one?)?
Mobile Population Studies - Wellness, Corporate environment, or Whatever
Ever want to design, iterate, and deliver a social science experiment or mobile wellness intervention to a group of people on Android mobile phones in a matter of minutes? (You social and behavioral scientists out there know who you are.)
User Control of Data
Do you want to be able to correlate your data across multiple trackers?
Do you want your data kept private and under your control? With informed consent about what you are sharing and with whom?
If you answered yes to any or all of these questions,
then,
Paco is the tool for you! Though we are still building
a lot of these features, so don't be too judgmental just yet -
instead
chip in some of your own 20% time.
What does PACO provide?
PACO allows rapid creation and iteration of
experimental trackers and interventions.
You can create a new mobile phone experiment in a matter of minutes on the PACO website. Once you save it, it is ready to download into the PACO Android app. You can keep your experiment designs private, share them with select groups of people, or with the world (Gmail logins for the moment). If you decide that an experimental input isn't quite right, just update it and then within a day the Android app will pick up the new definition.
PACO uses a novel, but validated sampling technique known as Experiential Sampling.
Experiential Sampling was developed by Psychology researchers and has been used in 10s of 1000s of experiments over the last 40 years. It provides a much more accurate way to gather a sample of daily experience by pinging randomly over a period of time. However, PACO can also do more traditional sampling schedules if necessary.
PACO allows users to easily explore and ask questions about their data.
PACO comes with a feature called, Explore Data, that guides the user through answering specific questions about their data. It offers a choice of questions about trends in the data, relationships in the data, and the distribution of the data. It allows the user to chart data across experiments as well to visualize any relationships that might exists between different data sets.
PACO Examples
PACO is designed so that you can hear
about a new medical study on the radio and then build a version for yourself in minutes.
Here are some types of "experiments" PACO can help you create:
- Personal diet and wellness data
- Example: You decide to practice healthy eating by following, say, the guidelines in Michael Pollan's Food Rules, and you want to see how well are following the program. With PACO and an Android phone you can easily create a personal "experiment" that will automatically ask you to rate your meal based on the three core food rules (Did you eat food? Was it mostly plants? Was it too much?) and help you track them. You can also easily add weight, blood pressure, cholesterol, etc., to the data you track and collect.
- Below are sample screen from Alberto's LowCarbTracker experiment:
- Personal exercise or activity data
- Example: You are a runner and you want to track not only how many miles you run each day but also, say, how you feel before, during and after a run. PACO makes it easy to create a study to collect, store and analyze this data.
- Personal work data
- Example: You would like to keep track of where you spend your time at work (34% of my time in meetings! Aaargh!) and how productive or passionate you are feeling about your work. The best way to collect this data is to use Experience Sampling Method (ESM for short.) With PACO you can easily create a simple ESM study that will ask you at random times what you are doing and, say, if you are feeling productive and passionate at that particular time.


---
layout: base
title: "Damir Cavar's CV - Research projects"
author: "Damir Cavar"
desc: "This is Damir Cavar's Research section of the Curriculum Vitae (CV)."
keywords: "Damir Cavar, CV, Research, LINGUIST List, Computational Linguistics, Natural Language Processing, CL, NLP"
link: research
---
Curriculum Vitae: Damir Cavar - Research Projects
Content
Research projects
My research lab, called the NLP-Lab at Indiana University meets usually 4 times per week. The times and other details are available on the website and the Slack channel.
Ongoing projects:
- HooSIER - HooSIER
Semantic Information ExtractoR is a text to semantic or knowledge graph system with Deep NLP and
Deep Graph Processing algorithms for learning of probabilistic Knowledge Graphs from unstructured texts, and in
the next phase from visual or multi-modal input. This project is part of my NLP-Lab
activities.
The HooSIER project subsumes the engineering and standardization effort
related to JSON-NLP, the engineering of a
big-data capable NLP platform of high-performance Microservices for Deep NLP,
Knowledge Graphs, and Natural Language Semantics and Pragmatics.\\
This project is related to my interests in High-Performance Computing for NLP: HPNLP.org.
- NLP for Medical
Natural Language Processing of Medical Documents, Information Extraction (IE), Mapping of Text to Knowledge Graph,
Semantic Search over medical documents, using Deep Learning and Knowledge Driven hybrid methods.
- NLP for Legal
Natural Language Processing of Legal Documents, Information Extraction (IE), Mapping of Text to Knowledge Graph,
Semantic Search over legal documents.
- Hate Speech and anti-Semitism in Social Media (see Social Lense Online)
Corpus annotation and creation of AI and NLP technologies for the detection and annotation of content in text and images.
This is a joint project with Günther Jikeli at
Indiana University, sponsored, among others by the Office of the Provost for Reseach
at Indiana University.
- Business Document Mining and Semantic Web
Awards:
- Collaborative Research Grant together with Prof. Matthew Josefy from the Kelley School of Business
at Indiana University on: Technologies for Deep Linguistic NLP for mining of SEC reports, network
mapping of people and firms, and risk management analyses. Funded by the Office of the Office of the Vice Provost for Research at Indiana University.
- Joint fellowship with Prof. Josefy from the Kelley School of Business at Indiana University: Fellows of the National Center for the Middle Market at the Fisher College of Business, The Ohio State University. The project is on extraction of business data from SEC reports of Middle Market firms.
Legacy projects that are still maintained:
- GORILLA (Global Open Resources and Information for Language and Linguistic Analysis), Speech and Language
Resources, Corpora, Speech Recognition and related technologies for low-resourced languages: Burmese, Chatino, Croatian, Yiddish, ... See also: GORILLA
- Free Linguistic Environment
(FLE): algorithms for morphological, syntactic and semantic
analysis of natural language for a grammar engineering platform for different grammar formalisms, e.g.
Context-free grammars (CFG), Probabilistic Context-free Grammars (PCFG), the
Lexical Functional Grammar
(LFG), Construction Grammar (CxG),
and related frameworks. See also the Bitbucket repo, the
FLE Mailing list, and the
FLE Slack Team
Awards:
Former projects:
- LL-Map (maintenance, previous NSF funding)
- GOLD (maintenance, continuation in new form, previous NSF funding)
- LEGO (maintenance, continuation in new form, previous NSF funding)
- MultiTree: Completing the Library of Language Relationships
Award Number: 1227106; Principal Investigator: Damir Cavar, former PIs: Helen Aristar-Dry, Anthony Aristar. Organization:
Eastern Michigan University; NSF Organization: BCS Award Date: 07/12/2012; Award Amount: $ 153,885.00.
Project
page: multitree.org
- Automatically
Annotated Repository of Digital Video and Audio Resources Community
(AARDVARC)
Award Number: 1244713; Principal Investigator: Damir Cavar; former
PI: Helen Aristar-Dry and former Co-PIs: Anthony Aristar, Damir Cavar; Organization: Eastern Michigan
University; NSF Organization: BCS Award Date: 09/15/2012; Award Amount: $ 84,982.00. Collaborative grant: PI Douglas H. Whalen, CUNY.
Project page: linguistlist.org/aardvarc
- Croatian computational morphology with XFST/Foma, (porting CroMo from a Ragel-based Finite State Transducer model to Lexc)
- The Scheme Natural Language Toolkit
(SNLTK)
This
project is a no-budget project to develop a Scheme and Racket
implementation
of libraries and functionality for the analysis and processing of text, language and linguistic data. This
project is open to all interested parties, and mainly supported by the Schemers or Racketeers
in Zadar, and myself.
- The Croatian Language Corpus
(CLC)
(Hrvatski jezični
korpus)
is a joint project with the Institute for Croatian Language and Linguistics, as part of the program
"Croatian Online Language Repository", in cooperation with Dunja Brozović-Rončević, Małgorzata E. Ćavar, Tomislav Stojanov. The CLC
is a
text corpus of Croatian literature, newspapers and other genres, encoded in XML on the basis of the TEI P5 standard, made available online
using
the Philologic interface. Currently
additional interfaces are being developed and tested, to extend the online usability and user experience, when
working with the corpus. The corpus is being annotated phonemically and morphologically and syntactically
parsed. We ported an initial hand-crafted morphological analyzer to XFST, and we are
working on a Croatian LFG
grammar for XLE for syntactic parsing and
functional markup. An extended search interface that allows for online retrieval of linguistic annotations and
structures at these linguistic levels will be provided in the near future.
- Semantic Nets and
Computational Lexicology
This project is part of a research program at the Institute of Croatian Language and Linguistics (IHJJ), funded by the Ministry of Research,
Education, and Sports of the Republic of Croatia, since November 2006. Several researchers at the University of Zadar and the Institute of
Croatian Language and Linguistics are affiliated with it.
- Applied Technology for Language-Aided CMS (ATLAS) till September 2010
Workpackages leader:
Damir Cavar (Croatian Language
Processing Chain and Multilingual Document Classification)
EC web site
Funded under: The Information and Communication Technologies Policy
Support Programme
Area: CIP-ICT-PSP.2009.5.3 - Multilingual Web : Multilingual Web content management:
methods, tools and processes
Total cost: €3.32m; EU contribution: €1.66m; Project reference:
250467; Execution: From 01/03/2010 to 28/02/2013; Project status: Running
In cooperation with: Pavle
Valerijev (University of Zadar), Franjo Pehar (University of Zadar), Damir Kero (University of Zadar), Drahomira
Gavranović (University of Zadar), Malgorzata E. Cavar
(University of Zadar)
Consortium:
Tetracom Interactive Solutions (Tetracom) – Coordinator;
Deutsches Forschungszentrum Fuer Kuenstliche Intelligenz GmbH (DFKI); Instytut Podstaw Informatyki Polskiej
Akademii Nauk (ICS PAS); Atlantis Consulting SA (Atlantis); University Alexandru Ioan Cuza (UAIC); Institute for
Bulgarian Language (IBL DCL); Institute of Technologies and Development Foundation (ITD); University of Hamburg
(UHH); University of Zadar (UniZD)
- ABUGI (Alignment based grammar induction)
Unsupervised Grammar Induction; with Joshua Herring, Toshikazu Ikuta, Paul Rodrigues, Giancarlo Schrementi,
Linguistics Dept., Indiana University.
- A quantitative Model of Contact-Induced Language
Change...
with a Focus on Pidginization and Creolization
This grant was funded in 2005 and 2006
by the FRSP Award program, Linguistics Dept., Indiana University.
Northern
Caddoan Languages Documentation Project
Award Number: 0421838; Principal
Investigator: Douglas Parks; Co-Principal Investigator: Wallace Hooper, Damir Cavar; Organization: Indiana
University; NSF Organization: BCS Award Date: 07/15/2004; Award Amount: $ 324,999.00


Installation
sudo apt-get install hugo
Go to folder structure and do
hugo new site <project_name>
A Bunch of folders will be created
Folder_Structure
archetypes
content
data
layouts - You can define complex layouts in a hugo - like same header and footer in all pages in webiste , like writing a header.html and footer.html
static
themes
config.toml
You can define
title of webiste
what language it is written in
base URL
About Themes
.toml
fileAbout Content
hugo new manoj.md
you can add subdirectories also and add content files
Each folder should have _index.md
because it would the home page for list
Starting Server
hugo server -D
D
Option is for telling the server to include the draft files too otherwise we cant see the working files coz when we create content files it will set draft = true
by defaultContent Organization
Hugo defines two seperate types of content(breakdowns all the content of the website into two types)
single pages
to serve only particular content
list pages
eg : Home page , to list other pages
When you are doing just breakdown content into list pages and single pages
Front Matter in Hugo
can be written in
Default
ArcheTypes
when we create a new content file we will get some front matter , how will it be created ?(using archetypes
)
in archetypes there is default.md
folder
That will be taken as reference for front matter - for all new files
we can have different archetypes for different for different files
Just you have to give the containing dir name in archetype
folder
If it cant find the container folder it will take from default files
Short Code
html
we can have snippets called short codes
for eg : to embedd a youtube video "{{ <youtube qtIqKaDlqXo>}}"
“Please remove space between bracker and youtube”
Taxonomies
2 types
tags
Suppose if we want to tag different blogs with different key words
when you click on tags hufo automatically creates a page with tag in the route
when you create a new taxonomies you have to decalre the default tags and categores
along with cusotm
Eg :
[taxonomies]
tag = "tags"
category = "categories"
mood = "moods"
singular = plural syntax
categories
Group different pieces of content with different categories
when you change config.toml
you have to restart the hugo
server
Templates
html
which is same on every page for eg : menu bar html is a templatelayouts
folder with _default
folder and list.html
which is a page used to render#### Hugo variable
{{.Content}}
which wll display the index content
In order to loop
{{range .Pages}}
{{.Title}}
{{end}}
means i want to range over pages and display title
{{range .Pages}}
{{.URL}}
{{end}}
-means range over pages and display the route
layouts
folder with _default
folder and single.html
which is a page used to render{{.Title}}
or {{.Date}}
layouts
folder with index.html
file### Section Templates
we can create in layouts
folder with content
sub folders


"buttons" below shall have gradient background on screen. On print they will have solid gray background.


Only Allow Access to This Domain
Disallow Access to This Domain
Hide This Tab
Hide All Other Tabs
Hide Tabs on This Domain
Hide Tabs Not on This Domain
Manage Hidden Tabs
Remove All Data


ice sheet SLR temperature Fig. projections experts range values likely percentile Appendix, median {border-style rise sea-level contributions px;} #ffffff;} expert total GrIS mean future level Antarctic SEJ Table Climate climate contribution global scenarios sea using Note University scenario sheets tail high probability processes uncertainties uncertainty Change RCP WAIS approach credible dependence findings upper compared projection result value Global Panel experts’ given projections, px; questions recent statistical used {font-family AIS Intergovernmental Kopp Sci. United based elicited font-size judgement mass provided responses shown study EAIS Ice PDFs WAIS, accuracy assuming century change combination combined dependencies different distribution distributions double; exceeds including increase larger range, understanding warming Bamber Classical Cooke Future Greenland Horton Model Nat. Nature Oppenheimer Pollard Report border-color border-width end external largest long loss percentiles probabilistic process response results scientific solid; surface target {font-style {font-weight (denoted AR, AR. Acad. Assessment Clim. EAIS, European Fifth Grant Here, Lett. Methods National Natl. New Princeton Proc. RCP. Res. SLR, Science Sea-level West York accumulation, and, article available basis bold broadly central cm, coastal comparable comparison consideration considered courier; current discharge em; estimates example, factor fifth higher http://orcid.org/--- important include internal joint judgments land large marine mm⋅y model modeling performance positive potential pt;} record regional representation respectively. scenario. similar studies substantially thermal threshold use weight weighted weights workshops °C, EAIS GrIS PW WAIS


This is your public task tracker.
This is a gamified platform for connecting and encouraging people.
This is a social network for people who want to do stuff.
This is a place to gather and provide feedback on the things you did and on the things you're going to do.
Finally, you can get game points here!


Images and other file resources can be loaded based on scale factor, high contrast mode, user language and other dimensions. All file references in HTML, CSS or code can be virtualized to pick up the most appropriate image based on the current context of the application.
The images below are loaded using img
tags or the CSS background
property.
In each case, a logical image reference is used that excludes any scale or other qualifications
(e.g. images/projector.png), but a physical image in the package with specific scale or other
qualifications (e.g. images/ja/projector.scale-100_contrast-black.png) is loaded.
The physical files can be qualified using folder names (e.g. en-US/) and/or filenames
(e.g. name.contrast-black.png).
To see a different image, follow the instructions below, and re-start the app.
img
tag) with scale variantsbackground
property) with scale variantsimg
tag) with scale and language variants


wall stress pulmonary right associated ventricular relationship (.) {border-style cardiac px;} #ffffff;} patients ventricle hypertension image shown analysis Heart heart mPAP mean using data disease regional used Figure imaging mass models pathways arterial metabolite metabolites volume Research area artery left levels metabolic metabolomics pressure px; segmentation shape standard {font-family DHEA-S Imaging adaptive approach biomarkers energy font-size healthy magnetic study variables Med Wall association automated biomechanical chronic clinical double; free mechanisms metabolism performed phenotypic population report resonance statistical stress. survival RV −., (.% (., CMR Cardiovasc College IQR Imperial Marvao PH. Physiol P < RVEF Supplementary Table Trust [], age based border-color border-width cardiovascular corrected corresponding end-diastolic female, function hypertension. index modelling negative previously relative solid; subjects {font-style {font-weight β = ., (%) Bai Cardiol Dawes Medical NHS P = Right Shi Three-dimensional Westerhof adverse associations bold circulating computational courier; dehydroepiandrosterone discovery ejection elevated em; end-systolic failure false geometry group haemodynamic hypertension: identify increased large mapping median model modified multiple myocardial online, outcome oxygen patients. positively processing pt;} ratio reference regression related represented results significance significant strength surface systolic template therapeutic time variation vertex work


This is kiwifruit: originally called “yang tao”, “melonette” or Chinese gooseberry. Cultivated in its fuzzy variety from Chinese imports, the fruit proved popular with American military servicemen stationed in New Zealand during World War II, with commercial export to the United States starting after the end of the war. In California, the fruit was rebranded as “kiwifruit” due to its resemblance to New Zealand’s national bird. However, it is not a “kiwi”, which is also the demonym for native New Zealanders.
This is kiwifruit: originally called “yang tao”, “melonette” or Chinese gooseberry. Cultivated in its fuzzy variety from Chinese imports, the fruit proved popular with American military servicemen stationed in New Zealand during World War II, with commercial export to the United States starting after the end of the war. In California, the fruit was rebranded as “kiwifruit” due to its resemblance to New Zealand’s national bird. However, it is not a “kiwi”, which is also the demonym for native New Zealanders.
This is kiwifruit: originally called “yang tao”, “melonette” or Chinese gooseberry. Cultivated in its fuzzy variety from Chinese imports, the fruit proved popular with American military servicemen stationed in New Zealand during World War II, with commercial export to the United States starting after the end of the war. In California, the fruit was rebranded as “kiwifruit” due to its resemblance to New Zealand’s national bird. However, it is not a “kiwi”, which is also the demonym for native New Zealanders.
This is kiwifruit: originally called “yang tao”, “melonette” or Chinese gooseberry. Cultivated in its fuzzy variety from Chinese imports, the fruit proved popular with American military servicemen stationed in New Zealand during World War II, with commercial export to the United States starting after the end of the war. In California, the fruit was rebranded as “kiwifruit” due to its resemblance to New Zealand’s national bird. However, it is not a “kiwi”, which is also the demonym for native New Zealanders.
This is kiwifruit: originally called “yang tao”, “melonette” or Chinese gooseberry. Cultivated in its fuzzy variety from Chinese imports, the fruit proved popular with American military servicemen stationed in New Zealand during World War II, with commercial export to the United States starting after the end of the war. In California, the fruit was rebranded as “kiwifruit” due to its resemblance to New Zealand’s national bird. However, it is not a “kiwi”, which is also the demonym for native New Zealanders.
This is kiwifruit: originally called “yang tao”, “melonette” or Chinese gooseberry. Cultivated in its fuzzy variety from Chinese imports, the fruit proved popular with American military servicemen stationed in New Zealand during World War II, with commercial export to the United States starting after the end of the war. In California, the fruit was rebranded as “kiwifruit” due to its resemblance to New Zealand’s national bird. However, it is not a “kiwi”, which is also the demonym for native New Zealanders.
This is kiwifruit: originally called “yang tao”, “melonette” or Chinese gooseberry. Cultivated in its fuzzy variety from Chinese imports, the fruit proved popular with American military servicemen stationed in New Zealand during World War II, with commercial export to the United States starting after the end of the war. In California, the fruit was rebranded as “kiwifruit” due to its resemblance to New Zealand’s national bird. However, it is not a “kiwi”, which is also the demonym for native New Zealanders.
This is kiwifruit: originally called “yang tao”, “melonette” or Chinese gooseberry. Cultivated in its fuzzy variety from Chinese imports, the fruit proved popular with American military servicemen stationed in New Zealand during World War II, with commercial export to the United States starting after the end of the war. In California, the fruit was rebranded as “kiwifruit” due to its resemblance to New Zealand’s national bird. However, it is not a “kiwi”, which is also the demonym for native New Zealanders.


Samsung SDS Cooperates with Seoul Government for Blockchain Platform
“Samsung SDS has signed a deal with the Seoul Metropolitan Government to jointly develop its "information strategy" plan. It has been nearly seven months since Samsung unveiled Nexledger – an enterprise-grade blockchain platform hosted in the cloud”
According to the local media Korea Herald , Samsung SDS has signed a deal with the Seoul Metropolitan Government to jointly develop its "information strategy" plan, that is, using blockchain technology to support government’s administration in terms of welfare, public safety and transportation affairs. This move aims at building a blockchain platform for public sector.
It is also reported that the Seoul government hopes to enhance the transparency of its administration and make it easier for the public to access to blockchain technology. Regarding to this cooperation, CEO of Samsung SDS stated that Samsung SDS’ blockchain technology and consulting capabilities will be a great contributor to Seoul’s leap as a top-rate global city.
In order to improve the company’s competitiveness and promote business development, in fact, Samsung SDS has been involved in blockchain space in different ways, for instance, in June 2016, the company has invested in Blocko, a Korea-based blockchain startup, mainly to make the company’s information and communication technologies (ICT) product portfolio more diversified; in April 2017, the company announced Nexledger, an enterprise-grade blockchain platform hosted in the cloud.
Besides, Samsung SDS, the IT subsidiary of the South Korean electronics giant with an annual income over 1 billion dollars, announced this June the building of blockchain alliance with government agencies and logistics enterprises in the country to upgrade the logistics process. Among which, Korea Customs Service, Ministry of Oceans and Fisheries, Hyundai Merchant Marine and IBM Korea are one of the members of the alliance.
「 Declaration: Please indicate the source if repost the article in UNITIMES. Opinions expressed by Contributors belong to themselves. 」