|
FreeRTOS port on GAP8/RISC-V
|
Macros | |
| #define | FLL_NUM |
| #define | FLL_REF_CLK |
| #define | FLL_CTRL_BASE |
| #define | FLL_CTRL |
| #define | FLL_CTRL_BASE_ADDRS |
| #define | FLL_CTRL_BASE_PTRS |
FLL_STATUS - FLL_CTRL status register | |
| #define | FLL_CTRL_STATUS_MULTI_FACTOR_MASK |
| #define | FLL_CTRL_STATUS_MULTI_FACTOR_SHIFT |
| #define | FLL_CTRL_STATUS_MULTI_FACTOR(x) |
| #define | READ_FLL_CTRL_STATUS_MULTI_FACTOR(x) |
SOC_CONF1 - FLL_CTRL configuration 1 register | |
| #define | FLL_CTRL_CONF1_MULTI_FACTOR_MASK |
| #define | FLL_CTRL_CONF1_MULTI_FACTOR_SHIFT |
| #define | FLL_CTRL_CONF1_MULTI_FACTOR(x) |
| #define | READ_FLL_CTRL_CONF1_MULTI_FACTOR(x) |
| #define | FLL_CTRL_CONF1_DCO_INPUT_MASK |
| #define | FLL_CTRL_CONF1_DCO_INPUT_SHIFT |
| #define | FLL_CTRL_CONF1_DCO_INPUT(x) |
| #define | READ_FLL_CTRL_CONF1_DCO_INPUT(x) |
| #define | FLL_CTRL_CONF1_CLK_OUT_DIV_MASK |
| #define | FLL_CTRL_CONF1_CLK_OUT_DIV_SHIFT |
| #define | FLL_CTRL_CONF1_CLK_OUT_DIV(x) |
| #define | READ_FLL_CTRL_CONF1_CLK_OUT_DIV(x) |
| #define | FLL_CTRL_CONF1_OUTPUT_LOCK_EN_MASK |
| #define | FLL_CTRL_CONF1_OUTPUT_LOCK_EN_SHIFT |
| #define | FLL_CTRL_CONF1_OUTPUT_LOCK_EN(x) |
| #define | READ_FLL_CTRL_CONF1_OUTPUT_LOCK_EN(x) |
| #define | FLL_CTRL_CONF1_MODE_MASK |
| #define | FLL_CTRL_CONF1_MODE_SHIFT |
| #define | FLL_CTRL_CONF1_MODE(x) |
| #define | READ_FLL_CTRL_CONF1_MODE(x) |
SOC_INTEGRATOR - FLL_CTRL configuration 2 register | |
| #define | FLL_CTRL_INTEGRATOR_FRACT_PART_MASK |
| #define | FLL_CTRL_INTEGRATOR_FRACT_PART_SHIFT |
| #define | FLL_CTRL_INTEGRATOR_FRACT_PART(x) |
| #define | READ_FLL_CTRL_INTEGRATOR_FRACT_PART(x) |
| #define | FLL_CTRL_INTEGRATOR_INT_PART_MASK |
| #define | FLL_CTRL_INTEGRATOR_INT_PART_SHIFT |
| #define | FLL_CTRL_INTEGRATOR_INT_PART(x) |
| #define | READ_FLL_CTRL_INTEGRATOR_INT_PART(x) |
FLL_CONVERGE - FLL_CTRL configuration 2 register | |
| #define | FLL_CTRL_SOC_FLL_CONV_MASK |
| #define | FLL_CTRL_SOC_FLL_CONV_SHIFT |
| #define | FLL_CTRL_SOC_FLL_CONV(x) |
| #define | READ_FLL_CTRL_SOC_FLL_CONV(x) |
| #define | FLL_CTRL_CLUSTER_FLL_CONV_MASK |
| #define | FLL_CTRL_CLUSTER_FLL_CONV_SHIFT |
| #define | FLL_CTRL_CLUSTER_FLL_CONV(x) |
| #define | READ_FLL_CTRL_CLUSTER_FLL_CONV(x) |
| #define FLL_CTRL |
Peripheral FLL_CTRL base pointer
Referenced by pi_fll_get_frequency(), pi_fll_init(), and pi_fll_set_frequency().
| #define FLL_CTRL_BASE |
Peripheral FLL_CTRL base address
| #define FLL_CTRL_BASE_ADDRS |
Array initializer of FLL_CTRL base addresses
| #define FLL_CTRL_BASE_PTRS |
Array initializer of FLL_CTRL base pointers
| #define FLL_CTRL_CLUSTER_FLL_CONV | ( | x | ) |
| #define FLL_CTRL_CLUSTER_FLL_CONV_MASK |
| #define FLL_CTRL_CLUSTER_FLL_CONV_SHIFT |
| #define FLL_CTRL_CONF1_CLK_OUT_DIV | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF1_CLK_OUT_DIV_MASK |
| #define FLL_CTRL_CONF1_CLK_OUT_DIV_SHIFT |
| #define FLL_CTRL_CONF1_DCO_INPUT | ( | x | ) |
| #define FLL_CTRL_CONF1_DCO_INPUT_MASK |
| #define FLL_CTRL_CONF1_DCO_INPUT_SHIFT |
| #define FLL_CTRL_CONF1_MODE | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF1_MODE_MASK |
| #define FLL_CTRL_CONF1_MODE_SHIFT |
| #define FLL_CTRL_CONF1_MULTI_FACTOR | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF1_MULTI_FACTOR_MASK |
| #define FLL_CTRL_CONF1_MULTI_FACTOR_SHIFT |
| #define FLL_CTRL_CONF1_OUTPUT_LOCK_EN | ( | x | ) |
| #define FLL_CTRL_CONF1_OUTPUT_LOCK_EN_MASK |
| #define FLL_CTRL_CONF1_OUTPUT_LOCK_EN_SHIFT |
| #define FLL_CTRL_CONF2_ASSERT_CYCLES | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF2_ASSERT_CYCLES_MASK |
| #define FLL_CTRL_CONF2_ASSERT_CYCLES_SHIFT |
| #define FLL_CTRL_CONF2_CONF_CLK_SEL | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF2_CONF_CLK_SEL_MASK |
| #define FLL_CTRL_CONF2_CONF_CLK_SEL_SHIFT |
| #define FLL_CTRL_CONF2_DEASSERT_CYCLES | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF2_DEASSERT_CYCLES_MASK |
| #define FLL_CTRL_CONF2_DEASSERT_CYCLES_SHIFT |
| #define FLL_CTRL_CONF2_DITHERING | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF2_DITHERING_MASK |
| #define FLL_CTRL_CONF2_DITHERING_SHIFT |
| #define FLL_CTRL_CONF2_LOCK_TOLERANCE | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF2_LOCK_TOLERANCE_MASK |
| #define FLL_CTRL_CONF2_LOCK_TOLERANCE_SHIFT |
| #define FLL_CTRL_CONF2_LOOPGAIN | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF2_LOOPGAIN_MASK |
| #define FLL_CTRL_CONF2_LOOPGAIN_SHIF |
| #define FLL_CTRL_CONF2_OPEN_LOOP | ( | x | ) |
Referenced by pi_fll_set_frequency().
| #define FLL_CTRL_CONF2_OPEN_LOOP_MASK |
| #define FLL_CTRL_CONF2_OPEN_LOOP_SHIFT |
| #define FLL_CTRL_INTEGRATOR_FRACT_PART | ( | x | ) |
| #define FLL_CTRL_INTEGRATOR_FRACT_PART_MASK |
| #define FLL_CTRL_INTEGRATOR_FRACT_PART_SHIFT |
| #define FLL_CTRL_INTEGRATOR_INT_PART | ( | x | ) |
Referenced by pi_fll_init().
| #define FLL_CTRL_INTEGRATOR_INT_PART_MASK |
| #define FLL_CTRL_INTEGRATOR_INT_PART_SHIFT |
| #define FLL_CTRL_SOC_FLL_CONV | ( | x | ) |
| #define FLL_CTRL_SOC_FLL_CONV_MASK |
| #define FLL_CTRL_SOC_FLL_CONV_SHIFT |
| #define FLL_CTRL_STATUS_MULTI_FACTOR | ( | x | ) |
| #define FLL_CTRL_STATUS_MULTI_FACTOR_MASK |
| #define FLL_CTRL_STATUS_MULTI_FACTOR_SHIFT |
| #define FLL_NUM |
Referenced by FLL_Clear().
| #define FLL_REF_CLK |
Referenced by fll_get_frequency_from_mult_div(), and fll_get_mult_div_from_frequency().
| #define READ_FLL_CTRL_CLUSTER_FLL_CONV | ( | x | ) |
| #define READ_FLL_CTRL_CONF1_CLK_OUT_DIV | ( | x | ) |
Referenced by pi_fll_get_frequency().
| #define READ_FLL_CTRL_CONF1_DCO_INPUT | ( | x | ) |
| #define READ_FLL_CTRL_CONF1_MODE | ( | x | ) |
Referenced by pi_fll_init().
| #define READ_FLL_CTRL_CONF1_MULTI_FACTOR | ( | x | ) |
| #define READ_FLL_CTRL_CONF1_OUTPUT_LOCK_EN | ( | x | ) |
| #define READ_FLL_CTRL_CONF2_ASSERT_CYCLES | ( | x | ) |
| #define READ_FLL_CTRL_CONF2_CONF_CLK_SEL | ( | x | ) |
| #define READ_FLL_CTRL_CONF2_DEASSERT_CYCLES | ( | x | ) |
| #define READ_FLL_CTRL_CONF2_DITHERING | ( | x | ) |
| #define READ_FLL_CTRL_CONF2_LOCK_TOLERANCE | ( | x | ) |
| #define READ_FLL_CTRL_CONF2_LOOPGAIN | ( | x | ) |
| #define READ_FLL_CTRL_CONF2_OPEN_LOOP | ( | x | ) |
| #define READ_FLL_CTRL_INTEGRATOR_FRACT_PART | ( | x | ) |
| #define READ_FLL_CTRL_INTEGRATOR_INT_PART | ( | x | ) |
| #define READ_FLL_CTRL_SOC_FLL_CONV | ( | x | ) |
| #define READ_FLL_CTRL_STATUS_MULTI_FACTOR | ( | x | ) |


Researcher Lorain:
What? Misunderstanding?
What is that old man talking about? That's absurd...
But he said he would help us, eh? It's certainly not like him to lend us his precious map.
I'm still angry at him, but now I have to admit I'm curious enough about his motives to talk to him again...
In any case, show me the map! I want to study it to see exactly where we should search.
Give her the map.


- java2DToValue(double, Rectangle2D, RectangleEdge) - Method in class org.jfree.chart.axis.CyclicNumberAxis
-
Converts a coordinate from Java 2D space to data space.
- java2DToValue(double, Rectangle2D, RectangleEdge) - Method in class org.jfree.chart.axis.DateAxis
-
Translates a Java2D coordinate into the corresponding data value.
- java2DToValue(double, Rectangle2D, RectangleEdge) - Method in class org.jfree.chart.axis.LogarithmicAxis
-
Converts a coordinate in Java2D space to the corresponding data
value, assuming that the axis runs along one edge of the specified
plotArea.
- java2DToValue(double, Rectangle2D, RectangleEdge) - Method in class org.jfree.chart.axis.LogAxis
-
Converts a Java2D coordinate to an axis value, assuming that the
axis is aligned to the specified edge
of the area
.
- java2DToValue(double, Rectangle2D, RectangleEdge) - Method in class org.jfree.chart.axis.ModuloAxis
-
Translates a Java2D coordinate into a data value.
- java2DToValue(double, Rectangle2D, RectangleEdge) - Method in class org.jfree.chart.axis.NumberAxis
-
Converts a coordinate in Java2D space to the corresponding data value,
assuming that the axis runs along one edge of the specified dataArea.
- java2DToValue(double, Rectangle2D, RectangleEdge) - Method in class org.jfree.chart.axis.PeriodAxis
-
Converts a coordinate in Java2D space to the corresponding data value,
assuming that the axis runs along one edge of the specified dataArea.
- java2DToValue(double, Rectangle2D, RectangleEdge) - Method in class org.jfree.chart.axis.ValueAxis
-
Converts a coordinate in Java2D space to the corresponding data value,
assuming that the axis runs along one edge of the specified dataArea.
- javascriptEscape(String) - Static method in class org.jfree.chart.imagemap.ImageMapUtilities
-
Returns a string that is equivalent to the input string, but with
special characters converted to JavaScript escape sequences.
- JDBCCategoryDataset - Class in org.jfree.data.jdbc
-
- JDBCCategoryDataset(String, String, String, String) - Constructor for class org.jfree.data.jdbc.JDBCCategoryDataset
-
Creates a new dataset with a database connection.
- JDBCCategoryDataset(Connection) - Constructor for class org.jfree.data.jdbc.JDBCCategoryDataset
-
Create a new dataset with the given database connection.
- JDBCCategoryDataset(Connection, String) - Constructor for class org.jfree.data.jdbc.JDBCCategoryDataset
-
Creates a new dataset with the given database connection, and executes
the supplied query to populate the dataset.
- JDBCPieDataset - Class in org.jfree.data.jdbc
-
A
PieDataset
that reads data from a database via JDBC.
- JDBCPieDataset(String, String, String, String) - Constructor for class org.jfree.data.jdbc.JDBCPieDataset
-
Creates a new JDBCPieDataset and establishes a new database connection.
- JDBCPieDataset(Connection) - Constructor for class org.jfree.data.jdbc.JDBCPieDataset
-
Creates a new JDBCPieDataset using a pre-existing database connection.
- JDBCPieDataset(Connection, String) - Constructor for class org.jfree.data.jdbc.JDBCPieDataset
-
Creates a new JDBCPieDataset using a pre-existing database connection.
- JDBCXYDataset - Class in org.jfree.data.jdbc
-
This class provides an
XYDataset
implementation over a database
JDBC result set.
- JDBCXYDataset(String, String, String, String) - Constructor for class org.jfree.data.jdbc.JDBCXYDataset
-
Creates a new dataset (initially empty) and establishes a new database
connection.
- JDBCXYDataset(Connection) - Constructor for class org.jfree.data.jdbc.JDBCXYDataset
-
Creates a new dataset (initially empty) using the specified database
connection.
- JDBCXYDataset(Connection, String) - Constructor for class org.jfree.data.jdbc.JDBCXYDataset
-
Creates a new dataset using the specified database connection, and
populates it using data obtained with the supplied query.
- JFreeChart - Class in org.jfree.chart
-
A chart class implemented using the Java 2D APIs.
- JFreeChart(Plot) - Constructor for class org.jfree.chart.JFreeChart
-
Creates a new chart based on the supplied plot.
- JFreeChart(String, Plot) - Constructor for class org.jfree.chart.JFreeChart
-
Creates a new chart with the given title and plot.
- JFreeChart(String, Font, Plot, boolean) - Constructor for class org.jfree.chart.JFreeChart
-
Creates a new chart with the given title and plot.
- JFreeChartEntity - Class in org.jfree.chart.entity
-
A class that captures information about an entire chart.
- JFreeChartEntity(Shape, JFreeChart) - Constructor for class org.jfree.chart.entity.JFreeChartEntity
-
Creates a new chart entity.
- JFreeChartEntity(Shape, JFreeChart, String) - Constructor for class org.jfree.chart.entity.JFreeChartEntity
-
Creates a new chart entity.
- JFreeChartEntity(Shape, JFreeChart, String, String) - Constructor for class org.jfree.chart.entity.JFreeChartEntity
-
Creates a new chart entity.
- JFreeChartResources - Class in org.jfree.chart.resources
-
Localised resources for JFreeChart.
- JFreeChartResources() - Constructor for class org.jfree.chart.resources.JFreeChartResources
-
- JPEG - Static variable in interface org.jfree.chart.encoders.ImageFormat
-
Joint Photographic Experts Group format - lossy
- JThermometer - Class in org.jfree.chart.plot
-
An initial quick and dirty.
- JThermometer() - Constructor for class org.jfree.chart.plot.JThermometer
-
Default constructor.


The pharmacokinetics of ziprasidone in healthy volunteers treated with cimetidine or antacid
Abstract
Aims
To evaluate the effects of cimetidine and Maalox® (aluminium hydroxide 1.35 g and magnesium hydroxide 1.2 g) on the pharmacokinetics of ziprasidone.
Methods
Eleven healthy young subjects aged 18–45 years were given single oral doses of ziprasidone 40 mg on three occasions at least 7 days apart. On one occasion ziprasidone was administered alone, on another occasion ziprasidone was co-administered with oral cimetidine 800 mg and on a third occasion ziprasidone was co-administered with oral Maalox®.
Results
The administration of cimetidine increased the ziprasidone AUC(0, ∞) by 6% but there were no statistically significant differences in Cmax, tmax or λz between the ziprasidone + cimetidine group and the ziprasidone group. The administration of Maalox® did not produce any statistically significant differences in AUC(0, ∞), Cmax, tmax or λz between the ziprasidone + Maalox® group and the ziprasidone group.
Conclusions
The pharmacokinetics of ziprasidone are not affected by concurrent administration of cimetidine or Maalox®. This suggests that other nonspecific inhibitors of cytochrome P450 and antacids are unlikely to alter the pharmacokinetics of ziprasidone.
Introduction
Ziprasidone has a pharmacokinetic profile unaffected by age and gender [1]. It is extensively metabolized to inactive derivatives in humans, and in vitro studies using human liver microsomes have shown that the oxidative metabolism of ziprasidone is primarily mediated by the 3A4 isoform of cytochrome P450 (CYP3A4) [2]. The absorption of orally administered ziprasidone is enhanced when it is taken immediately after eating, perhaps as a consequence of improved drug solubilization in the presence of food [3].
Cimetidine is an H2 receptor antagonist which is commonly used to treat duodenal ulcers, benign gastric ulcers and hypersecretory states. It inhibits several isoforms of cytochrome P450, including CYP3A4 [4]. This inhibition can result in alterations in the elimination of co-administered drugs which are also oxidatively metabolized by CYP3A4. In addition, cimetidine can alter gastric pH and therefore has the potential to affect the absorption of co-administered drugs.
Antacids are commonly used in the symptomatic relief of dyspeptic symptoms and, usually in combination with H2 receptor antagonists, in the treatment of duodenal ulcers. As they function by raising gastric pH, they have the potential to affect the absorption of co-administered drugs. Furthermore, they can influence the pharmacokinetics of co-administered drugs through absorption or chelation.
This study was designed to determine whether or not multiple-dose cimetidine or antacid administration alters the pharmacokinetics of ziprasidone.
Methods
Subjects
The subjects were healthy, young (18–45 years) adults of either gender. All subjects weighed ≤91 kg and were within 10% of their ideal body weight for age, height, sex and frame [5]. None was pregnant or lactating and none was a smoker. All subjects provided written informed consent.
Protocol
This was an open-label, randomized, three-way crossover study designed to determine whether multiple doses of cimetidine and Maalox® alter the pharmacokinetics of ziprasidone. The study protocol was approved by an independent institutional review board.
The study comprised three 1 day treatment periods separated by intervals of at least 7 days. During each treatment period each subject received one of three different treatments in one of six sequences according to a computer-generated randomization. These three treatments were: ziprasidone 40 mg alone; ziprasidone 40 mg + cimetidine 800 mg; and ziprasidone 40 mg + Maalox® 30 ml (aluminium hydroxide 1.35 g and magnesium hydroxide 1.2 g).
Ziprasidone hydrochloride capsules were administered orally, after a standard breakfast at approximately 09.00 h. Cimetidine tablets were administered once daily, at approximately 07.00h, commencing 2 days before ziprasidone administration and continuing until 1 day after ziprasidone dosing. Maalox® suspension was administered on the evening before the administration of ziprasidone (approximately 23.00 h), immediately before the ziprasidone dosing (approximately 09.00 h), and after lunch (approximately 13.00 h) and dinner (approximately 18.00 h) on the day that ziprasidone was taken.
Pharmacokinetic sampling
Blood samples for the determination of serum ziprasidone concentrations were collected immediately before dosing and at fixed intervals up to 36 h after each dose of ziprasidone.
Pharmacokinetic analysis
Serum concentrations of ziprasidone were determined using high performance liquid chromatography involving solid-phase extraction and u.v. detection. The assay had a dynamic range of 1.0–250.0 ng ml−1[6]. Ziprasidone concentrations below the lower limit of quantification were assigned a value of 0 ng ml−1 in pharmacokinetic calculations.
The maximum serum concentration of ziprasidone (Cmax) and the earliest time at which Cmax occurred (tmax) were estimated directly from the experimental data. The terminal elimination rate constant for ziprasidone (λz) was estimated using least-squares regression analysis of the ziprasidone concentration–time data obtained during the terminal log-linear phase. The terminal half-life of ziprasidone (t½,z) was calculated as ln 2/λz, and the mean half-life of ziprasidone was estimated as ln 2/mean λz. The area under the serum concentration–time curve from time zero to the last time (t) serum ziprasidone was measurable (AUC(0, t)) was estimated by the linear trapezoidal approximation. The area under the serum concentration–time curve from the time t to infinity (AUC(t, ∞)) was calculated as Cpest/λz, where Cpest is the estimated concentration at the last time serum ziprasidone was measurable based on the regression analysis of the terminal log-linear phase. The total area under the serum concentration–time curve (AUC(0, ∞)) was estimated as the sum of the AUC(0, t) and AUC(t, ∞) values.
Statistical analysis
Natural log-transformed AUC(0, ∞) and Cmax values, and untransformed tmax and λz values, were analysed in a two-way analysis of variance (anova) model containing sequence, subject within sequence, period and treatment effects (PROC GLM of SAS®). The sequence effect was tested using the subject within sequence mean square as the error term and the period effect was tested using the within subject mean square error as the error term.
Geometric means and standard deviations were calculated for AUC(0, ∞) and Cmax. Arithmetic means and standard deviations were calculated for tmax and λz. Adjusted means, and their variances and covariances, were then calculated using the least-squares means statement from SAS®. These were then used to estimate the difference between the treatment effects.
Student’s t-tests with 95% confidence limits were used to examine pair-wise differences between the groups. Values of P< 0.05 were considered to be statistically significant.
Results
Subjects
Twelve subjects entered the study (Table 1). Ten completed all three treatment periods and were included in the pharmacokinetic analysis (n = 10 for all three treatment periods).
One subject discontinued the study after experiencing adverse events and only completed the ziprasidone treatment period. Another subject discontinued the study for personal reasons after completing the ziprasidone + Maalox® and ziprasidone + cimetidine treatment periods.
Pharmacokinetics
The mean serum ziprasidone concentration–time curves for the three treatment groups were broadly similar, but suggested a small but not statistically significant delay in the occurrence of Cmax in the ziprasidone + Maalox® group compared with the ziprasidone alone group (mean ratio 108.4%; 95% CI: 82.8,134) (Figure 1).
The pharmacokinetic parameters for ziprasidone across the three treatment groups were generally similar (Table 2). Individual AUC(0, ∞) and Cmax values are shown in Figures 2 and and3.3. The only statistically significant difference between the treatment groups, for any of the pharmacokinetic parameters, occurred in the comparison of mean AUC(0, ∞) values in the ziprasidone + cimetidine group with the ziprasidone alone group. This parameter was 6.2% greater in the ziprasidone + cimetidine group than in the ziprasidone alone group (95% CI: 100.6,113.5). None of the differences in Cmax, tmaxand λz between the ziprasidone + cimetidine group and the ziprasidone alone group was statistically significant. The t½,z of ziprasidone in the ziprasidone + cimetidine group was 3.1% longer than that in the ziprasidone alone group.
The mean AUC(0,∞), Cmax, tmax and λz values in the ziprasidone + Maalox® group were not significantly different from those in the ziprasidone alone group. The t½,z of ziprasidone in the ziprasidone + Maalox® group was almost identical to that in the group receiving ziprasidone alone.
Discussion
Findings from this study indicate that concomitant administration of cimetidine produces a small increase in systemic exposure to ziprasidone as measured by the AUC(0,∞). Although this increase was statistically significant, it was small (6%) and is not considered to be clinically meaningful. None of the other pharmacokinetic parameters that were measured showed any statistically or clinically significant differences between the ziprasidone + cimetidine and ziprasidone alone groups. Similarly, no statistically significant differences between the ziprasidone + Maalox® and ziprasidone alone groups were observed for any of the measured pharmacokinetic parameters. The delay in reaching Cmax is unlikely to be of clinical relevance.
The lack of clinically significant effects of cimetidine on the pharmacokinetics of ziprasidone was observed despite the fact that oxidative ziprasidone metabolism is primarily mediated by CYP3A4 [2]. As cimetidine is known to be a non-specific inhibitor of CYP3A4 [4], the findings of this study suggest that ziprasidone could also be metabolized via alternative pathways. In view of the in vitro activity of ziprasidone for the inhibition of CYP3A4 [4], however, a single dose of ziprasidone would seem unlikely to inhibit this isoenzyme substantially in vivo. Nevertheless, the modest increase in the AUC(0,∞) is in accord with this hypothesis. Alternatively, ziprasidone may be excreted unchanged to a greater degree than normal in the presence of cimetidine.
In conclusion, the findings of this study indicate that the administration of multiple doses of cimetidine or of Maalox® do not exert any clinically significant influence on the single-dose pharmacokinetics of ziprasidone 40 mg.
References
Formats:
- Article
- |
- PubReader
- |
- ePub (beta)
- |
- PDF (108K)
- |
- Citation


Function
| Static Public Summary | ||
| public |
accessDeep(path: array, obj: object): null | any Safely access deeply nested values in an object. |
|
| public |
arrayChunks(arr: array, len: number): array Group an array's values into subgroups. |
|
| public |
Quickly call a function or fail gracefully if it does not exist. |
|
| public |
The mapObj() method creates a new array with the results of calling a provided function on every element in the calling object. |
|
| public |
Deeply nest and set a value in an object. |
Static Public
public accessDeep(path: array, obj: object): null | any source
import {accessDeep} from 'project-helpers/js/object-helpers.js'
Safely access deeply nested values in an object. If the path to the value is not valid, the method will gracefully return null.
Params:
| Name | Type | Attribute | Description |
| path | array | the array representation of the path to access. |
|
| obj | object | the object who's value you are trying to access. |
Return:
| null | any | will return null on path not found, or the value found. |
public arrayChunks(arr: array, len: number): array source
import {arrayChunks} from 'project-helpers/js/object-helpers.js'
Group an array's values into subgroups.
Params:
| Name | Type | Attribute | Description |
| arr | array | The target array. |
|
| len | number | The length of the chunks. |
Return:
| array | A two-dimensional segmented array. |
public ifFunc(func: function, args: args): any source
import {ifFunc} from 'project-helpers/js/object-helpers.js'
Quickly call a function or fail gracefully if it does not exist.
Params:
| Name | Type | Attribute | Description |
| func | function | The function to try to call. |
|
| args | args | The would-be arguments of the function. |
Return:
| any | returns whatever the function returns. |
public mapObj(obj: object, callback: function): array source
import {mapObj} from 'project-helpers/js/object-helpers.js'
The mapObj() method creates a new array with the results of calling a provided function on every element in the calling object.
Return:
| array | returns an array with the values of each returned value in the callback. |
public setDeep(obj: object, path: array | string , value: any, setRecursively: boolean): object source
import {setDeep} from 'project-helpers/js/object-helpers.js'
Deeply nest and set a value in an object.


Heroin valued at €195,000 found at derelict property in Limerick
Discovery was made at a building in the Ardkilmartin area of Kilmallock
by Sarah BurnsHeroin worth €195,000 has been seized during a search of a derelict property in Co Limerick.
The discovery was made at a property in the Ardkilmartin area of Kilmallock by gardaí from Bruff assisted by members of the regional Garda dog unit.
The drugs have been removed for technical examination.
No arrests have been made and gardaí said their investigations are continuing.
Anyone who may have information in relation to the seizure is asked to contact Bruff Garda station on 061 382940 or the Garda Confidential Line on 1800 666 111.


APC awaits Buhari’s approval for NEC meeting
by Kamarudeen OgundeleKamarudeen Ogundele, Abuja
The proposed National Executive Council meeting of the All Progressives Congress earlier slated for Friday is still uncertain as President Muhammadu Buhari’s has yet to give his consent.
But the national caucus meeting will still hold on Thursday as proposed, our correspondent gathered on Monday night.
According to Article 12.5 of the APC constitution, members of the national caucus include 10 members of the National Working Committee, past and present presidents and vice-presidents, current presidential and vice-presidential candidates of the party as well as the Secretary to the Government of the Federation.
Others are the past and present Senate presidents and their deputies, and past and present speakers of the House of Representatives and their deputies, among others.
A member of the NWC, who spoke in confidence with our correspondent after their meeting in Abuja on Monday, said the committee reviewed the governorship elections in Kogi and Bayelsa states and commended the leadership of the party.
“We reviewed the progress made so far in our electoral fortunes and gave ourselves a pass mark but not without noting some areas that we need to improve in future elections. We did our best and the result is there for everyone to see.”
Asked if the NWC set agenda for the NEC meeting, he said that would only come up at the national caucus meeting where such issues would be addressed.
Another source, however, told our correspondent that the NWC would at the caucus meeting present financial books of the party to stakeholders for review before presentation at the NEC meeting.
“We are also going to set agenda for the NEC meeting at the national caucus meeting. That will serve as the preparatory ground,” the source added.
The APC National Publicity Secretary, Lanre Issa-Onilu, refused to comment on the outcome of the NWC meeting on Monday.
“Yes, we met but the issues are not for public consumption,” he simply said.
He, however, confirmed that the national caucus meeting would hold on Thursday while the NEC meeting “is tentative” without giving reasons.
But a source within the top hierarchy said the NEC meeting was still in doubt because the President’s consent had not been sought.
“The President just returned from abroad; so the leadership of the party needs to meet him and know his schedules to know the time that will be most convenient for him. It is an important meeting that the president and vice-president have to be in attendance since it is the first in a while,” the source added.
Copyright PUNCH.
All rights reserved. This material, and other digital content on this website, may not be reproduced, published, broadcast, rewritten or redistributed in whole or in part without prior express written permission from PUNCH.
Contact: theeditor@punchng.com


TWELFTH SESSION OF THE SUBSIDIARY BODIES OF THE UNFCCC
13-Jun-00 — original report
IPCC Chair Robert Watson outlined the key issues in the IPCC Special Report on LULUCF.
Co-Chair Gwage noted the capacity building function of the pre-sessional informal meetings with regard to the LULUCF Special Report and progress on the data format for submissions due on 1 August. Several delegates called for sufficient time to consider the Special Report.
The G-77/CHINA expressed concern that the 'sink' in Annex I countries would create an entitlement to emit, and called for appropriate carbon accounting approaches.
COLOMBIA, opposed by SAMOA, supported equal treatment of forestry in the CDM.
The AFRICA GROUP underscored links between land degradation and sequestration. AUSTRALIA and CANADA suggested dealing with Article 3.3 (afforestation, reforestation and deforestation) and 3.4 (additional activities) as a package.
SWITZERLAND preferred prioritizing Article 3.3, while the EU stressed emissions reduction as the main emphasis when considering Article 3.4.
Co-Chair Slade of the Joint Working Group on Compliance (JWG) reported on the workshop held from 1-3 March 2000 and the informal meetings preceding SB-12.
He said that these, together with further submissions from Parties, formed the basis for the negotiating text for SB- 12.
Chair Chow reported on progress made during the inter-sessional period and introduced relevant documents, including the draft consolidated text on mechanisms.
A number of delegates said the new consolidated text formed a useful basis or reference point from which to proceed.
The G-77/CHINA stressed the need to include rather than exclude views, and to determine the nature of the process and terms of reference for the contact group on mechanisms in the lead-up to COP-6. COLOMBIA said the CDM should: ensure sufficient additionality; provide for equal treatment between the three mechanisms; recognize the unilateral model for the formulation of projects; and focus on prioritizing the sustainable development aspect of CDM.
ROMANIA, speaking for the Group of Eastern European countries, and supported by the US, said JI and CDM have distinct roles and should not be treated in the same way.
AUSTRALIA cautioned against loading JI and CDM with transaction costs.
CHILE supported inclusion of sinks within the CDM.
Delegates considered the Co-Chairs' note on draft conclusions for SBSTA-12 relating to criteria and guiding principles for identification and selection of additional activities under Article 3.4.
The EU called for inclusion of further criteria and a guiding principle emphasizing emissions reduction.
AUSTRALIA disagreed, stressing the importance of not being prescriptive, but allowing for consideration of national circumstances.
TUVALU and the G-77/CHINA proposed deleting reference to sustainable development and to multilateral environmental agreements.
Some Parties suggested referring to specific articles, but proceeded to agree on a general reference to the FCCC and the Protocol.
Co-Chair Kjellén emphasized that the goal of the contact group was to develop a proposal for negotiating text for consideration at SBSTA-13.
On procedural issues, delegates differed over whether to develop one or two draft decisions.
SAUDI ARABIA and several other developing countries, opposed by AUSTRALIA and JAPAN, supported continuing work on the basis of the Co-Chairs' consolidated text.
SWITZERLAND said it was premature to take a decision on long-term actions without further research, information and a full assessment of options, and said this process was moving too fast.
Several non-Annex I Parties expressed concern that this position would make it difficult to move forward, and KUWAIT noted that this could result in the whole package of issues being blocked.
NIGERIA said there was sufficient information to take action, in spite of gaps.
Co-Chair Kjellén said the group should continue discussions to move forward based on the consolidated text.
Chair Chow introduced the draft consolidated text on mechanisms.
SAUDI ARABIA requested adjournment of the meeting, noting the obstructive position of certain Annex I Parties in the contact group on adverse effects, and recalling the agreement struck on 9 June to use the consolidated texts on adverse effects and on mechanisms as the basis for negotiation.
SWITZERLAND, supported by SAMOA, CANADA and JAPAN, and opposed by BRAZIL and KUWAIT, requested further discussion on the consolidated text.
Delegates resumed their deliberations and recommended, inter alia: the development of a more concise text; elaboration of the nature and scope of the mechanisms; development of a participatory and transparent system that engages the private sector; and clarity on dealing with assigned amounts within each mechanism.
This contact group reached agreement on the second draft of the Guidelines for National Systems under Protocol Article 5.1.
The Secretariat introduced SBSTA-12 draft Conclusions on Good Practice Guidance and Uncertainty Management in National GHG Inventories.
In considering the Chairs' draft Conclusions on Guidelines under Protocol Articles 5, 7 and 8, delegates discussed, inter alia, deadlines for the voluntary implementation of the guidelines for national systems and for their possible revision based on experience of Parties.
The Friends of the Chair group exchanged views on the themes for action emerging from the regional consultative process.
The spirit of cooperation generated during the informal meetings was shaken late Monday, when tensions in negotiations in the contact group on adverse effects spilled over into the mechanisms group in what many saw as tit-for-tat reprisals.
The apparent reluctance of some Annex I Parties to discuss a consolidated text based on Parties' proposals on adverse effects sparked a response in the mechanisms group from Saudi Arabia, who sought to bring the meeting to an abrupt halt.
Several delegates observed that the incident underlined the difficulties in moving forward on a 'package' given some Parties' insistence on simultaneous progress on all issues.
Others also noted that divisions within the G-77/China on adverse effects were becoming more apparent by the day.
Taka Hiraishi, IPCC, said the IPCC report on this topic was a significant additional instrument in improving national inventory estimates.
The EU urged adoption at COP-6 of good practice guidance as part of inventory reporting.
GHANA called for regional workshops to enhance developing country understanding of the IPCC report.
Co-Chair Paciornik reported on the pre- sessional informal meeting and its outcomes.
The US and JAPAN recommended adoption of guidelines for national systems at COP-6.
The EU said some matters under Articles 5, 7 and 8 can only be completed after COP-6, as decisions made on other issues need to be taken into consideration.
The G-77/CHINA said work on Articles 5, 7 and 8 should take into account other Protocol articles, including those on demonstrable progress, the financial mechanism and adverse effects.
On the linkage to the mechanisms, JAPAN proposed that any Party should be able to use the mechanisms until non-compliance with Articles 5 and/or 7 is proven.
Delegates considered experiences with the review of second national communications.
SWITZERLAND, with the RUSSIAN FEDERATION, underlined the importance of training review experts, and proposed a workshop to exchange information on the preparation of third national communications.
The EU said it expected a decision on Protocol Article 7.2 (national communications) at COP-6 and a decision on Protocol Article 8 (review of information) at COP-7.
The US and CANADA suggested postponing consideration of the review of guidelines on national communications until SB-14.
SBI heard the first report of the Consultative Group of Experts (CGE), which was established to assist non-Annex I Parties improve their national communications.
CGE Chair José Gonzalez Miguez (Brazil) said the CGE had at its first meeting agreed on a schedule of meetings and activities, and prepared an indicative budget.
The EU, opposed by BRAZIL, the CENTRAL AFRICAN REPUBLIC and KENYA, suggested that the CGE's findings be presented by June 2001 to contribute to the review of guidelines so as to adopt at COP-7 improved guidelines for the second national communications.
The US urged the CGE to provide specific advice on the guidelines and report on it at SB-14.
Several Parties highlighted the importance of the GEF's support for the preparation of non- Annex I national communications and expressed appreciation for the GEF Capacity Development Initiative (CDI).
CANADA supported the comprehensive approach in assessing capacity development needs.
The EU said the CDI should provide the basis for a framework on capacity building, along with national communications.
The G-77/CHINA stressed the need to link the CDI to the overall process under decision 10/CP.5 (capacity building in developing countries) to avoid duplication.
The IPCC outlined the GEF's proposal entitled 'Assessment of Impacts of, and Adaptation to, Climate Change in Multiple Regions and Sectors in Coordination with the IPCC.
FCCC Executive Secretary Michael Zammit Cutajar presented a document on late payment of contributions.
He suggested consideration of the option that Parties with arrears of one year or more could be ineligible to, inter alia: host a session of the COP/Subsidiary Bodies; be invited to or receive funding to attend informal meetings; or be allocated membership of the Bureau of the COP or its subsidiary bodies.
Several Parties stressed the need for further exploration of the options presented by the Executive Secretary.
Informal consultations will be held on this issue.
SBSTA Chair Dovland (Norway) opened the meeting and called on delegates to develop text on as many issues as possible in accordance with the Buenos Aires Plan of Action.
The G-77/CHINA stressed the need to negotiate the issues as a package and said the outcome should be a balanced set of decisions.
He called on Annex II Parties to commit specific financial resources for technology transfer and capacity building by COP-6.
Chair Dovland reported on the recent workshops and informal meetings on FCCC Article 4.8 and 4.9 and Protocol Article 3.14 (adverse effects).
The G-77/CHINA, with other non-Annex I Parties, advocated the adoption of two draft decisions: one on Article 4.8 and 4.9 and another on Article 3.14.
The EU, AUSTRALIA, JAPAN, US and SWITZERLAND preferred a single decision.
AUSTRALIA, with JAPAN and others, said the consolidated text was not an appropriate basis for contact group discussion, and proposed revisiting the compilation of Parties' views.


| Rank Config | Def Value | Def OP Value | Info |
| display.badge |
Default: ""
| "" |
Prefix of player's nickname
|
| display.color |
- Default:
"white"
- Variants:
- aqua
- black
- blue
- bold
- dark_aqua
- dark_blue
- dark_gray
- dark_green
- dark_purple
- dark_red
- gold
- gray
- green
- italic
- light_purple
- obfuscated
- red
- reset
- strikethrough
- underline
- white
- yellow
| "green" |
Color of player's nickname
|
| display.prefix |
Default: ""
| "" |
Prefix of player's nickname
|
| ftbu.chunkloader.offline_timer |
| -1.0 |
- -1 - Chunk will always be loaded
- 0 - Disabled, will unload instantly when he disconnects
- Max hours player can be offline until he's chunks unload
|
| ftbu.chunkloader.type |
- Default:
"offline"
- Variants:
| "offline" |
- disabled: Players won't be able to chunkload
- offline: Chunks stay loaded when player loggs off
- online: Chunks only stay loaded while owner is online
|
| ftbu.claims.forced_explosions |
| "-" |
- -: Player setting
- disabled: Explosions will never happen in claimed chunks
- enabled: Explosions will always happen in claimed chunks
|
| ftbu.homes.max |
- Default:
1
- Min: 0
- Max: 30000
| 100 |
Max home count
|


Firewall to activate on connection
This field can be used to have an IPchains firewall automatically enabled
when the ADSL connection is made. However, Webmin's Linux Firewall module
can be used instead to create and customize a firewall of your choice.


If you are interested in sponsoring the conference, you may either contact us at<EMAIL_ADDRESS>or you can register as a sponsor using the Registration link. Sponsorship price is $4,000 and includes two tickets to the conference, a table at the conference furnished with 2 chairs and power setup in a location that will attract attended traffic, and your corporate logo listed on the conference website and conference program.


'3BlackChicks Review...'
TOMB RAIDER (2001) Rated PG-13; running time 101 minutes Genre: Action Seen at: Jack Lokes' Celebration Cinema (Lansing, Michigan) Official site: http://www.tombraidermovie.com/ IMDB site: http://us.imdb.com/Details?0146316 Written by: Patrick Massett, John Zinman Directed by: Simon West Cast: Angelina Jolie, Jon Voight, Iain Glen, Daniel Craig, Noah Taylor, Chris Barrie
Review Copyright Rose Cooper, 2001 Review URL: http://www.3blackchicks.com/bamstombraider.html
Of all the sins in the world of motion pictures, the most unforgivable sin is to bore the audience to death.

The Upshot (WARNING: **DEFINITE spoilers contained below**): Beyond all the MysticMumboJumbo, beyond Lara's SuperPowers (chief among them, her PerkyTits), beyond the total lack of character development in this completely plot-driven movie (Not A Good Thing, when the plot stinks), there is a question that I kept asking; one similar to the question Spock had in the similarly-bad STAR TREK 5 when he asked, "why would God need a starship?"
My question? Why in the world would someone who had the capacity to give someone else The Power Of God, do so? No, really; I need to know. If you had The Key, the only way to unlock The Mysteries Of The Universe, something no one else could force from you, because you could always call a Do Over - would you just say "right; here ya go, mate". WTF? I mean, WTFF?
Nothing else about this movie mattered to me beyond that question. It didn't matter that Patrick Massett and John Zinman wouldn't know a good story if it fell on its knees and offered them a Lewinsky, or that Simon West apparently only watched the second, gut-bustingly awful "Indiana Jones" flick [maybe the much-superior first and third installments weren't available at Blockbuster that weekend], or that Angelina Jolie's Humorous Bits were delivered in such a staccato voice, they may as well have been absent, or that NOT ONE of the supporting characters' backstories, made the slightest bit of bloody sense (not that their front stories were any better). No, none of that mattered, nor did the admittedly well-executed stuntwork of TOMB RAIDER - all because of that damnable question. Or, more to the point, because of its only logical answer.
Thanks, guys, for trashing another hero of mine, with illogic, bad plotting, and useless background characters. Thanks a bleepin lot.
Bammer's Bottom Line: I'm pissed. Sorry, but there's no better way to put it. I'm completely ripped. I had anticipated this movie for so long - mostly because I thought Jolie was absolutely perfect for it. And this is the thanks I get?
I'm just glad Hollyweird has no interest in developing a QBert movie.
TOMB RAIDER (rating: flashing redlight): The upside? It's pretty much a sure bet that there won't be a "Tomb Raider 2". How could there be? They've already used up their Power Of God chip; where would one go from there?
Rose "Bams" Cooper Webchick and Editor, 3BlackChicks Review Entertainment Reviews With Flava! Copyright Rose Cooper, 2001 EMAIL<EMAIL_ADDRESS>http://www.3blackchicks.com/
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


| tensor.prod.model.matrix {mgcv} | R Documentation |
Produce model matrices or penalty matrices for a tensor product smooth from the model matrices or penalty matrices for the marginal bases of the smooth.
tensor.prod.model.matrix(X) tensor.prod.penalties(S)
X |
a list of model matrices for the marginal bases of a smooth |
S |
a list of penalties for the marginal bases of a smooth. |
If X[[1]]
, X[[2]]
... X[[m]]
are the model matrices of the marginal bases of
a tensor product smooth then the ith row of the model matrix for the whole tensor product smooth is given by
X[[1]][i,]%x%X[[2]][i,]%x% ... X[[m]][i,]
, where %x%
is the Kronecker product. Of course
the routine operates column-wise, not row-wise!
If S[[1]]
, S[[2]]
... S[[m]]
are the penalty matrices for the marginal bases, and
I[[1]]
, I[[2]]
... I[[m]]
are corresponding identity matrices, each of the same
dimension as its corresponding penalty, then the tensor product smooth has m associate penalties of the form:
S[[1]]%x%I[[2]]%x% ... I[[m]]
,
I[[1]]%x%S[[2]]%x% ... I[[m]]
...
I[[1]]%x%I[[2]]%x% ... S[[m]]
.
Of course it's important that the model matrices and penalty matrices are presented in the same order when constructing tensor product smooths.
Either a single model matrix for a tensor product smooth, or a list of penalty terms for a tensor product smooth.
Simon N. Wood<EMAIL_ADDRESS>Wood, S.N. (2006) Low rank scale invariant tensor product smooths for Generalized Additive Mixed Models. Biometrics 62(4):1025-1036
te
, smooth.construct.tensor.smooth.spec
require(mgcv) X <- list(matrix(1:4,2,2),matrix(5:10,2,3)) tensor.prod.model.matrix(X) S<-list(matrix(c(2,1,1,2),2,2),matrix(c(2,1,0,1,2,1,0,1,2),3,3)) tensor.prod.penalties(S)


|
||||||||||
| PREV NEXT | FRAMES NO FRAMES |
| Packages that use Subject | |
|---|---|
| org.apache.shiro | This package primarily exists as a root classpath distinction, but it does contain two core classes widely used
by applications, SecurityUtils and
ShiroException . |
| org.apache.shiro.aop | Components used to support the framework's AOP/interception support classes. |
| org.apache.shiro.cas | |
| org.apache.shiro.concurrent | Executor , ExecutorService ,
and ScheduledExecutorService implementations for transparent
Subject association with threads in an asynchronous execution environment. |
| org.apache.shiro.mgt | Provides the master SecurityManager interface and a default implementation
hierarchy for managing all aspects of Shiro's functionality in an application. |
| org.apache.shiro.subject | Components supporting the Subject interface, the most important concept in
Shiro's API. |
| org.apache.shiro.subject.support | Concrete support implementations of most of the org.apache.shiro.subject interfaces. |
| org.apache.shiro.util | Your run-of-the-mill 'util' pacakge for components and logic widely used across the framework that can't find their home into a proper OO hierarchy (or, most likely for things used across many hierarchies). |
| org.apache.shiro.web.filter | Base package supporting all Servlet Filter implementations used to control
access to web pages and URL resources. |
| org.apache.shiro.web.filter.authc | Servlet Filter implementations specific to controlling access based on a
subject's authentication status, or those that can execute authentications (log-ins) directly. |
| org.apache.shiro.web.mgt | Components supporting web-specific
SecurityManager implementations. |
| org.apache.shiro.web.servlet | Shiro-specific implementations of the Servlet API (Servlet Filters, et al). |
| org.apache.shiro.web.subject | Web-specific Subject interfaces to enable Subject use in web
environments. |
| org.apache.shiro.web.subject.support | Supporting implementations of org.apache.shiro.web.subject package interfaces. |
| org.apache.shiro.web.tags | Provides the Shiro JSP Tag Library implementations. |
| Uses of Subject in org.apache.shiro |
|---|
| Methods in org.apache.shiro that return Subject | |
|---|---|
static Subject |
SecurityUtils.getSubject()
Returns the currently accessible Subject available to the calling code depending on
runtime environment. |
| Uses of Subject in org.apache.shiro.aop |
|---|
| Methods in org.apache.shiro.aop that return Subject | |
|---|---|
protected Subject |
MethodInterceptorSupport.getSubject()
Returns the Subject associated with the currently-executing code. |
protected Subject |
AnnotationHandler.getSubject()
Returns the Subject associated with the currently-executing code. |
| Uses of Subject in org.apache.shiro.cas |
|---|
| Methods in org.apache.shiro.cas that return Subject | |
|---|---|
Subject |
CasSubjectFactory.createSubject(SubjectContext context)
|
| Methods in org.apache.shiro.cas with parameters of type Subject | |
|---|---|
protected boolean |
CasFilter.onLoginSuccess(AuthenticationToken token,
Subject subject,
ServletRequest request,
ServletResponse response)
If login has been successful, redirect user to the original protected url. |
| Uses of Subject in org.apache.shiro.concurrent |
|---|
| Methods in org.apache.shiro.concurrent that return Subject | |
|---|---|
protected Subject |
SubjectAwareExecutor.getSubject()
Returns the currently Subject instance that should be associated with Runnable or Callable instances before being dispatched to the target Executor instance. |
| Uses of Subject in org.apache.shiro.mgt |
|---|
| Methods in org.apache.shiro.mgt that return Subject | |
|---|---|
protected Subject |
DefaultSecurityManager.createSubject(AuthenticationToken token,
AuthenticationInfo info,
Subject existing)
Creates a Subject instance for the user represented by the given method arguments. |
Subject |
SubjectFactory.createSubject(SubjectContext context)
Creates a new Subject instance reflecting the state of the specified contextual data. |
Subject |
SecurityManager.createSubject(SubjectContext context)
Creates a Subject instance reflecting the specified contextual data. |
Subject |
DefaultSubjectFactory.createSubject(SubjectContext context)
|
Subject |
DefaultSecurityManager.createSubject(SubjectContext subjectContext)
This implementation functions as follows: Ensures the SubjectContext is as populated as it can be, using heuristics to acquire
data that may not have already been available to it (such as a referenced session or remembered principals).
Calls DefaultSecurityManager.doCreateSubject(org.apache.shiro.subject.SubjectContext) to actually perform the
Subject instance creation.
calls save(subject) to ensure the constructed
Subject 's state is accessible for future requests/invocations if necessary.
returns the constructed Subject instance.
|
protected Subject |
DefaultSecurityManager.doCreateSubject(SubjectContext context)
Actually creates a Subject instance by delegating to the internal
subjectFactory . |
Subject |
SecurityManager.login(Subject subject,
AuthenticationToken authenticationToken)
Logs in the specified Subject using the given authenticationToken , returning an updated Subject
instance reflecting the authenticated state if successful or throwing AuthenticationException if it is
not. |
Subject |
DefaultSecurityManager.login(Subject subject,
AuthenticationToken token)
First authenticates the AuthenticationToken argument, and if successful, constructs a
Subject instance representing the authenticated account's identity. |
protected Subject |
DefaultSubjectFactory.newSubjectInstance(PrincipalCollection principals,
boolean authenticated,
String host,
Session session,
SecurityManager securityManager)
Deprecated. since 1.2 - override DefaultSubjectFactory.createSubject(org.apache.shiro.subject.SubjectContext) directly if you
need to instantiate a custom Subject class. |
Subject |
SubjectDAO.save(Subject subject)
Persists the specified Subject's state for later access. |
Subject |
DefaultSubjectDAO.save(Subject subject)
Saves the subject's state to the subject's session only
if sessionStorageEnabled(subject) . |
| Methods in org.apache.shiro.mgt with parameters of type Subject | |
|---|---|
protected void |
DefaultSecurityManager.beforeLogout(Subject subject)
|
protected void |
DefaultSecurityManager.bind(Subject subject)
Deprecated. in favor of save(subject) . |
protected Subject |
DefaultSecurityManager.createSubject(AuthenticationToken token,
AuthenticationInfo info,
Subject existing)
Creates a Subject instance for the user represented by the given method arguments. |
void |
SubjectDAO.delete(Subject subject)
Removes any persisted state for the specified Subject instance. |
void |
DefaultSubjectDAO.delete(Subject subject)
Removes any existing subject state from the subject's session (if the session exists). |
protected void |
DefaultSecurityManager.delete(Subject subject)
Removes (or 'unbinds') the Subject's state from the application, typically called during DefaultSecurityManager.logout(org.apache.shiro.subject.Subject) .. |
protected abstract void |
AbstractRememberMeManager.forgetIdentity(Subject subject)
Forgets (removes) any remembered identity data for the specified Subject instance. |
protected PrincipalCollection |
AbstractRememberMeManager.getIdentityToRemember(Subject subject,
AuthenticationInfo info)
Returns info .getPrincipals() and
ignores the Subject argument. |
boolean |
SessionStorageEvaluator.isSessionStorageEnabled(Subject subject)
Returns true if the specified Subject 's
session may be used to persist that Subject's
state, false otherwise. |
protected boolean |
DefaultSubjectDAO.isSessionStorageEnabled(Subject subject)
Determines if the subject's session will be used to persist subject state or not. |
boolean |
DefaultSessionStorageEvaluator.isSessionStorageEnabled(Subject subject)
This implementation functions as follows: If the specified Subject already has an existing Session (typically because an application developer
has called subject.getSession() already), Shiro will use that existing session to store subject state.
If a Subject does not yet have a Session, this implementation checks the
sessionStorageEnabled property:
If sessionStorageEnabled is true (the default setting), a new session may be created to persist
Subject state if necessary.
If sessionStorageEnabled is false , a new session will not be created to persist
session state.
Most applications use Sessions and are OK with the default true setting for sessionStorageEnabled . |
Subject |
SecurityManager.login(Subject subject,
AuthenticationToken authenticationToken)
Logs in the specified Subject using the given authenticationToken , returning an updated Subject
instance reflecting the authenticated state if successful or throwing AuthenticationException if it is
not. |
Subject |
DefaultSecurityManager.login(Subject subject,
AuthenticationToken token)
First authenticates the AuthenticationToken argument, and if successful, constructs a
Subject instance representing the authenticated account's identity. |
void |
SecurityManager.logout(Subject subject)
Logs out the specified Subject from the system. |
void |
DefaultSecurityManager.logout(Subject subject)
|
protected void |
DefaultSubjectDAO.mergeAuthenticationState(Subject subject)
Merges the Subject's current authentication state with whatever may be in any available session. |
protected void |
DefaultSubjectDAO.mergePrincipals(Subject subject)
Merges the Subject's current getPrincipals() with whatever may be in
any available session. |
protected void |
DefaultSecurityManager.onFailedLogin(AuthenticationToken token,
AuthenticationException ae,
Subject subject)
|
void |
RememberMeManager.onFailedLogin(Subject subject,
AuthenticationToken token,
AuthenticationException ae)
Reacts to a failed authentication attempt, typically by forgetting any previously remembered principals for the Subject. |
void |
AbstractRememberMeManager.onFailedLogin(Subject subject,
AuthenticationToken token,
AuthenticationException ae)
Reacts to a failed login by immediately forgetting any
previously remembered identity. |
void |
RememberMeManager.onLogout(Subject subject)
Reacts to a Subject logging out of the application, typically by forgetting any previously remembered principals for the Subject. |
void |
AbstractRememberMeManager.onLogout(Subject subject)
Reacts to a subject logging out of the application and immediately forgets any previously stored identity and returns. |
protected void |
DefaultSecurityManager.onSuccessfulLogin(AuthenticationToken token,
AuthenticationInfo info,
Subject subject)
|
void |
RememberMeManager.onSuccessfulLogin(Subject subject,
AuthenticationToken token,
AuthenticationInfo info)
Reacts to a successful authentication attempt, typically saving the principals to be retrieved ('remembered') for future system access. |
void |
AbstractRememberMeManager.onSuccessfulLogin(Subject subject,
AuthenticationToken token,
AuthenticationInfo info)
Reacts to the successful login attempt by first always forgetting any previously
stored identity. |
void |
AbstractRememberMeManager.rememberIdentity(Subject subject,
AuthenticationToken token,
AuthenticationInfo authcInfo)
Remembers a subject-unique identity for retrieval later. |
protected void |
AbstractRememberMeManager.rememberIdentity(Subject subject,
PrincipalCollection accountPrincipals)
Remembers the specified account principals by first converting them to a byte
array and then remembers that
byte array. |
protected void |
DefaultSecurityManager.rememberMeFailedLogin(AuthenticationToken token,
AuthenticationException ex,
Subject subject)
|
protected void |
DefaultSecurityManager.rememberMeLogout(Subject subject)
|
protected void |
DefaultSecurityManager.rememberMeSuccessfulLogin(AuthenticationToken token,
AuthenticationInfo info,
Subject subject)
|
protected abstract void |
AbstractRememberMeManager.rememberSerializedIdentity(Subject subject,
byte[] serialized)
Persists the identity bytes to a persistent store for retrieval later via the AbstractRememberMeManager.getRememberedSerializedIdentity(SubjectContext) method. |
protected void |
DefaultSubjectDAO.removeFromSession(Subject subject)
Removes any existing subject state from the Subject's session (if the session exists). |
Subject |
SubjectDAO.save(Subject subject)
Persists the specified Subject's state for later access. |
Subject |
DefaultSubjectDAO.save(Subject subject)
Saves the subject's state to the subject's session only
if sessionStorageEnabled(subject) . |
protected void |
DefaultSecurityManager.save(Subject subject)
Saves the subject's state to a persistent location for future reference if necessary. |
protected void |
DefaultSubjectDAO.saveToSession(Subject subject)
Saves the subject's state (it's principals and authentication state) to its session . |
protected void |
DefaultSecurityManager.stopSession(Subject subject)
|
protected void |
DefaultSecurityManager.unbind(Subject subject)
Deprecated. in Shiro 1.2 in favor of DefaultSecurityManager.delete(org.apache.shiro.subject.Subject) |
| Uses of Subject in org.apache.shiro.subject |
|---|
| Methods in org.apache.shiro.subject that return Subject | |
|---|---|
Subject |
Subject.Builder.buildSubject()
Creates and returns a new Subject instance reflecting the cumulative state acquired by the
other methods in this class. |
Subject |
SubjectContext.getSubject()
Returns any existing Subject that may be in use at the time the new Subject instance is
being created. |
| Methods in org.apache.shiro.subject with parameters of type Subject | |
|---|---|
void |
SubjectContext.setSubject(Subject subject)
Sets the existing Subject that may be in use at the time the new Subject instance is
being created. |
| Uses of Subject in org.apache.shiro.subject.support |
|---|
| Classes in org.apache.shiro.subject.support that implement Subject | |
|---|---|
class |
DelegatingSubject
Implementation of the Subject interface that delegates
method calls to an underlying SecurityManager instance for security checks. |
| Methods in org.apache.shiro.subject.support that return Subject | |
|---|---|
protected Subject |
SubjectThreadState.getSubject()
Returns the Subject instance managed by this ThreadState implementation. |
Subject |
DefaultSubjectContext.getSubject()
|
| Methods in org.apache.shiro.subject.support with parameters of type Subject | |
|---|---|
void |
DefaultSubjectContext.setSubject(Subject subject)
|
| Constructors in org.apache.shiro.subject.support with parameters of type Subject | |
|---|---|
SubjectCallable(Subject subject,
Callable<V> delegate)
|
|
SubjectRunnable(Subject subject,
Runnable delegate)
Creates a new SubjectRunnable that, when executed, will execute the target delegate , but
guarantees that it will run associated with the specified Subject . |
|
SubjectThreadState(Subject subject)
Creates a new SubjectThreadState that will bind and unbind the specified Subject to the
thread |
| Uses of Subject in org.apache.shiro.util |
|---|
| Methods in org.apache.shiro.util that return Subject | |
|---|---|
static Subject |
ThreadContext.getSubject()
Convenience method that simplifies retrieval of a thread-bound Subject. |
static Subject |
ThreadContext.unbindSubject()
Convenience method that simplifies removal of a thread-local Subject from the thread. |
| Methods in org.apache.shiro.util with parameters of type Subject | |
|---|---|
static void |
ThreadContext.bind(Subject subject)
Convenience method that simplifies binding a Subject to the ThreadContext. |
| Uses of Subject in org.apache.shiro.web.filter |
|---|
| Methods in org.apache.shiro.web.filter that return Subject | |
|---|---|
protected Subject |
AccessControlFilter.getSubject(ServletRequest request,
ServletResponse response)
Convenience method that acquires the Subject associated with the request. |
| Uses of Subject in org.apache.shiro.web.filter.authc |
|---|
| Methods in org.apache.shiro.web.filter.authc that return Subject | |
|---|---|
protected Subject |
LogoutFilter.getSubject(ServletRequest request,
ServletResponse response)
Returns the currently executing Subject . |
| Methods in org.apache.shiro.web.filter.authc with parameters of type Subject | |
|---|---|
protected String |
LogoutFilter.getRedirectUrl(ServletRequest request,
ServletResponse response,
Subject subject)
Returns the redirect URL to send the user after logout. |
protected boolean |
FormAuthenticationFilter.onLoginSuccess(AuthenticationToken token,
Subject subject,
ServletRequest request,
ServletResponse response)
|
protected boolean |
AuthenticatingFilter.onLoginSuccess(AuthenticationToken token,
Subject subject,
ServletRequest request,
ServletResponse response)
|
| Uses of Subject in org.apache.shiro.web.mgt |
|---|
| Methods in org.apache.shiro.web.mgt that return Subject | |
|---|---|
Subject |
DefaultWebSubjectFactory.createSubject(SubjectContext context)
|
protected Subject |
DefaultWebSubjectFactory.newSubjectInstance(PrincipalCollection principals,
boolean authenticated,
String host,
Session session,
ServletRequest request,
ServletResponse response,
SecurityManager securityManager)
Deprecated. since 1.2 - override DefaultWebSubjectFactory.createSubject(org.apache.shiro.subject.SubjectContext) directly if you
need to instantiate a custom Subject class. |
| Methods in org.apache.shiro.web.mgt with parameters of type Subject | |
|---|---|
protected void |
DefaultWebSecurityManager.beforeLogout(Subject subject)
|
protected void |
CookieRememberMeManager.forgetIdentity(Subject subject)
Removes the 'rememberMe' cookie from the associated WebSubject 's request/response pair. |
boolean |
DefaultWebSessionStorageEvaluator.isSessionStorageEnabled(Subject subject)
Returns true if session storage is generally available (as determined by the super class's global
configuration property DefaultSessionStorageEvaluator.isSessionStorageEnabled() and no request-specific override has turned off
session storage, false otherwise. |
protected void |
CookieRememberMeManager.rememberSerializedIdentity(Subject subject,
byte[] serialized)
Base64-encodes the specified serialized byte array and sets that base64-encoded String as the cookie value. |
protected void |
DefaultWebSecurityManager.removeRequestIdentity(Subject subject)
|
| Uses of Subject in org.apache.shiro.web.servlet |
|---|
| Methods in org.apache.shiro.web.servlet that return Subject | |
|---|---|
protected Subject |
ShiroHttpServletRequest.getSubject()
|
| Uses of Subject in org.apache.shiro.web.subject |
|---|
| Subinterfaces of Subject in org.apache.shiro.web.subject | |
|---|---|
interface |
WebSubject
A WebSubject represents a Subject instance that was acquired as a result of an incoming
ServletRequest . |
| Uses of Subject in org.apache.shiro.web.subject.support |
|---|
| Classes in org.apache.shiro.web.subject.support that implement Subject | |
|---|---|
class |
WebDelegatingSubject
Default WebSubject implementation that additional ensures the ability to retain a
servlet request/response pair to be used by internal shiro components as necessary during the request execution. |
| Uses of Subject in org.apache.shiro.web.tags |
|---|
| Methods in org.apache.shiro.web.tags that return Subject | |
|---|---|
protected Subject |
SecureTag.getSubject()
|
|
||||||||||
| PREV NEXT | FRAMES NO FRAMES |


Customers and Industries:
Pedyn has been selling software products and solutions to a broad range of buisnesses, from small start-ups to very large, well established, companies. Our Customer base serves a wide range of industries and markets.
Some Industries include: Aerospace, Automotive, Communications, Components, Computers, Construction, Consumer Goods, Defense, Electronics, Food & Beverage, Fabricated Metals, Industrial Equipment, Instruments, Homes, Medical Devices, Networks, Tools, Wireless and More.


IPCam Device Test
version:
Information
RTC
LED
IR-Cut
IR LED
Light Sensor
Audio
SD Card
Focus/Zoom
Admin
Network
Snapshot
RTSP URL
MAC
Change
IV(intelligence) license key
Change
FR(face recognition) license key
Change
LPR license key
Change
Model Name
Change
PC Time
RTC Time
Set RTC
SET RTC
Green Led
Red Led
IR Cut
Please disable D&N mode to control IR-CUT.
Please disable D&N mode to control IR-LED.
No websocket connection yet
Audio
Download Audio File
Speaker Volume
Mic Volume
Single Test
Continue Test
Zoom
Focus
one push
MFG Firmware Upgrade
Submit
NSC Firmware Upgrade
Submit
Reboot
Reboot
Change Boot Partition
Change
factory reset
Reset
Static IP
DHCP
Static IP
Mask
Gateway
Submit
Enable D&N Mode
Snapshot after Boot
FTP IP
Snapshot Interval
Submit
FTP Test


Contact
Github
Athenz is completely open source and can be found here on Github. We welcome any issues and pull-requests!
Slack
We use Slack for discussion and support. For any Athenz questions, join the
`#general`
channel on the
Athenz
Slack team.
For everything else, join the `#random`
channel.
Groups


Before reading, know that I generally have low-tolerance to many drugs, although i am a very experenced drug user. This was also my first time using oxycontin.
10:30 PM - Me and my good friend Chris were tring to find a party and a place to stay on Friday night. We had just bought a QP so we were smokin alot. My two friends, Katy and Crystal, called us up and asked of we wanted to pick them up to go to a party. That sounded cool so we went over to Crystal's house. When we got there they were telling us that the party might not happen. So we sat down, smoked a bowl, and tried to find somthing to do. Chris busted out a pill bottle and he had a 80 mg oxycontin. I asked if I could pay him $5 for half of it and he was cool with that because he didn't wanna take all 80 anyway. Chris broke the pill in half and we ground it up into a line with our I.D.'s. We snorted the lines and smoked a bowl.
[Erowid Note: Driving while intoxicated or tripping is dangerous and irresponsible because it endangers other people. Don't do it!]
11:30 PM - Before I started to feel the oxy, Katy asked if we wanted to stay at her house so we got up and drove over there.  Coming up felt alot like coming up on vicodin and I thought it might not be better than vicodin. I would soon find out I was extremly wrong. So I took a roll I was saving for the next day.
12:00 AM - When we got to Katy's house her stepdad was there, but he was cool with us smoking in the house. He offered us some alcohol, he had a bottle of 151. So we both took about 5 or 6 shots. The girls payed Chris for a roll each and Chris took one himself. After that I started feeling amazing, like I was floating and extremly heavy at the same time. I remember thinking 'I wish I could feel like this forever' and I couldn't get the smile off my face.
12:30 AM - We all went into her room to hit up a gravity bong filled with sensimilla, and I kept coming up! I was feeling the X a little already.  The gravity bong got to me and I took a humongous hit and about ten seconds later everything started to get darker, and a minute later I couldn't see anything with my eyes completly open. I seriously went blind. I didn't tell anybody for like 5 minutes because I thought it would go away, but I started to feel dizzy so I told Chris and asked if he could help me to the couch.
1:00 AM - I laid down and crystal was diggin me so she laid down next to me. Katy got me a cold towel to put on my face cause i was sweating really bad. I started to have a 'Oxy-Dream' as my friends call it, It's a dream that you don't know is a dream until you wake up, and you get them when your on oxy. I don't remember what it was about but it was cool. When I woke up I was startled, but I could see light sources and eventully my vision came back.
1:30 AM - Now that the bad part was over I felt the best I ever have in my life. The X was hitting me like crazy. So incredibly euphoric that I almost started crying out of joy. We smoked another bowl and had a couple more shots, although I didn't really need it. One of the girls was hittin on me, so we fooled around a bit, making out and stuff. I asked if she wanted to hook up with me, and she was into that.  After a good hour I had an amazing orgazam that lasted about 2-3 minutes! I passed out after that for like 5-10 minutes.
3:00 AM - We went back into the living room, where Chris was having sex with Katy on the couch, me and the girl I was with when back into the kitchen cause I needed some water and a joint. We were both peaking on the X and I took off my pants, again. When I did she gave me head and although it took a while for me to cum when I did it lasted almost as long as the last time. We went back to the living room to talk to Chris.
4:00 AM- I hadn't ate anything all day, and we were getting hungry so me, the girls, and chris all went up to the 24 hour taco bell. On the way we smoked some more and after we got done eating Katy wanted to go home to sleep so we took her back and headed to one of my friend's house named James. James had a sheet of acid so we all took 2 tabs. By this time I couldn't feel the oxy anymore. We smoked a bowl and went to walk around the lake by his house.
5:30 AM - I started to feel the acid, I started to see figures in my periphial vision. We all knew we needed to smoke out of James' bong so we sat down on a bench and smoked 3 bowls or so. I started to feel the acid real good. I dicided to lay down in the grass and close my eyes to see cool stuff. It was a very good trip.
6:30 AM- When I woke up it was starting to get brighter outside. I knew a had to take Crystal home soon, but I was still seeing things that wern't there so I asked if she wamted to just stay at my place next door, and she was cool with that, so we smoked a bowl and went back to my place. I was tripping pretty good still.
7:00 AM - I was so tired I could hardly keep my eyes open. I had been up for over 36 hours. So me and Crystal smoked 2 bowls and went to sleep.
There you have it. My typical friday. Oxycontin might just be my favorite drug, even though I may have took too much my first time.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Archive
Tags
About
Gokhan Ciflikli
R | Shiny Apps | Data Visualization | Python | ML
Creating a New Theme
This tutorial will show you how to create a simple theme in Hugo.
Migrate to Hugo from Jekyll
Jekyll has a rule that any directory not starting with
_
will be copied as-is to the
_site
output.
Hello R Markdown
(Hu)go Template Primer
Hugo uses the excellent go library for its template engine.
Getting Started with Hugo
Goto hugo releases and download the appropriate version for your os and architecture.


| Package | idv.cjcat.stardust.twoD.actions |
| Class | public class LazyAction |
| Inheritance | LazyAction CompositeAction Action StardustElement |
This composite action is consisted of the folling actions:
| Property | Defined by | ||
|---|---|---|---|
| acceleration : Number
The particles' velocity acceleration.
| LazyAction | ||
| active : Boolean
Denotes if the action is active, true by default.
| Action | ||
| ageMultiplier : Number
The age action's multiplier.
| LazyAction | ||
| checkComponentMasks : Boolean | CompositeAction | ||
| collision : Boolean
Whether particles would collide against each other.
| LazyAction | ||
| damping : Number
The velocity damping coefficient.
| LazyAction | ||
| deathTrigger : DeathTrigger
[read-only]
The death trigger for particles.
| LazyAction | ||
| deflectors : Deflect
[read-only]
You can add deflectors to the simulation with this
Deflect object reference. | LazyAction | ||
| gravity : Gravity
[read-only]
You can add gravity fields to the simulation with this
Gravity object reference. | LazyAction | ||
| inAlpha : Number | LazyAction | ||
| inAlphaFunction : Function | LazyAction | ||
| inAlphaFunctionExtraParams : Array | LazyAction | ||
| inAlphaLifespan : Number | LazyAction | ||
| inScale : Number | LazyAction | ||
| inScaleFunction : Function | LazyAction | ||
| inScaleFunctionExtraParams : Array | LazyAction | ||
| inScaleLifespan : Number | LazyAction | ||
| mask : int | LazyAction | ||
| moveMultiplier : Number
The move action's multiplier.
| LazyAction | ||
| name : String | StardustElement | ||
| needsSortedParticles : Boolean | CompositeAction | ||
| onAdd : ISignal
Dispatched when the added to an emitter.
| Action | ||
| onPriorityChange : ISignal
Dispatched when the action's priority is changed.
| Action | ||
| onRemove : ISignal
Dispatched when the removed from an emitter.
| Action | ||
| orientationFactor : Number
The orientation factor, 1 by default.
| LazyAction | ||
| orientationOffset : Number
The orientation offset, 90 by default.
| LazyAction | ||
| oriented : Boolean
Whether the particles rotatoin are oriented to their velocities.
| LazyAction | ||
| outAlpha : Number | LazyAction | ||
| outAlphaFunction : Function | LazyAction | ||
| outAlphaFunctionExtraParams : Array | LazyAction | ||
| outAlphaLifespan : Number | LazyAction | ||
| outScale : Number | LazyAction | ||
| outScaleFunction : Function | LazyAction | ||
| outScaleFunctionExtraParams : Array | LazyAction | ||
| outScaleLifespan : Number | LazyAction | ||
| priority : int
Actions will be sorted by the associated emitter according to their priorities.
| Action | ||
| skipThisAction : Boolean
Reset to false on each emitter step.
| Action | ||
| speedLimit : Number
The particles' speed limit.
| LazyAction | ||
| spinMultiplier : Number
The spin action's multiplier.
| LazyAction | ||
| stardustSpriteUpdate : Boolean
Whether the display class is a
StardustSprite subclass, false by default. | LazyAction | ||
| supports2D : Boolean
Whether this action supports 2D.
| Action | ||
| supports3D : Boolean
Whether this action supports 3D.
| Action | ||
| undead : Boolean
If set to true, particles would not be marked dead when their lives are less than or equal to zero.
| LazyAction |
| Method | Defined by | ||
|---|---|---|---|
| LazyAction | |||
| LazyAction | |||
|
clearActions():void
| LazyAction | ||
|
getElementTypeXMLTag():XML
| Action | ||
|
getRelatedObjects():Array
| LazyAction | ||
|
getXMLTag():XML
Returns the root tag of the XML representation.
| StardustElement | ||
|
getXMLTagName():String
| LazyAction | ||
|
parseXML(xml:XML, builder:XMLBuilder = null):void
| LazyAction | ||
|
postUpdate(emitter:Emitter, time:Number):void
| CompositeAction | ||
| CompositeAction | |||
|
removeAction(action:Action):void
| LazyAction | ||
|
sortActions(action:Action = null):void
| CompositeAction | ||
|
toXML():XML
| LazyAction | ||
| CompositeAction |
| Method | Defined by | ||
|---|---|---|---|
|
superAddAction(action:Action):void
| LazyAction |
| acceleration | property |
acceleration:Number
[read-write]The particles' velocity acceleration.
Implementation public function get acceleration():Number
public function set acceleration(value:Number):void
| ageMultiplier | property |
ageMultiplier:Number
[read-write]The age action's multiplier.
Implementation public function get ageMultiplier():Number
public function set ageMultiplier(value:Number):void
| collision | property |
collision:Boolean
[read-write]Whether particles would collide against each other.
Implementation public function get collision():Boolean
public function set collision(value:Boolean):void
| damping | property |
damping:Number
[read-write]The velocity damping coefficient.
Implementation public function get damping():Number
public function set damping(value:Number):void
| deathTrigger | property |
deathTrigger:DeathTrigger
[read-only]The death trigger for particles. You can add actions that you wish to act on particles upon their death to this action trigger.
Implementation public function get deathTrigger():DeathTrigger
| deflectors | property |
deflectors:Deflect
[read-only]
You can add deflectors to the simulation with this Deflect
object reference.
public function get deflectors():Deflect
| gravity | property |
gravity:Gravity
[read-only]
You can add gravity fields to the simulation with this Gravity
object reference.
public function get gravity():Gravity
| inAlpha | property |
inAlpha:Number
[read-write]Implementation
public function get inAlpha():Number
public function set inAlpha(value:Number):void
| inAlphaFunction | property |
inAlphaFunction:Function
[read-write]Implementation
public function get inAlphaFunction():Function
public function set inAlphaFunction(value:Function):void
| inAlphaFunctionExtraParams | property |
inAlphaFunctionExtraParams:Array
[read-write]Implementation
public function get inAlphaFunctionExtraParams():Array
public function set inAlphaFunctionExtraParams(value:Array):void
| inAlphaLifespan | property |
inAlphaLifespan:Number
[read-write]Implementation
public function get inAlphaLifespan():Number
public function set inAlphaLifespan(value:Number):void
| inScale | property |
inScale:Number
[read-write]Implementation
public function get inScale():Number
public function set inScale(value:Number):void
| inScaleFunction | property |
inScaleFunction:Function
[read-write]Implementation
public function get inScaleFunction():Function
public function set inScaleFunction(value:Function):void
| inScaleFunctionExtraParams | property |
inScaleFunctionExtraParams:Array
[read-write]Implementation
public function get inScaleFunctionExtraParams():Array
public function set inScaleFunctionExtraParams(value:Array):void
| inScaleLifespan | property |
inScaleLifespan:Number
[read-write]Implementation
public function get inScaleLifespan():Number
public function set inScaleLifespan(value:Number):void
| mask | property |
mask:int
[read-write]Implementation
public function get mask():int
public function set mask(value:int):void
| moveMultiplier | property |
moveMultiplier:Number
[read-write]The move action's multiplier.
Implementation public function get moveMultiplier():Number
public function set moveMultiplier(value:Number):void
| orientationFactor | property |
orientationFactor:Number
[read-write]The orientation factor, 1 by default.
Implementation public function get orientationFactor():Number
public function set orientationFactor(value:Number):void
| orientationOffset | property |
orientationOffset:Number
[read-write]The orientation offset, 90 by default.
Implementation public function get orientationOffset():Number
public function set orientationOffset(value:Number):void
| oriented | property |
oriented:Boolean
[read-write]Whether the particles rotatoin are oriented to their velocities.
Implementation public function get oriented():Boolean
public function set oriented(value:Boolean):void
| outAlpha | property |
outAlpha:Number
[read-write]Implementation
public function get outAlpha():Number
public function set outAlpha(value:Number):void
| outAlphaFunction | property |
outAlphaFunction:Function
[read-write]Implementation
public function get outAlphaFunction():Function
public function set outAlphaFunction(value:Function):void
| outAlphaFunctionExtraParams | property |
outAlphaFunctionExtraParams:Array
[read-write]Implementation
public function get outAlphaFunctionExtraParams():Array
public function set outAlphaFunctionExtraParams(value:Array):void
| outAlphaLifespan | property |
outAlphaLifespan:Number
[read-write]Implementation
public function get outAlphaLifespan():Number
public function set outAlphaLifespan(value:Number):void
| outScale | property |
outScale:Number
[read-write]Implementation
public function get outScale():Number
public function set outScale(value:Number):void
| outScaleFunction | property |
outScaleFunction:Function
[read-write]Implementation
public function get outScaleFunction():Function
public function set outScaleFunction(value:Function):void
| outScaleFunctionExtraParams | property |
outScaleFunctionExtraParams:Array
[read-write]Implementation
public function get outScaleFunctionExtraParams():Array
public function set outScaleFunctionExtraParams(value:Array):void
| outScaleLifespan | property |
outScaleLifespan:Number
[read-write]Implementation
public function get outScaleLifespan():Number
public function set outScaleLifespan(value:Number):void
| speedLimit | property |
speedLimit:Number
[read-write]The particles' speed limit.
Implementation public function get speedLimit():Number
public function set speedLimit(value:Number):void
| spinMultiplier | property |
spinMultiplier:Number
[read-write]The spin action's multiplier.
Implementation public function get spinMultiplier():Number
public function set spinMultiplier(value:Number):void
| stardustSpriteUpdate | property |
stardustSpriteUpdate:Boolean
[read-write]
Whether the display class is a StardustSprite
subclass, false by default.
public function get stardustSpriteUpdate():Boolean
public function set stardustSpriteUpdate(value:Boolean):void
| undead | property |
undead:Boolean
[read-write]If set to true, particles would not be marked dead when their lives are less than or equal to zero.
Implementation public function get undead():Boolean
public function set undead(value:Boolean):void
| LazyAction | () | constructor |
public function LazyAction()
| addAction | () | method |
| clearActions | () | method |
public override function clearActions():void
| getRelatedObjects | () | method |
public override function getRelatedObjects():Array
Returns
Array |
| getXMLTagName | () | method |
public override function getXMLTagName():String
Returns
String |
| parseXML | () | method |
public override function parseXML(xml:XML, builder:XMLBuilder = null):void
Parameters
xml:XML |
|
builder:XMLBuilder (default = null )
|
| removeAction | () | method |
| superAddAction | () | method |
| toXML | () | method |
public override function toXML():XML
Returns
XML |